feat(orchestration): compose security scenarios

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02929-244b-7391-b933-c04010e8eedb

canon/standards/playbook-capability-contract_v0.1.md

@@ -6,7 +6,7 @@ domain: netkingdom
 status: accepted
 version: "0.1"
 created: "2026-05-22"
-updated: "2026-05-22"
+updated: "2026-08-23"
 scope: meta-orchestration
 adr:
   - docs/adr/ADR-0012-playbook-capability-contract-ownership.md
@@ -161,6 +161,12 @@ Security-sensitive and secret-reference parameters MUST NOT be
 `tenant_tunable`. Secret-reference defaults must be references or paths,
 not plaintext secret values.
 
+For executable validation, a `secret_reference` value MUST be a non-whitespace
+URI such as `openbao://kv/platform/example` or
+`kubernetes://namespace/name#key`, or an explicit absolute/relative path
+beginning with `/`, `./`, or `../`. Bare strings are rejected because the
+composer cannot distinguish them from secret values.
+
 Supported constraints:
 
 | Constraint | Applies to | Meaning |
@@ -244,7 +250,8 @@ separate playbook runner execute safely.
 
 ## Scenario Shape
 
-The validator supports a small scenario file for conformance demos:
+The validator supports a small scenario file for single-provider conformance
+demos:
 
 ```yaml
 id: scenario:s1-host-bootstrap-reference
@@ -263,6 +270,13 @@ Allowed scenario authorities are `platform`, `netkingdom`, and `tenant`.
 Tenant authority cannot override `platform_only`,
 `security_sensitive`, or `secret_reference` parameters.
 
+The demo composer refuses ambiguous providers and overrides aimed at unselected
+declarations. Deterministic multi-provider selection, explicit provider pins,
+trust sequencing, responsibility maps, and owner-routed readiness handoffs are
+defined by `security-scenario-composition_v0.1.md` and implemented by
+`tools/security-scenario-composer/`. Use that contract for operational planning;
+the demo path does not authorize or execute playbooks.
+
 ## Conformance
 
 A declaration conforms when it passes: