coulomb/net-kingdom
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
net-kingdom/tools/playbook-capability-contract/README.md
tegwick d96aab2321
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
feat(orchestration): compose security scenarios 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02929-244b-7391-b933-c04010e8eedb
2026-08-23 12:40:52 +02:00

1.3 KiB
Raw Blame History

Playbook Capability Contract Validator

Executable checks for canon/standards/playbook-capability-contract_v0.1.md.

Runtime dependency: Python 3.11+ with PyYAML. Fixture tests also require pytest.

Validate a declaration:

python3 tools/playbook-capability-contract/playbook_contract_validator.py \
  ../railiance-infra/capabilities/playbooks/railiance-infra.bootstrap-host.yaml

Validate and compose the legacy single-provider conformance sample:

python3 tools/playbook-capability-contract/playbook_contract_validator.py \
  ../railiance-infra/capabilities/playbooks/railiance-infra.bootstrap-host.yaml \
  --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:

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:

python3 -m pytest tools/playbook-capability-contract/tests