coulomb/the-custodian
5
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Record approved API guard delivery and completed owner returns
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Reject generated-only commits / generated-commit-guard (push) Successful in 9s
Details

Browse source
This commit is contained in:
codex 2026-10-17 04:02:49 +02:00
parent b17e753efc
commit ceaeef1ee7
33 changed files with 2800 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

29
docs/netkingdom-target-implementation.md
View file

@ -903,3 +903,32 @@ All sixteen native target gates remain open.
The same pending API guard proposal now has revision 2, SHA256 `5d0ddebc21bcb035809cc8b57f4c2e1ba8ed09204be5b965460e178a90913f1e`, at `docs/changes/netkingdom-target-2026-10-17/guard-successor-review-r2/FINAL-PROPOSAL.md`. Only the probe source-hash metadata representation changed after the normal scanner flagged hashes as generic API keys. Revision 1 remains unapproved and unexecuted; the runtime image, probe case logic, acceptance exception and recovery scope are unchanged. Source-publication receipt hashes are exposed through reversible typed metadata companions; original bytes and the refused scan remain retained.
The owner’s WP-only revision-2 reference amendment is published at State Hub `4c03c9d2c6a47f5c7247473f74b2e2f188b787bd`. Final source/remote/primary readback verifies all 26 affected owner task bindings; runtime source remains `51bc70d` and the proposed guard image remains `c103cbf`.
## Approved API guard delivered and verified, 2026-10-17
The founder approved `STATE-WP-0095-T10-frozen-bindings-guard-r1` revision 2,
SHA256 `5d0ddebc21bcb035809cc8b57f4c2e1ba8ed09204be5b965460e178a90913f1e`,
through decision `df703266-6719-4c04-ae1b-ba9afd3bca1c`. The exact pinned
`main-c103cbf@sha256:4cc4ce17bbcdb1b66132d07c5b7b741f46df83124ef1c8403ffabdafba6993d1`
image is delivered at Helm 77. API and MCP are Ready; applied/expected schema
remains `c4d5e6f7a8b9`. The exact observed migration Job and owned Pod are gone,
and only the verified owned chart staging was removed. No recovery was needed.
All eight deployed owner-handler cases passed with enforced commit interception,
rollback and fresh-transaction comparison. The actual ordinary Cluster pipeline
passes with the verified installed checker: 20/20 ordinary bindings, three frozen
bindings omitted, and all eighteen CURRENT historical full rows unchanged across
the rollout, native probes and maintenance. All three frozen archives and
unrelated staged/worktree state are preserved. The earlier three-parent mismatch
remains a founder-approved historical exception: unavailable old preimages were
not guessed, restored or relabeled as a passing result. Runtime acceptance is
separate from all sixteen NetKingdom native target gates, which remain open.
Frozen acceptance return:
`docs/changes/netkingdom-target-2026-10-17/guard-successor-execution-r2/verified-receiving-return.json`,
SHA256 `09958bd69367cc6903e2a21a56eb81b6a8a46c2a1907afc93f787cd63732e92a`.
The supervision record retains original revision 1, the approved/executed revision
2, exact digests and successful refined outcome; it grants no autopilot authority.
Source follow-through: State Hub `200cbd0a61a805d0fe29f9d6d1c49a6cf1f1703a` finishes STATE-WP-0095 with all ten tasks done and declared image pins matching the verified deployment; Repo Manager `3bcb1e1cf3e58b263f690534f7f28024d75cdbf6` finishes RMGR-WP-0019 with all six tasks done. Task UUIDs remain unchanged. The existing binding-guard successor coordination case is satisfied; independent native-owner work remains live, and no worker was woken.