Repository navigation
feat: retain immutable causal admission evidence in telemetry - #4353
Merged
Merged
Conversation
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.
When Coordination emits a committed causal admission, the telemetry receiver now accepts an independent
execution-causal-admission/1fact that binds its canonical identity and dispatch to the exact retained admission bytes. Schema-14 storage makes that fact immutable, preserves first-receipt provenance and exposes it through the boundedlearningObservationssnapshot. The private analyzer reports declaration and join coverage separately while keeping dependency wait and critical path unknown. Existing admission, lineage and usage facts and their historical identities remain unchanged.Four fixed synthetic admissions cover root, child, follow-up and explicit retry, including reordered and whitespace-bearing raw JSON. Their manifest pins all raw/event lengths and digests. Receiver tests verify 4096/4097-byte and 16/17-edge boundaries, replay/conflict behavior through a disposable schema-14 store, and opaque Dashboard projection. Source documentation keeps producer composition, publication and installed adoption pending; this PR does not enable new installed emission or infer native provenance.
Validation: LEARN analyzer suite 46 passed; focused Core decoder 3 passed; focused CLI temporary-store test 1 passed; focused Dashboard projection test 1 passed. All three .NET projects restored in locked mode from an isolated closed local feed including the authentic public FSharp.Core package; no tracked lockfile changed.
scripts/test --assert-wiredpassed, and the workflow-derived selector includes all touched suites. The exact source-built CLI artifact and its 82-file runtime closure are pinned privately for a separate C3 producer/receiver probe.