Software Factory

You end with: factory/line-map.md — your delivery line as stages, queues, gates and the named approver for each gate

You end with: factory/release-slice.md — one release split into issues with a dependency map, a size cap per PR and a plan sign-off line

You end with: factory/autonomy-map.md — each lane of your repo with its autonomy level, the check that earns it and the revert path

You end with: factory/review-gate.md — reviewer config read from the base branch, round cap, finding states, and who approves per tier

You end with: factory/holdout-set.md — 3 hidden scenarios with hand-computed expected figures, where they are stored, and the red control for each

You end with: factory/protected-paths.md — the protected path list with patterns, who may change each, and the server-side rule that enforces it

You end with: factory/risk-lanes.md — three lanes with exact entry tests, the human action for each, the audit sample rate and the revert-rate tripwire

You end with: factory/merge-gate-charter.md — review gate, holdout set, protected paths and risk lanes merged into one charter for one repo, with a red control for each gate

You end with: factory/blueprint.md — your line as a node list marking each node deterministic or agent, the retry cap and the exit for each

You end with: factory/readiness-score.md — a tiered checklist scored for one repo, with the tier it unlocks and the proposed-issue rule for a tier drop

You end with: factory/release-path.md — merge target, staging validation, canary checks with false-positive tracking, rollback owner and the human release step

You end with: factory/readiness-scorecard.md — a repo scored against the readiness list, with the blueprint nodes and release path attached, and the tier it earns

You end with: factory/registry.md — every skill and agent role with owner, version, status, lifecycle and the distinct-version count

You end with: factory/identity-ledger.md — each agent identity with its sponsor, scope, branch rights and the rule that stops self-approval

You end with: factory/context-map.md — each context fact the line needs, where it lives, who keeps it fresh and which gate reads it

You end with: factory/scoreboard.md — six metrics with definition, denominator, guardrail pairing and the tripwire that pauses a lane

You end with: factory/incident-lessons.md — five incidents each turned into a gate test, the control that blocks it and its red control

You end with: factory/charter.md — one repo's complete factory charter: line map, lanes, gates, readiness tier, identities, context map, scoreboard and the incident tests, with the single lane you will switch on first

You end with: factory/adopt/anthropic.md — the mechanics you adopt from the Anthropic flow, mapped to your lanes, with the one you refuse and why

You end with: factory/adopt/openai.md — ticket states, workpad and land-step rules adapted to your tracker

You end with: factory/adopt/stripe.md — your line's blueprint with deterministic and agent nodes marked, copied from the Stripe shape

You end with: factory/adopt/spotify.md — a fleet-change plan with verifier, stop hook and your own veto rule

You end with: factory/adopt/ramp.md — an identity and approval rule so nobody approves their own agent's change

You end with: factory/adopt/shopify.md — a visibility and proof-of-work rule for your agent threads

You end with: factory/adopt/uber.md — an evidence-table for reviewers and a cost metric plan

You end with: factory/adopt/cloudflare.md — risk tiers that decide how many reviewer agents run, with a cost ceiling

You end with: factory/adopt/coinbase.md — a plan sign-off and PR size rule

You end with: factory/adopt/intercom.md — an eligibility rule for no-human approval with size limits, tripwires and a sample audit

You end with: factory/adopt/small-flows.md — one borrowed mechanic per company, each with a test

You end with: factory/adopt/comparison-board.md — a seven-dimension comparison of the factories you studied, plus the pattern you copy and the gap you measure yourself.

You end with: factory/improve/loop-map.md — the executing loop and the improving loop on one page: the signal each reads, the artifact each writes, and the trigger between them

You end with: factory/improve/skill-change.md — one proposal format, one review gate, one revert line and a weekly churn budget for changes to the files that govern the agents

You end with: factory/improve/memory-log.md — the memory schema, the write and read paths, the provenance rule, and the three curation events that keep a store honest

You end with: factory/improve/routing-rules.yaml — a task-class table with the model per class, the classes that may never be downgraded, and the benchmark card that earns each rule

You end with: factory/adopt/warp.md — a fill-in plan that borrows Warp's improvement stack: scorer, self-improvement run, memory store and router, each with your own threshold, reviewer and test

You end with: factory/improve/rollout.md — a six-week sequence with a gate at the end of each week, the file each week produces, and the condition that stops the rollout