EXP-0147: project expansion coverage - #590
Draft
buger wants to merge 2 commits into
Draft
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
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.
Stacked on EXP-0132 (#589).
Adds an opt-in expansion coverage contract and deterministic request-bound live/replay projection over existing Graph v2 lifecycle facts. The exact denominator is derived from validated ClaimProjection catalog evidence, while InstanceProjection supplies the per-item lifecycle evidence. Replay rebuilds both projections before projecting coverage.
Provider outcomes are limited to clean, findings, or guardrail; the host derives error from execution failure and cancelled only from an exact managed-deadline/cancellation evidence bundle. Invalid or incomplete lineage fails closed. Semantic digests exclude request IDs and provenance, so equivalent executions remain stable across sessions and completion order.
Public engine/journal APIs expose live projection, request IDs with an optional owner filter, and replay. Normal-path tests run through executeGroupedChecks with deterministic restored fakes, real throws, a real managed deadline, order inversion, empty catalogs, and in-flight state; direct journal injection is restricted to malformed-evidence cases.
Validation:
Nonclaims: no Proof/Probe/model/network/provider integration, admission, freshness, persistence, retry, lease, or global fan-in.