coulomb/net-kingdom
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(orchestration): compose KeyCape C1 and C2b
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02929-244b-7391-b933-c04010e8eedb
This commit is contained in:
tegwick 2026-08-23 13:24:55 +02:00
parent 21f477f699
commit 7f4e4e9f57
8 changed files with 133 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

14
tools/security-scenario-composer/README.md
View file

@ -17,6 +17,20 @@ python3 tools/security-scenario-composer/security_scenario_composer.py \
capabilities/playbooks/net-kingdom.local-identity.yaml
```
Compose the KeyCape C1 plus C2b reference from its authoritative sibling
declarations:
```bash
python3 tools/security-scenario-composer/security_scenario_composer.py \
--scenario examples/security-scenarios/c1-c2b-key-cape.yaml \
../key-cape/capabilities/playbooks/key-cape.lightweight-sso.yaml \
../key-cape/capabilities/playbooks/key-cape.privacyidea-token-authority.yaml
```
The scenario pins both provider ids. NetKingdom does not copy or reinterpret
their execution authority; the emitted plan retains `execution.permitted:
false` and routes readiness to the declaration owners.
Run tests:
```bash