moailisted

## Pre-execution Context !`git status --porcelain 2>/dev/null || true` !`git branch --show-current 2>/dev/null || true` ## Essential Files .moai/config/config.yaml --- ## Authority References Rules and constraints governing all workflows are always loaded from these sources. Do NOT duplicate their content here: - Core identity, orchestration principles, agent catalog: CLAUDE.md - Quality gates, security boundaries: .claude/rules/moai/core/moai-constitution.md - SPEC workflow phases, token budgets: .claude/rules/moai/workflow/spec-workflow.md - Development methodologies (DDD/TDD): .claude/rules/moai/workflow/spec-workflow.md (Run Phase section) - Agent definitions: See CLAUDE.md Section 4. For agent creation, use builder-harness subagent (artifact_type=agent). - @MX tag rules and protocol: .claude/rules/moai/workflow/mx-tag-protocol.md --- ## Routing Observation Ledger When dispatching a subcommand or workflow, the orchestrator records the routing decision to the append-only routing-ledger (`.moai/state/routing-ledger.jsonl`) via `moai harness ledger record` at dispatch time — the request text is piped via stdin and only a privacy-preserving digest is stored, never verbatim user text. As the routed pipeline reaches gate points, machine evidence is appended via `moai harness ledger evidence` (gate exits, audit verdicts, verify-log paths). Outcome is never supplied as an input; it is finalized from machine evidence only. This observation is opt-in and fail-open — it ne