fix(discovery): project bootstrap metadata from owner entry
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 5s

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a140c4-354a-7823-8f0d-8f717397f786
This commit is contained in:
tegwick 2026-10-16 21:01:52 +02:00
parent d1dcfde527
commit 6927f5ec64
2 changed files with 32 additions and 4 deletions

View file

@ -4,7 +4,7 @@ domain: helix_forge
capabilities:
- id: capability.railiance.bootstrap-sequencing
name: Bootstrap sequencing contracts
summary: Bare-VM sequencing with NetKingdom identity backup recovery handoff.
summary: Bare-VM to estate sequence and handoff contract.
domain: infotech
status: draft
owner: railiance-bootstrap
@ -12,9 +12,6 @@ capabilities:
- security
- netkingdom
- framework-reuse
- backup
- restore
- disaster-recovery
vector: D3 / A0 / C1 / R0
path: registry/capabilities/capability.railiance.bootstrap-sequencing.md
consumption_modes:

View file

@ -0,0 +1,31 @@
---
id: RAIL-BOOT-WP-ADHOC-2026-10-16
type: workplan
title: "Reconcile bootstrap index with its owner entry"
domain: financials
repo: railiance-bootstrap
status: finished
owner: codex
created: "2026-10-16"
updated: "2026-10-16"
flavor: implementation
---
## Reconcile bootstrap index with its owner entry
```task
id: RAIL-BOOT-WP-ADHOC-2026-10-16-T01
status: done
priority: medium
```
Reconcile only bootstrap-sequencing index summary and tags with the existing authoritative capability entry. Old strict validation passed despite both differences; the reviewed validator refuses them until corrected. No new backup/recovery delivery or runtime acceptance is asserted.
Completed 2026-10-16 under the founder's NetKingdom target implementation demand
(CUST-WP-0080, TSA-11). Source review and exact before/after native CLI evidence:
`the-custodian/docs/changes/netkingdom-target-2026-10-16/improvement-loop-next/`.
The current 60-provider cohort has all 70 reviewed IDs exactly once; 3 field
mismatches across 2 capabilities become zero with the source corrections.
Native hosted refresh/readback and the accepted Activity/rein schedule remain
separate gates. No production change, model call, credential access or external
message was performed.