coulomb/user-engine
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Complete live empty custody consumer acceptance
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a1029d-2c93-7500-a0e0-e3e089668b29
This commit is contained in:
tegwick 2026-10-03 20:39:15 +02:00
parent f85c9681a7
commit 608cbff477
4 changed files with 157 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/root-custody-runtime.md
View file

@ -73,9 +73,11 @@ old state cannot detect rollback by itself. Keep this feature disabled through
restore until owner audit/history establishes the latest revision and a reviewed
reconciliation updates the baseline. Never delete the row to make a read pass.
## Remaining live acceptance
## Live acceptance and remaining owner gates
The code and offline fixtures do not establish a real grant. Delivery requires
Live empty-source consumer acceptance is now complete; see
[the receipt](evidence/2026-10-03-root-custody-consumer-live.md). The code and
offline fixtures do not establish a real grant. Full estate acceptance also needs
reviewed publisher provenance (the approved empty entries[] baseline establishes
no grant), role/policy receipts, projected-token packaging,
network trust, owner-reviewed baseline initialization, image digest promotion and
@ -88,3 +90,7 @@ It comes from NetKingdom examples/custody-record/initial-empty-record.json and
the owner provenance packet, not from positive-grant fixtures. Publication and
an actual authenticated read matching this receipt are still required before
baseline initialization.
USER-WP-0037-T02 is done for the delivered no-grant source and actual restart
acceptance. USER-WP-0037-T03 real Hub admission/private integration and platform
producer recovery/audit gates remain independently owned.