Repository navigation
perf: separate content lifecycle maintenance from authorized reads - #2060
Merged
Merged
Conversation
Replace collection-wide owner health scans and repeated static preset initialization with current grant decisions. Keep owner attestation on writes while allowing valid Scope and Artifact grants independently of missing owner relations. Read bounded built-in page projections under one policy/content snapshot, batch exact content, lineage and usage queries, and load review history and evidence on demand. Preserve injected application/provider boundaries. Validation: make check; Dashboard regressions; actual SQLite, seekdb and OceanBase query-budget and concurrent-snapshot tests; 45 scale scenarios.
Batch candidate projections, owner facts, and Tag basis checks while preserving current read and decision authority. Load opened history and evidence independently, retain revision cards and Scope labels, and fix Topic pagination. Cover grant revocation and restart behavior through public interfaces.
PsiACE
marked this pull request as ready for review
October 19, 2026 08:21
PsiACE
requested review from
AlexStocks,
frostming and
zhanghuidinah
as code owners
October 19, 2026 08:21
Contributor
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
Keep state-only reads consistent with the existing artifact error contract. Fold HTTP and sharing regressions into access-control tests and remove the separate read-governance suite.
Contributor
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
zhanghuidinah
approved these changes
Oct 19, 2026
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.
Which issue or RFC does this PR close?
Refs #1396 and #1813.
Rationale for this change
Reads replay initialization and repeatedly verify ownership across the entire Scope. Dashboard HTTP fan-out multiplies this work. Separate lifecycle maintenance from authorized reads.
SQLite, enforced authorization, explicit Scope, approximately 3,000 records per Family. HTTP comparison against master
683e2db0:Warm latency samples: master 2, this PR 20. Text/FTS retrieval and serial writes were measured.
Dashboard SSR SELECTs: Home 3, Notes 6, Usage 2; Scope discovery is a separate browser request. Against
268ac1b3, selected-candidate reads change 46→10, and the full history page 51→14. Opening history or evidence separately takes 4 or 6 SELECTs.What changes are included in this PR?
Are there any user-facing changes?
Valid grants remain effective without owner relations; owner-derived rights still require those facts. Artifact grants do not grant Scope discovery or metadata access.
Breaking: remove
/dashboard/guide, Notesentry, and Methodskind=allcompatibility paths.How was this change tested?
make check; focused behavior tests and E2E acceptance.AI usage statement
Codex assisted implementation, validation, and documentation.
gpt-6-astra(xhigh) contributed design and adversarial ablation analysis.