feat(cache): add rebuild and provenance safeguards
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a023c0-a0a3-7c03-b395-5a0d2757214d
This commit is contained in:
parent
bf3f416b82
commit
5dc2f3cdf6
11 changed files with 2809 additions and 4 deletions
|
|
@ -62,3 +62,8 @@ records require both repository and domain context and resolve to
|
|||
types resolve to their one declared hub owner. Unknown types and writes whose
|
||||
claimed owner disagrees with the contract are rejected instead of falling back
|
||||
to whichever hub received the request.
|
||||
|
||||
Local repository projections implement the cache side through `rmgr cache
|
||||
status|rebuild`; every read carries observation age and fingerprint-based
|
||||
staleness. The guarded legacy-cache procedure and closed provenance export are
|
||||
defined in `docs/cache-rebuild_v1.md`.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue