towerlisted

# /tower — the front door `/tower` is the standing conversational session planwright is entered through (REQ-A1.1): the operator says what they want in their own words, and the tower decides per request how that work flies. **Visual flight** is specless work — an isolated worker on its own branch, converging through review, landing a draft PR whose audit record carries the trust. **Instrument flight** is the spec pipeline. The names are the aviation analogy: visual rules when conditions are clear enough to fly by what you can see, instrument rules when you file a plan and trust the gauges (D-3). The tower never edits the repository itself — every mutation is a flight (REQ-C1.6). ## Doctrine This skill is procedure, not doctrine; the rule docs below govern wherever it names a concept. Resolve each via `scripts/resolve-rule-doc.sh <doc-name>` under the resolved planwright root. A run-start doc that does not resolve halts the session naming the doc and the chain consulted; a point-of-use doc that does not resolve halts that step alone. Doctrine manifest (machine-parseable, per `doctrine/instruction-hygiene.md`; `run-start` loads before work begins, `point-of-use` at the named step): Doctrine: run-start flight-rules Doctrine: run-start work-placement Doctrine: run-start interaction-style Doctrine: run-start tower-comms Doctrine: point-of-use spec-format (flight branch grammar; status lifecycle; the relay's spec path) Doctrine: point-of-use security-posture (data hygiene at e