# 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:

```bash
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:

```bash
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:

```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
python3 -m pytest tools/playbook-capability-contract/tests
```