Bind knowledge retrieval to sealed bytes and invalidate changed releases
Assistant: codex Assistant-Model: gpt-6.1-sol Assistant-Session: 01a10238-7ecc-78e2-903d-075f50e913cc
This commit is contained in:
parent
416f9919c5
commit
d0bf65e964
16 changed files with 335 additions and 40 deletions
|
|
@ -66,6 +66,13 @@ current owner's authorization path.
|
|||
|
||||
## Refresh ownership
|
||||
|
||||
From 0.2.2, each retrieval, check and public source-status call revalidates the
|
||||
loaded release seal and package files. Returned cards use the exact bytes
|
||||
validated against that seal. A changed seal invalidates the loaded object:
|
||||
explicitly reload the reviewed bundle rather than silently following an update.
|
||||
Unsealed file changes fail closed. This detects local bundle changes; an offline
|
||||
bundle still cannot discover an upstream withdrawal it has not received.
|
||||
|
||||
Emergent Security maintains the package and tests. Every source remains owned
|
||||
by its repository; gate-house/net-kingdom adoption and publication review are
|
||||
tracked in EMERGENT-WP-0002-T02/T09, not presumed accepted. Review at least every
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue