Repository navigation
Add Observatory analytics, worker nodes, transcripts and provider inventory - #5
Merged
Merged
Conversation
flujo-app
marked this pull request as ready for review
October 3, 2026 22:42
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.
The Observatory exposes delegation metadata but leaves worker execution, conversations, analytics and cloud resources hard to inspect. This adds expanded analytics, a timestamped timeline, FLUJO node cards, transcripts with tool calls/results, and separate Modal/Fly inventory. Sticky source and section navigation make the details readable beside the spatial field.
The versioned detail projection is allowlisted and scoped to exact registered source/factory identities. Conversation evidence supplies the recorded worker position; flow definitions do not imply execution. Historical provider receipts and paid reservations remain separate from fresh provider state, and missing usage/spend stays unknown. Paid revisions cannot rewind and failed access clears private detail. The existing two-second expiry tick refreshes analytics and worker/provider freshness across lease/time boundaries even with unchanged observations, preserving transcript DOM, scroll and tool expansion.
Validation: production build and 17 viewer checks pass, including an actual JSDOM render through lease expiry and a freshness-only tick. The companion bridge passes 30 server checks and 24 real host/principal/frame checks, with synthetic transcript redaction and incremental collection cancellation regressions. Earlier authorized local qualification inspected one unbound FLUJO conversation, retained Modal/Fly receipts, and desktop/mobile rendering. Current cloud health and machine-to-conversation bindings remain unverified.
Stacked on the swarm viewer in #4. Requires https://github.com/flujo-app/brain-online/pull/36 and explicitly owned observation sources. This remains a draft; releasing and pinning a matching upstream image is required before deployment.