docs(proposals): VEP-0005 — richer scopes on Claim/Source (draft) - #105
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
I wanna you prove vouch compatible with claude code and codex in next PR |
Summary
(visibility, project, agent)scopes onClaim/Source, replacing the singlescopeenum, with out-of-scope artifacts filtered from retrieval (feat: richer scopes on Claim/Source —(visibility, project, agent)[VEP] #100 is tagged [VEP]).Why a VEP and not a code PR
proposals/README.mdrequires a VEP for changes to the object model and toconfig.yamlsemantics — both of which this touches. So this opens the design for review before any code, same as VEP-0004.What the VEP proposes
Scopeenum →Visibility(values unchanged); addArtifactScope(visibility, project, agent);Claim.scope/Source.scopebecome that object.(project, agent)from request param >VOUCH_PROJECT/VOUCH_AGENTenv >config.yaml, with an explicit visibility match table. Default viewer reproduces today's single-agent behavior.mode="before"validator coerces the old barescope: projectstring into{visibility: project}, so existing.vouch/reads with no migration..vouch/is plaintext;privatemeans "hidden from other agents' default context," not "secret." Calls out fail-closed behavior forprivate.Open questions for reviewers (in the VEP)
teamvs project-unbound semantics; filter location (post-pass vs SQLWHERE); viewer-context precedence; whether Entity/Relation/Page also need scope (deferred); how sync (#90/#91) interacts with scope.Note on numbering
This is 0005; 0004 is reserved by my in-flight HTTP-transport PR (#94), so the index here skips 0004 intentionally. If the README index conflicts when both merge, I'll rebase per the numbering rule.
Test Plan
proposals/VEP-0005-richer-scopes.md(statusdraft) + index rowRefs #100 (implementation in separate PRs once/if accepted)