Write

<!-- Generated from harness_core; do not hand-edit. -->

Use /write for: Produce evidence-grounded core docs and optionally route manuscript work.

Runtime Contract

1. Read harness_core/recipes/write.yaml and identify the current Action.
2. Resolve Capability Packs from that Action plus the active Assurance Profile.
3. Load only the resolved Packs. Ordinary Actions allow 3; declared high-risk Actions allow 5 and must record the escalation reason.
4. Execute, validate postconditions, and record semantic Runtime Events and Gate Evidence. Do not infer success from artifact existence.
5. After durable changes under docs/, run python tooling/harness.py docs sync --json; this establishes or validates the live docs link. Git hooks only repair the link after checkout, merge, commit, or rewrite.
6. Pause only at a declared interrupt or human-stop boundary.

Actions:

• write.compose: documentation-and-publication
• write.validate: documentation-and-publication

Default profile: reproducible.

Start interactively with python tooling/harness.py write --json; use --auto for a bounded fresh Agent per Action. Inspect with python tooling/harness.py status --json. Legacy internal sources are inactive migration/debug references, not normal routes.