Section overview · guide
FPAT Lite & agent governance
FPAT Lite routes every task through exactly one proportionate command contract, with shared safety rules and executed evidence. The arrows below are the recommended order, not a mandatory state machine — a tiny fix may use prime → implement → validate.
One command at a time
A command may recommend the next one, but it must not silently cross into a higher-mutation mode. Remote writes always need current, named approval — dry-run labels do not override documented command behavior.
Understand the toolkit
WorkflowgovernanceCommand selection, transitions, artifacts, and resumption.Command contractsreferenceSix contracts, each with purpose, inputs, and output shape.Rulesinvariants15 core invariants, mutation classification, evidence rules.Knowledge baseknowledgeArchitecture, design rationale, compatibility, glossary.AGENTS.mdagentsRepository agent guide: startup, authority, status vocabulary.Scope decisiondecisionWhy FPAT Lite stays a shared modular core (Decision 0001).Agent compatibilityknowledgeHow Codex and Claude Code invoke the same contracts.FPAT workflow graphgraphThe command lifecycle as a typed, provenanced graph.