Repository navigation
P2.10: presence is telemetry - #16
Merged
Merged
Conversation
Every approved validation writes {type: presence, value: 1} for the
device at the attesting host's site — into the same store as any sensor
reading, so rules and alerts apply to presence like any other metric.
The original product is now the platform's first stream.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Roadmap item
P2.10 — the strategic reframe from the original review, made literal: every approved validation writes
{type: presence, value: 1}for the device at the attesting host's site, into the sametelemetrystore as any sensor reading. Threshold rules and alerts apply to presence like any other metric — the original QR product is now the platform's first stream.Verification
🤖 Generated with Claude Code