Repository navigation
feat(projections): add independently delivered graph and vector consumers - #62
Open
DivyamTalwar wants to merge 1 commit into
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.
Original-scope gap
Implements C02 / GAP-02, refs #51. Stacked on #61's authoritative history/all-event API. These are actual persistent vector and graph consumers, not another ID-only reference projection and not a dependency on another user product.
Implementation
Independent-review fixes
The composed review identified TTL eligibility, corrected-validity handling, administrative generation races and an acquisition-budget mismatch. The final candidate applies current corrected fact validity plus independent expiry restrictions, fences selection/generation/enabled state inside delivery transactions, and avoids unbounded status hydration. A formerly incompatible fixture now preserves v2 ingestion rejection and tests legacy filtering separately.
The original deletion/revocation/receipt controls remain.
docs/closure/C02-interfaces.mdrecords the before/after findings, exact test scopes and remaining composition requirements.Actual supervisor verification
Candidate
3f35c46ba91c6144aa283446299c61889394090con parent5dc8e4855d74042964fdbfa8074350d4ea372af3.Source hashes were unchanged during the full assembled run. Actual SQLite, vector ranking, graph traversal, new history APIs, parser regressions and process/restart fixtures ran. Counts include inherited cases, not independent model-quality benchmarks.
Explicit boundaries
Structured relation assertions and embedding implementations are trusted host inputs; the offline tests make no live-provider calls. Administrative raw-store APIs are not request authentication. Managed restoration must honor the current retention ledger, and the final C01/C07/C09 composition remains separately reviewed. Resource limits are declared; no global filesystem transaction, all-backup erasure, semantic superiority or full production-release signoff is claimed.
See
docs/projections.mdfor concrete setup and query examples. Review prerequisites first, retarget after merge and rerun CI. No automatic merge.