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

Console mapping: is v0.2 expressive enough (RBT-WP-0009-T05); RBT-WP-0005 decisions

Browse source 
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 295952@bnt-lap001
Assistant-Session: e93f64ad-516c-46eb-9666-aad8d300c477
This commit is contained in:
tegwick 2026-09-29 21:37:21 +02:00
parent 6d70f4d97d
commit f52a3e14f4
3 changed files with 120 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

16
workplans/RBT-WP-0005-legacy-adapter-and-console-migration.md
View file

@ -50,12 +50,12 @@ with a stub server.
```task
id: RBT-WP-0005-T03
status: todo
status: done
priority: high
state_hub_task_id: "dbb5553d-fb0c-5298-85c8-cebc9dd63312"
```
Classify the 5,300-line `security_bootstrap_console.py` into generic engine
Done 2026-09-29 (RBT-WP-0009-T05): `docs/console-mapping.md`. Classify the 5,300-line `security_bootstrap_console.py` into generic engine
concerns (record and state model, gates, stage derivation, copyable blocks,
approval phrase, localhost server) and NetKingdom-specific content (custody,
OpenBao ceremony, KeyCape, privacyIDEA checks). Output: a migration map with
@ -65,12 +65,13 @@ the tests that pin current behaviour.
```task
id: RBT-WP-0005-T04
status: todo
status: cancel
priority: medium
state_hub_task_id: "14261c00-65d0-55be-8ab2-bd81e579e20d"
```
Move the generic parts into `rtut` behind the run record. The console in
Cancelled 2026-09-29: extracting the console's engine now would freeze its workarounds into the engine, because v0.2 lacks conditional applicability, gate
recheck and outputs that feed later members (`docs/console-mapping.md` G1, G3, G7). It may return as part of a v0.3 design. Original scope: move the generic parts into `rtut` behind the run record. The console in
`net-kingdom` then imports them. Gate: the existing
`tools/security-bootstrap-console/tests` pass unchanged before and after, and
`make security-bootstrap-ui` behaves the same.
@ -79,13 +80,14 @@ Move the generic parts into `rtut` behind the run record. The console in
```task
id: RBT-WP-0005-T05
status: todo
status: done
priority: low
state_hub_task_id: "c54cfa35-1a34-5d5a-b85b-86ae8771dcfb"
```
With Bernd: keep the console as a permanent legacy pack, migrate its runbooks
to native packs, or a mix. Record as a decision.
Decided 2026-09-29 (Bernd, with RBT-WP-0009): the console stays a permanent legacy pack, launched unchanged. Its seven runbooks can become native v0.2
packs as separate content work (they need none of G1 to G7). Original question: keep the console as a permanent legacy pack, migrate its runbooks
to native packs, or a mix.
## Acceptance Criteria

4
workplans/RBT-WP-0009-finalize-the-runbook-tutorials-workplans.md
View file

@ -77,11 +77,11 @@ refused (409). Added `rtut seal <file>` so an exported record can be verified an
```task
id: RBT-WP-0009-T05
status: todo
status: done
priority: high
```
`docs/console-mapping.md`: map the security bootstrap console's 6 stages, 14 gates, roles, subsystems, integrations, 12 artefacts
Done 2026-09-29. Verdict: the structure maps, the behaviour does not fully; seven gaps (G1 to G7) are the v0.3 candidates. `docs/console-mapping.md`: map the security bootstrap console's 6 stages, 14 gates, roles, subsystems, integrations, 12 artefacts
and 7 runbooks onto v0.2 and say honestly where a special case is needed. This is the acceptance evidence for the model. It closes
RBT-WP-0005-T03, records the decision to keep the console as a permanent legacy pack (T05), and moves the extraction (T04) to the backlog.