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

feat(orchestration): compose security scenarios
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 12:40:52 +02:00
parent ad46cc89fc
commit d96aab2321
20 changed files with 1464 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

13
tools/playbook-capability-contract/README.md
View file

@ -13,7 +13,7 @@ python3 tools/playbook-capability-contract/playbook_contract_validator.py \
../railiance-infra/capabilities/playbooks/railiance-infra.bootstrap-host.yaml
```
Validate and compose a sample scenario:
Validate and compose the legacy single-provider conformance sample:
```bash
python3 tools/playbook-capability-contract/playbook_contract_validator.py \
@ -21,6 +21,17 @@ python3 tools/playbook-capability-contract/playbook_contract_validator.py \
--scenario examples/playbook-capability-contract/scenario-s1-host-bootstrap.yaml
```
The `--scenario` path exists for v0.1 conformance compatibility. It refuses
ambiguous providers and unselected overrides, but it does not perform trust
sequencing or build a complete owner handoff. Use the canonical Security
Scenario Composer for deterministic multi-provider plans:
```bash
python3 tools/security-scenario-composer/security_scenario_composer.py \
--scenario examples/security-scenarios/c0-local-identity.yaml \
capabilities/playbooks/net-kingdom.local-identity.yaml
```
Run tests:
```bash