temple8: Instructions file for Codex

AGENTS.md

A Python project with the staged-contract workflow wired in (flow set, agents/skills/knowledge, CI, tooling). Drive the pipeline one state at a time through flowr.

Binding constraints

1. flowr is the single router. Every state change runs through flowr — no improvised routing, no skipping, no pre-empting a later state's work. One state's work is exactly its output artifacts; the next begins only when the orchestrator transitions.
2. The orchestrator dispatches; the dispatched agent does the work. The orchestrator MUST invoke the state's dispatch_to agent — it never authors the work. The handoff gives the agent: skills paths, input artifacts, output artifacts (write only here), and the evidence keys to assert. The agent produces the artifacts and asserts evidence; it does not transition.
3. The state's contract is binding. Read every input artifact before starting — missing means stop, not assume. Write only to output artifacts.
4. Assert only verified evidence; CI is the backstop. On a guarded transition flowr fires only on the dispatched agent's asserted evidence (--evidence k=v); assert nothing you did not check — CI catches the lie (ruff / pyright / mypy.stubtest / pytest). Unguarded transitions (discovery, explore) carry no flowr gate — the orchestrator verifies the output artifacts and the stakeholder's approval IS the gate.
5. Branch discipline. Match the state's git branch: discovery/explore/plan/deliver run on dev; build runs on feature/<session_id>, cut from dev at build entry. The contract surface is committed to dev at plan; the feature branch carries only the source implementation. Squash-merge feature/<session_id> → dev only under the whole-suite gates, then delete the branch. No dangling branches.
6. Every requirement traced. Each interview finding maps to a test or an explicit deferral; an untraced requirement is a gap the simulate gate rejects.
7. Only the orchestrator transitions. Producing artifacts is not finishing — the orchestrator's verified flowr transition is. A dispatched agent never runs flowr transition / flowr session, never assumes the next state, never declares the flow done.
8. Todo-first. The first action on entering a state is to create its one-state todo (the loop below). No todo = no work. Only the orchestrator holds the todo; regenerate it after every transition.