Admit reviewed receiver evidence batch 10
This commit is contained in:
codex
parent
163aa98d8e
commit
a4e90c6860
5 changed files with 1466 additions and 9 deletions
|
|
@ -766,8 +766,8 @@
|
|||
},
|
||||
{
|
||||
"proposal_id": "STATE-WP-0095-T06-cluster-frozen-receiving-r1",
|
||||
"disposition": "pending",
|
||||
"outcome": "not_executed",
|
||||
"disposition": "accepted_revised",
|
||||
"outcome": "succeeded",
|
||||
"proposal_ref": "docs/changes/netkingdom-target-2026-10-16/cluster-historical-publication-r1/revisions/r4-rollout-review/proposal-metadata.json",
|
||||
"original_revision": 1,
|
||||
"original_digest_sha256": "5bef9e7818ce1ebc64b81e300b6b40dcfc710a8625d6e0595534f8284dc2052d",
|
||||
|
|
@ -776,21 +776,21 @@
|
|||
"current_digest_sha256": "63a02e8296d126c0158b7eb2c4ce79c7eeb6f8d6f61298d473c1065c7557ba32",
|
||||
"target": "railiance01 state-hub release/API/MCP and exact-new-trial migration Job only",
|
||||
"expected_result": "Normal owner image promotion makes exact frozen cluster receiving available; API/MCP ready, expected c4 schema and exact three historical parents/15 tasks preserved; only then is later registrar admission eligible. No original TLS/identity native acceptance is inferred.",
|
||||
"verification_ref": "docs/changes/netkingdom-target-2026-10-16/cluster-historical-publication-r1/revisions/r4-rollout-review/FINAL-PROPOSAL.md",
|
||||
"verification_ref": "docs/changes/netkingdom-target-2026-10-17/receiver-rollout-r4/verified-receiving-return.json",
|
||||
"rollback_ref": "docs/changes/netkingdom-target-2026-10-16/cluster-historical-publication-r1/revisions/r4-rollout-review/MIGRATION-JOB-RECOVERY.md",
|
||||
"cost_estimate_eur": null,
|
||||
"risk_estimate_eur": null,
|
||||
"cost_estimate": "Unknown attributable execution/network/operator recovery cost on existing infrastructure; no zero-cost claim or budget reservation inferred.",
|
||||
"risk_estimate": "Unpriced production coordination outage, message migration locks/data compatibility, retained active migration Job, uncertain connection/lock mapping and recovery time; three-minute Helm wait is not a bound on outage or DB effects. Explicit supervised risk disposition required.",
|
||||
"supervisor": "Bernd Worsch",
|
||||
"approval_ref": null,
|
||||
"approved_revision": null,
|
||||
"approved_digest_sha256": null,
|
||||
"executed_revision": null,
|
||||
"executed_digest_sha256": null,
|
||||
"approval_ref": "e3798419-8aa9-5425-8c08-20df6bd82a19",
|
||||
"approved_revision": 4,
|
||||
"approved_digest_sha256": "63a02e8296d126c0158b7eb2c4ce79c7eeb6f8d6f61298d473c1065c7557ba32",
|
||||
"executed_revision": 4,
|
||||
"executed_digest_sha256": "63a02e8296d126c0158b7eb2c4ce79c7eeb6f8d6f61298d473c1065c7557ba32",
|
||||
"refinement_or_rescue": true,
|
||||
"promotion_evidence": false,
|
||||
"reason": "Exact native rollout proposal remains pending. Source preparation, synthetic compatibility and public artifact verification are evidence only; earlier preparation failures and revisions remain one trial.",
|
||||
"reason": "Founder-approved revision4 executed successfully. Helm76, exact image/module, expected schema, 18 unchanged historical full rows and five rollback-only native cases verified. Original proposal refinements retained; no unchanged-success credit.",
|
||||
"revisions": [
|
||||
{
|
||||
"revision": 1,
|
||||
|
|
@ -813,6 +813,60 @@
|
|||
"disposition": "not_submitted_or_unadjudicated",
|
||||
"executed": false
|
||||
}
|
||||
],
|
||||
"approved_digest": "63a02e8296d126c0158b7eb2c4ce79c7eeb6f8d6f61298d473c1065c7557ba32",
|
||||
"approved_at": "2026-10-16T23:55:32.549865+00:00",
|
||||
"supervisor_disposition": "Founder approved exact presented revision4 unchanged; original r1 was refined before submission, so this remains accepted_revised for original-trial scoring.",
|
||||
"approval_scope": "Exact pinned receiver rollout including inbox migration and documented conditional recovery; no authority promotion.",
|
||||
"executed_digest": "63a02e8296d126c0158b7eb2c4ce79c7eeb6f8d6f61298d473c1065c7557ba32",
|
||||
"execution_started_at": "2026-10-16T23:57:03.186884+00:00",
|
||||
"execution_ref": "docs/changes/netkingdom-target-2026-10-17/receiver-rollout-r4/execution.json",
|
||||
"verified_at": "2026-10-17T00:07:47.015454+00:00",
|
||||
"recovery_required": false,
|
||||
"post_execution_findings_ref": "docs/changes/netkingdom-target-2026-10-17/receiver-rollout-r4/ordinary-pipeline-preservation-finding.json",
|
||||
"post_execution_finding": "Later ordinary Cluster deep-consistency binding refresh changed three historical parent hashes; original delivered-rollout preservation and five rollback probes passed before that separate pipeline. Further acceptance stays open."
|
||||
},
|
||||
{
|
||||
"proposal_id": "STATE-WP-0095-T10-frozen-bindings-guard-r1",
|
||||
"disposition": "pending",
|
||||
"outcome": "not_executed",
|
||||
"proposal_ref": "docs/changes/netkingdom-target-2026-10-17/guard-successor-review-r2/proposal-metadata.json",
|
||||
"original_revision": 1,
|
||||
"original_digest_sha256": "81d365926fc585a186955d8c98ee83501fd3cec12135b2256d71b46a75097932",
|
||||
"original_digest": "81d365926fc585a186955d8c98ee83501fd3cec12135b2256d71b46a75097932",
|
||||
"current_revision": 2,
|
||||
"current_digest_sha256": "5d0ddebc21bcb035809cc8b57f4c2e1ba8ed09204be5b965460e178a90913f1e",
|
||||
"target": "railiance01/92.205.62.239 state-hub release API/MCP and exact-new-trial migration Job",
|
||||
"expected_result": "New API binding guard delivered and current-baseline native/whole-pipeline preservation verified, with earlier parent mismatch retained as explicit exception.",
|
||||
"verification_ref": "docs/changes/netkingdom-target-2026-10-17/guard-successor-review-r2/FINAL-PROPOSAL.md",
|
||||
"rollback_ref": "docs/changes/netkingdom-target-2026-10-17/guard-successor-review-r2/RECOVERY.md",
|
||||
"cost_estimate_eur": null,
|
||||
"risk_estimate_eur": null,
|
||||
"cost_estimate": "Unpriced incremental execution and recovery costs on existing infrastructure.",
|
||||
"risk_estimate": "Unpriced coordination outage, hook lifetime, lock mapping and recovery; reviewed conditional limits stop for attended owner on unknown state.",
|
||||
"supervisor": "Bernd Worsch",
|
||||
"approval_ref": null,
|
||||
"approved_revision": null,
|
||||
"approved_digest_sha256": null,
|
||||
"executed_revision": null,
|
||||
"executed_digest_sha256": null,
|
||||
"refinement_or_rescue": true,
|
||||
"promotion_evidence": false,
|
||||
"related_proposal_id": "STATE-WP-0095-T06-cluster-frozen-receiving-r1",
|
||||
"reason": "Separate new-code runtime request follows retained ordinary-pipeline and stale-installed-client failures. Six source refinements and real writeback regression remain visible; no extra success or authority is inferred.",
|
||||
"revision_history": [
|
||||
{
|
||||
"revision": 1,
|
||||
"digest_sha256": "81d365926fc585a186955d8c98ee83501fd3cec12135b2256d71b46a75097932",
|
||||
"outcome": "not_executed",
|
||||
"refinement": "Normal secret scan flagged probe source-hash metadata; original retained locally and by digest."
|
||||
},
|
||||
{
|
||||
"revision": 2,
|
||||
"digest_sha256": "5d0ddebc21bcb035809cc8b57f4c2e1ba8ed09204be5b965460e178a90913f1e",
|
||||
"outcome": "not_executed",
|
||||
"refinement": "Typed module/SHA256 records; unchanged runtime and probe logic."
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load diff
|
|
@ -0,0 +1,34 @@
|
|||
"""Read-only final source/remote/Hub binding check, retaining only public identifiers."""
|
||||
from pathlib import Path
|
||||
import hashlib,json,re,subprocess,urllib.request,yaml
|
||||
here=Path(__file__).resolve().parent
|
||||
specs=[('state-hub','STATE-WP-0095','4c03c9d2c6a47f5c7247473f74b2e2f188b787bd',10),('repo-manager','RMGR-WP-0019','1dacdd4a31c8e9b1bb1ddfb0c349dfb87e29e8cd',6),('repo-manager','RMGR-WP-0021','1dacdd4a31c8e9b1bb1ddfb0c349dfb87e29e8cd',5),('railiance-cluster','RCLUSTER-WP-0018','6ae3f847c83da3402883453ee7110457bfb2d0d6',5)]
|
||||
def git(root,*a):return subprocess.check_output(['git','--no-optional-locks','-C',str(root),*a],stderr=subprocess.PIPE,timeout=30).decode().strip()
|
||||
def get(path):return json.load(urllib.request.urlopen('http://127.0.0.1:8000'+path,timeout=20))
|
||||
health=get('/state/health');assert health['instance_role']=='primary' and health['instance_label']=='railiance01'
|
||||
rows=[];snapshots={};targets={'NK-WP-0049-T33':'56c8d469-7a10-5d50-a30e-95cbf3cd4756'}
|
||||
for repo,wp,head,count in specs:
|
||||
root=Path('/home/worsch')/repo;assert git(root,'rev-parse','HEAD')==head
|
||||
paths=list((root/'workplans').glob(wp+'-*.md'));assert len(paths)==1;path=paths[0];raw=path.read_text();assert git(root,'show',head+':'+str(path.relative_to(root)))==raw.strip()
|
||||
front=yaml.safe_load(raw.split('---',2)[1]);tasks=[yaml.safe_load(v) for v in re.findall(r'```task\n(.*?)\n```',raw,re.S)];assert len(tasks)==count
|
||||
for task in tasks:targets[task['id']]=task['state_hub_task_id']
|
||||
rows.append(dict(repo=repo,wp=wp,head=head,source_path=str(path),front=front,tasks=tasks,source_sha256=hashlib.sha256(path.read_bytes()).hexdigest()))
|
||||
result=[]
|
||||
for item in rows:
|
||||
repo=item['repo'];root=Path('/home/worsch')/repo
|
||||
remote=git(root,'ls-remote','origin','refs/heads/main').split()[0];assert remote==item['head']
|
||||
snapshot=snapshots.setdefault(repo,get('/repos/'+repo+'/work-record-projection/snapshot'))
|
||||
plan=next(p for p in snapshot['workplans'] if p['id']==item['front']['state_hub_workstream_id']);assert plan['status']==item['front']['status']
|
||||
actual=[t for t in snapshot['tasks'] if t.get('workplan_id',t.get('workstream_id'))==plan['id']];assert len(actual)==len(item['tasks']);byid={t['id']:t for t in actual}
|
||||
for task in item['tasks']:
|
||||
t=byid[task['state_hub_task_id']];assert t['record_id']==task['id'] and t['status']==task['status']
|
||||
if 'needs_human' in task:assert bool(t.get('needs_human'))==task['needs_human']
|
||||
expected={(t['state_hub_task_id'],targets[d],'starts_after') for t in item['tasks'] for d in t.get('depends_on',[]) if d in targets}
|
||||
edges=[e for e in snapshot['dependencies'] if e['from_workplan_id']==plan['id'] and e.get('from_task_id')]
|
||||
observed={(e['from_task_id'],e.get('to_task_id'),e['relationship_type']) for e in edges}
|
||||
assert observed<=expected,'undeclared-projected-edge'
|
||||
required_pairs={'RMGR-WP-0019':[('RMGR-WP-0019-T06','STATE-WP-0095-T10')],'STATE-WP-0095':[('STATE-WP-0095-T07','STATE-WP-0095-T10')],'RCLUSTER-WP-0018':[('RCLUSTER-WP-0018-T03','RCLUSTER-WP-0018-T02'),('RCLUSTER-WP-0018-T04','RCLUSTER-WP-0018-T02'),('RCLUSTER-WP-0018-T04','RCLUSTER-WP-0018-T03')]}
|
||||
assert all((targets[a],targets[b],'starts_after') in observed for a,b in required_pairs.get(item['wp'],[])),'required-current-edge-missing'
|
||||
result.append({'repo':repo,'workplan_id':item['wp'],'commit':item['head'],'remote_exact':True,'source_sha256':item['source_sha256'],'status':plan['status'],'tasks':[{k:t[k] for k in ['id','record_id','status','needs_human'] if k in t} for t in actual],'projected_edges':[{'from_task_id':a,'to_task_id':b,'relationship_type':c} for a,b,c in sorted(observed)],'unprojected_source_declarations':[{'from_task_id':a,'to_task_id':b,'relationship_type':c} for a,b,c in sorted(expected-observed)]})
|
||||
v={'schema':'custodian.rollout-owner-bindings.v1','status':'verified','primary':'primary/railiance01','task_bindings':sum(len(r['tasks']) for r in result),'rows':result,'runtime_deployed_source':'51bc70d1ff8f25450a8650d8e50caf053093a02e','successor_runtime_source_not_deployed':'c103cbf3c8bed5dba87a03e320595ddded9301a3','native_target_gates_closed':0}
|
||||
(here/'rollout-owner-bindings.json').write_text(json.dumps(v,indent=2)+'\n');print(json.dumps({'status':'verified','task_bindings':v['task_bindings']}))
|
||||
|
|
@ -772,3 +772,134 @@ driver, external message or worker wake was created. The
|
|||
verifies all 58 NetKingdom and eight State Hub task IDs/UUIDs/statuses against
|
||||
source, plus exact remote heads. Earlier Repo Manager/Secrets readback verifies
|
||||
nine more owner bindings and the two Secrets dependency edges.
|
||||
|
||||
|
||||
## Approved coordination receiver execution, 2026-10-17
|
||||
|
||||
This checkpoint supersedes the pending-rollout state recorded above. The founder's
|
||||
“good, go ahead” approved exact revision 4 of
|
||||
`STATE-WP-0095-T06-cluster-frozen-receiving-r1`, digest
|
||||
`63a02e8296d126c0158b7eb2c4ce79c7eeb6f8d6f61298d473c1065c7557ba32`.
|
||||
Decision `e3798419-8aa9-5425-8c08-20df6bd82a19` records
|
||||
`ADMINISTER @ realm:kubernetes/railiance01`, `activation=APPROVED` for that
|
||||
proposal and its exact conditional recovery, with no autonomy grant.
|
||||
|
||||
The owner Helm upgrade succeeded as revision 76. API and MCP are Ready on the
|
||||
approved image digest `c802690ee1811b3d77df4077936f9cdced1385514e8673fcbc9232b84d645015`;
|
||||
primary/railiance01 reports applied and expected schema `c4d5e6f7a8b9`.
|
||||
Delivered historical projection module hash matches the reviewed image. Full-row
|
||||
hashes and column sets of all three historical workplans and fifteen tasks are
|
||||
identical before and after deployment. Five actual native receiving cases pass:
|
||||
preserve, foreign holder, missing task, nonterminal parent and nonterminal task.
|
||||
Every probe rolled back; zero commits and a fresh-transaction full-row comparison
|
||||
confirm preservation. Helm succeeded and the migration Job disappeared after
|
||||
its exact UID and owned Pod were observed; no Job Succeeded event is claimed.
|
||||
No recovery was needed. The exact owned staging archive/directory was removed.
|
||||
|
||||
Only after these observations was the frozen seven-file registrar source applied.
|
||||
Canonical focused checks pass 47; the actual read-only Cluster allocator preview
|
||||
proposes exactly seven missing UUID fields in the new WP0018 and one existing
|
||||
ADHOC task. Fifteen invalid historical labels and five collisions remain reported;
|
||||
no archive rewrite, direct database UUID repair or broad syntax exception occurred.
|
||||
Owner publication and receiving follow-through are recorded separately below.
|
||||
|
||||
Evidence: `docs/changes/netkingdom-target-2026-10-17/receiver-rollout-r4/verified-receiving-return.json`
|
||||
and its hash-bound actual native receipts; registrar source/application and preview
|
||||
receipts in `registrar-followthrough-r1/`. The same original supervision trial
|
||||
retains all preparation revisions and failures; accepted-revised execution earns
|
||||
no unchanged-success credit. All sixteen native target gates remain open.
|
||||
|
||||
|
||||
## Ordinary Cluster publication and retained acceptance failure, 2026-10-17
|
||||
|
||||
Cluster owner commit `c562d7134c38679952a8ffd17a8a893a900aef0d` is published and
|
||||
reconciled on primary/railiance01 at the exact expected/derived revision. WP0018's
|
||||
five task ID/UUID/status bindings and three internal edges match source and the
|
||||
remote. Exactly seven missing fields were assigned by the normal managed path,
|
||||
including one existing ADHOC task field. All three frozen archive hashes remain
|
||||
unchanged, and original staged/dirty generated files were restored exactly.
|
||||
Registrar source admission `70cd7549` is published and verified, with T05 done;
|
||||
source preparation and actual Cluster acceptance remain separate outcomes.
|
||||
|
||||
The stronger full-row guard FAILED after the required legacy deep consistency
|
||||
pass: the three historical parent hashes changed, while all fifteen task full
|
||||
rows remain identical. The native forge projection reports preservation, but
|
||||
that does not establish preservation for the whole pipeline. Source review found
|
||||
that `PUT /workplans/index/bindings` writes backing fields and a new sync timestamp
|
||||
without consulting the frozen-history guard; ORM update timestamps also advance.
|
||||
The checker calls this route even during checks. Only whole-row baseline hashes
|
||||
were retained, so exact changed columns/values cannot be reconstructed from the
|
||||
baseline. No guessed timestamp or database restoration is performed.
|
||||
|
||||
This later failure does not erase the earlier passing rollout and rollback-only
|
||||
probe results. It prevents RMGR-WP-0019-T06 and STATE-WP-0095-T07 completion.
|
||||
The existing State Hub owner record carries the source guard and regression
|
||||
follow-up plus its separate reviewed runtime-delivery obligation. Source edits,
|
||||
fixtures and successful publication do not stand in for that new native return.
|
||||
No further production rollout is authorized by the earlier revision-4 approval.
|
||||
|
||||
Evidence: `docs/changes/netkingdom-target-2026-10-17/cluster-publication-readback.json`,
|
||||
`railiance-cluster-projection.json`, and
|
||||
`receiver-rollout-r4/ordinary-pipeline-preservation-finding.json`, including the
|
||||
retained `post-publication-full-row-hashes-FAILED.json` and exact archive checks.
|
||||
All sixteen native target gates remain open.
|
||||
|
||||
|
||||
## Verified installed-client repair and exact runtime successor, 2026-10-17
|
||||
|
||||
State Hub source guards and real writeback regression are published through
|
||||
`c103cbf3c8bed5dba87a03e320595ddded9301a3`; the later WP-only checkpoint is
|
||||
`9eaa36143ea18111c522ea14d32978495b4e5030`. Canonical guard checks pass 102,
|
||||
independent review passes 109, and five actual disposable Git checks verify
|
||||
file-scoped commits with unrelated staged/dirty state and hook refusal preserved.
|
||||
Normal chart rendering and classification checks pass. The first attempted
|
||||
client rerun loaded an older installed package and failed again; its actual
|
||||
receipts stay retained. The installed owner package was then refreshed and its
|
||||
loaded checker hash verified against R6 source before the next run.
|
||||
|
||||
The corrected actual ordinary Cluster maintenance passes: 20/20 ordinary
|
||||
bindings, three frozen bindings omitted, and all eighteen CURRENT full-row
|
||||
hashes unchanged before/after. Original failed parent hashes are not restored
|
||||
or relabeled as successes. The old writeback helper also included an unrelated
|
||||
staged brief during legitimate C23 activation. Forward correction
|
||||
`6ae3f847c83da3402883453ee7110457bfb2d0d6` preserves active WP18, restores the
|
||||
prior committed brief, and reinstates its exact original staged/worktree bytes;
|
||||
dirty WORK-RECORDS and archive hashes are preserved. No history was rewritten.
|
||||
Repo Manager `1dacdd4a31c8e9b1bb1ddfb0c349dfb87e29e8cd` retains T05 done/T06 wait
|
||||
and projects T06's actual dependency on STATE-WP-0095-T10. State Hub T07 also
|
||||
waits on T10; all ten own task UUIDs remain exact, T09 done/T10 human wait.
|
||||
|
||||
The normal CI guard image at
|
||||
`sha256:4cc4ce17bbcdb1b66132d07c5b7b741f46df83124ef1c8403ffabdafba6993d1`
|
||||
is inspected read-only against runtime source `c103cbf`. Selected guard/receiver/
|
||||
migration/build files match; package metadata and hub-core source hashes equal
|
||||
the deployed image's observations. Exact pinned-package reuse-values server
|
||||
dry-run passes eight identities and only three image changes. Fresh explicit
|
||||
target/headroom/schema checks pass. The prepared eight native cases enforce
|
||||
commit interception and rollback; their actual schema/interception contracts
|
||||
are checked without a DB connection, but these new native cases are not executed.
|
||||
|
||||
Exact successor `STATE-WP-0095-T10-frozen-bindings-guard-r1` revision 1 is pending,
|
||||
metadata digest `81d365926fc585a186955d8c98ee83501fd3cec12135b2256d71b46a75097932`,
|
||||
decision `df703266-6719-4c04-ae1b-ba9afd3bca1c`. It requests scoped new-image
|
||||
approval, current-baseline acceptance with the old failure retained as an
|
||||
exception, and exact conditional recovery/rollback to Helm 76. Unknown EUR
|
||||
cost/risk or Job/DB mapping is not a free or bounded exposure. The prior
|
||||
revision-4 approval does not approve this successor. Current runtime remains
|
||||
healthy Helm 76 on the approved `51bc70d` image; no new API guard delivery or
|
||||
native security-gate closure is inferred. The original supervision record
|
||||
retains successful earlier-stage execution plus later failures; its new request
|
||||
is pending/not executed and grants no authority.
|
||||
|
||||
Evidence: `docs/changes/netkingdom-target-2026-10-17/guard-successor-review-r1/`,
|
||||
`receiver-rollout-r4/before-verified-client.json`, `after-verified-client.json`,
|
||||
`verified-loaded-client.json`, `verified-client-cluster-consistency.json`,
|
||||
`verified-client-cluster-projection.json`, the exact owner publication packets
|
||||
and `rollout-owner-bindings.json`. The original receiver/registrar case is
|
||||
satisfied; the successor attaches to the existing retirement driver and stops
|
||||
at the human gate. TLS metadata work remains an owner wait. No worker was woken.
|
||||
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`.
|
||||
|
|
|
|||
|
|
@ -961,3 +961,134 @@ action is approved or executed. Four coordination receipts attach foreign waits
|
|||
without messages or worker wakes. Source/remote/Hub readback verifies 66 new
|
||||
checkpoint owner bindings plus the nine Repo Manager/Secrets bindings; source
|
||||
counts and native acceptance remain separate.
|
||||
|
||||
|
||||
## Approved receiver execution, 2026-10-17
|
||||
|
||||
This checkpoint supersedes the pending-rollout state recorded above. The founder's
|
||||
“good, go ahead” approved exact revision 4 of
|
||||
`STATE-WP-0095-T06-cluster-frozen-receiving-r1`, digest
|
||||
`63a02e8296d126c0158b7eb2c4ce79c7eeb6f8d6f61298d473c1065c7557ba32`.
|
||||
Decision `e3798419-8aa9-5425-8c08-20df6bd82a19` records
|
||||
`ADMINISTER @ realm:kubernetes/railiance01`, `activation=APPROVED` for that
|
||||
proposal and its exact conditional recovery, with no autonomy grant.
|
||||
|
||||
The owner Helm upgrade succeeded as revision 76. API and MCP are Ready on the
|
||||
approved image digest `c802690ee1811b3d77df4077936f9cdced1385514e8673fcbc9232b84d645015`;
|
||||
primary/railiance01 reports applied and expected schema `c4d5e6f7a8b9`.
|
||||
Delivered historical projection module hash matches the reviewed image. Full-row
|
||||
hashes and column sets of all three historical workplans and fifteen tasks are
|
||||
identical before and after deployment. Five actual native receiving cases pass:
|
||||
preserve, foreign holder, missing task, nonterminal parent and nonterminal task.
|
||||
Every probe rolled back; zero commits and a fresh-transaction full-row comparison
|
||||
confirm preservation. Helm succeeded and the migration Job disappeared after
|
||||
its exact UID and owned Pod were observed; no Job Succeeded event is claimed.
|
||||
No recovery was needed. The exact owned staging archive/directory was removed.
|
||||
|
||||
Only after these observations was the frozen seven-file registrar source applied.
|
||||
Canonical focused checks pass 47; the actual read-only Cluster allocator preview
|
||||
proposes exactly seven missing UUID fields in the new WP0018 and one existing
|
||||
ADHOC task. Fifteen invalid historical labels and five collisions remain reported;
|
||||
no archive rewrite, direct database UUID repair or broad syntax exception occurred.
|
||||
Owner publication and receiving follow-through are recorded separately below.
|
||||
|
||||
Evidence: `docs/changes/netkingdom-target-2026-10-17/receiver-rollout-r4/verified-receiving-return.json`
|
||||
and its hash-bound actual native receipts; registrar source/application and preview
|
||||
receipts in `registrar-followthrough-r1/`. The same original supervision trial
|
||||
retains all preparation revisions and failures; accepted-revised execution earns
|
||||
no unchanged-success credit. All sixteen native target gates remain open.
|
||||
|
||||
|
||||
## Ordinary Cluster publication and retained acceptance failure, 2026-10-17
|
||||
|
||||
Cluster owner commit `c562d7134c38679952a8ffd17a8a893a900aef0d` is published and
|
||||
reconciled on primary/railiance01 at the exact expected/derived revision. WP0018's
|
||||
five task ID/UUID/status bindings and three internal edges match source and the
|
||||
remote. Exactly seven missing fields were assigned by the normal managed path,
|
||||
including one existing ADHOC task field. All three frozen archive hashes remain
|
||||
unchanged, and original staged/dirty generated files were restored exactly.
|
||||
Registrar source admission `70cd7549` is published and verified, with T05 done;
|
||||
source preparation and actual Cluster acceptance remain separate outcomes.
|
||||
|
||||
The stronger full-row guard FAILED after the required legacy deep consistency
|
||||
pass: the three historical parent hashes changed, while all fifteen task full
|
||||
rows remain identical. The native forge projection reports preservation, but
|
||||
that does not establish preservation for the whole pipeline. Source review found
|
||||
that `PUT /workplans/index/bindings` writes backing fields and a new sync timestamp
|
||||
without consulting the frozen-history guard; ORM update timestamps also advance.
|
||||
The checker calls this route even during checks. Only whole-row baseline hashes
|
||||
were retained, so exact changed columns/values cannot be reconstructed from the
|
||||
baseline. No guessed timestamp or database restoration is performed.
|
||||
|
||||
This later failure does not erase the earlier passing rollout and rollback-only
|
||||
probe results. It prevents RMGR-WP-0019-T06 and STATE-WP-0095-T07 completion.
|
||||
The existing State Hub owner record carries the source guard and regression
|
||||
follow-up plus its separate reviewed runtime-delivery obligation. Source edits,
|
||||
fixtures and successful publication do not stand in for that new native return.
|
||||
No further production rollout is authorized by the earlier revision-4 approval.
|
||||
|
||||
Evidence: `docs/changes/netkingdom-target-2026-10-17/cluster-publication-readback.json`,
|
||||
`railiance-cluster-projection.json`, and
|
||||
`receiver-rollout-r4/ordinary-pipeline-preservation-finding.json`, including the
|
||||
retained `post-publication-full-row-hashes-FAILED.json` and exact archive checks.
|
||||
All sixteen native target gates remain open.
|
||||
|
||||
|
||||
## Verified installed-client repair and exact runtime successor, 2026-10-17
|
||||
|
||||
State Hub source guards and real writeback regression are published through
|
||||
`c103cbf3c8bed5dba87a03e320595ddded9301a3`; the later WP-only checkpoint is
|
||||
`9eaa36143ea18111c522ea14d32978495b4e5030`. Canonical guard checks pass 102,
|
||||
independent review passes 109, and five actual disposable Git checks verify
|
||||
file-scoped commits with unrelated staged/dirty state and hook refusal preserved.
|
||||
Normal chart rendering and classification checks pass. The first attempted
|
||||
client rerun loaded an older installed package and failed again; its actual
|
||||
receipts stay retained. The installed owner package was then refreshed and its
|
||||
loaded checker hash verified against R6 source before the next run.
|
||||
|
||||
The corrected actual ordinary Cluster maintenance passes: 20/20 ordinary
|
||||
bindings, three frozen bindings omitted, and all eighteen CURRENT full-row
|
||||
hashes unchanged before/after. Original failed parent hashes are not restored
|
||||
or relabeled as successes. The old writeback helper also included an unrelated
|
||||
staged brief during legitimate C23 activation. Forward correction
|
||||
`6ae3f847c83da3402883453ee7110457bfb2d0d6` preserves active WP18, restores the
|
||||
prior committed brief, and reinstates its exact original staged/worktree bytes;
|
||||
dirty WORK-RECORDS and archive hashes are preserved. No history was rewritten.
|
||||
Repo Manager `1dacdd4a31c8e9b1bb1ddfb0c349dfb87e29e8cd` retains T05 done/T06 wait
|
||||
and projects T06's actual dependency on STATE-WP-0095-T10. State Hub T07 also
|
||||
waits on T10; all ten own task UUIDs remain exact, T09 done/T10 human wait.
|
||||
|
||||
The normal CI guard image at
|
||||
`sha256:4cc4ce17bbcdb1b66132d07c5b7b741f46df83124ef1c8403ffabdafba6993d1`
|
||||
is inspected read-only against runtime source `c103cbf`. Selected guard/receiver/
|
||||
migration/build files match; package metadata and hub-core source hashes equal
|
||||
the deployed image's observations. Exact pinned-package reuse-values server
|
||||
dry-run passes eight identities and only three image changes. Fresh explicit
|
||||
target/headroom/schema checks pass. The prepared eight native cases enforce
|
||||
commit interception and rollback; their actual schema/interception contracts
|
||||
are checked without a DB connection, but these new native cases are not executed.
|
||||
|
||||
Exact successor `STATE-WP-0095-T10-frozen-bindings-guard-r1` revision 1 is pending,
|
||||
metadata digest `81d365926fc585a186955d8c98ee83501fd3cec12135b2256d71b46a75097932`,
|
||||
decision `df703266-6719-4c04-ae1b-ba9afd3bca1c`. It requests scoped new-image
|
||||
approval, current-baseline acceptance with the old failure retained as an
|
||||
exception, and exact conditional recovery/rollback to Helm 76. Unknown EUR
|
||||
cost/risk or Job/DB mapping is not a free or bounded exposure. The prior
|
||||
revision-4 approval does not approve this successor. Current runtime remains
|
||||
healthy Helm 76 on the approved `51bc70d` image; no new API guard delivery or
|
||||
native security-gate closure is inferred. The original supervision record
|
||||
retains successful earlier-stage execution plus later failures; its new request
|
||||
is pending/not executed and grants no authority.
|
||||
|
||||
Evidence: `docs/changes/netkingdom-target-2026-10-17/guard-successor-review-r1/`,
|
||||
`receiver-rollout-r4/before-verified-client.json`, `after-verified-client.json`,
|
||||
`verified-loaded-client.json`, `verified-client-cluster-consistency.json`,
|
||||
`verified-client-cluster-projection.json`, the exact owner publication packets
|
||||
and `rollout-owner-bindings.json`. The original receiver/registrar case is
|
||||
satisfied; the successor attaches to the existing retirement driver and stops
|
||||
at the human gate. TLS metadata work remains an owner wait. No worker was woken.
|
||||
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`.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue