harness-discoverylisted

# harness-discovery Keep questions product-facing and one at a time. Surface tradeoffs and success criteria, not low-level implementation choices. - Separate facts, assumptions, constraints, and unknowns. - Turn a desired feature into observable user journeys and acceptance criteria. - Avoid choosing an architecture before validating the product decision. - Before closing a technical design, request an adversarial attack of its risks. Use `.codex/skills/harness-delivery/references/delivery-contract.md` for the entry tier and `.codex/skills/harness-rules/references/governance-contract.md` for adversarial scope.