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

Record approved empty custody bootstrap and source delivery receipt
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 8s
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 19:56:11 +02:00
parent 0d0751d39d
commit ae973142fd
2 changed files with 17 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -76,7 +76,15 @@ reconciliation updates the baseline. Never delete the row to make a read pass.
## Remaining live acceptance
The code and offline fixtures do not establish a real grant. Delivery requires
publisher ceremony provenance, role/policy receipts, projected-token packaging,
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
positive/denial/outage/revocation/supersession/restore receipts through the actual
Hub workload route. USER-WP-0037-T03 retains its separate Hub admission blocker.
Approved initial-empty candidate document digest:
`33a2ae086385028db1b654aa5646b7a98bcde1c5878c804e19315dadc3f87248`.
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.