Skip to content
~/agentops
GitHubInstall
// 12-FACTOR AGENTOPS

Don't run production
on vibes.

Agents generate code with no record of what was tried, no gate it had to pass, no proof it works. Twelve operating rules close that gap. Before a change counts as done, something that didn't write it has to check it. No verdict, not done.

Run it in your agent →GitHub ↗Read the 12 factors →

// the 12 factors

all 12 →

Four phases a unit of work passes through — Prepare, Bound, Select, Govern — and Govern feeds back into Prepare.

PREPAREI - IIIset up the environment
IContextPut only task-relevant context in the window.IITrackKeep work state, decisions, and learnings in git.IIIScopeGive each agent one bounded job and a fresh window.
BOUNDIV - VIconstrain what may act
IVPrivilegeAct inside a least-privilege envelope untrusted input cannot widen.VResearchInspect the integration surface before writing code.VIIsolateSeparate concurrent workers by workspace, context, and state.
SELECTVII - IXdecide what survives
VIIValidateThe worker reports evidence; an independent checker writes the verdict.VIIILockTurn validated work into the new baseline.IXExtractRecord what the session learned, not only what it changed.
GOVERNX - XIIsteer and feed back
XCompoundWire learnings — positive and negative — back into future work.XISuperviseEscalate up a clear tree; a stuck job goes to a fresh agent.XIIMeasureTrack fitness toward goals, not agent activity.

// the three gaps they close

The failure modes that make agent work unreliable, each closed by a named surface.

G1JUDGMENTPressure-test plans before code.closed by /pre-mortem · /validate · /council
G2DURABLE LEARNINGSolved problems stay solved: the measured, still-unproven bet.closed by /post-mortem · ao search · ao lookup
G3LOOP CLOSUREShipped work compounds into the next session: measured, still unproven.closed by /post-mortem · the promotion ratchet · /rpi

// the bet

THE WAGER — Vendors will ship managed memory, review councils, and overnight learning loops natively; they will lock them to their runtime. Your corpus stays in .agents/ in your repo, runs on whichever harness you already pay for, and is portable across whichever frontier model wins next quarter.

Good architecture principles outlive every tool that implements them.
see the proof →
// your agent said done; something else proved it. the proof is yours.
the corpus stays yours