statecraft.
Catalog/aicortex

048-one-spec-per-pull-request

One spec per pull request; a session may land several specs in build order

Lifecycle approvedImplementation completeVerification unknownQualification unknown

The owner's decision of 2026-09-25 replaces the repository rule that code lands one spec per session with one spec per pull request: a session may land several specs, each on its own branch and in its own pull request, in build order. This spec amends spec 001 B-6 and carries the new sentence into the harness text that repeated the old one (AGENTS.md, CLAUDE.md, README.md, the orchestrator rule, the architect agent, and constitution principle III).

Read the full pinned specification ↗

Relationships

Claimed units

  • extends
    {
  "nature": "additive",
  "spec": "001-agentic-harness",
  "unit": {
    "kind": "file",
    "path": "AGENTS.md"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "001-agentic-harness",
  "unit": {
    "kind": "file",
    "path": "CLAUDE.md"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "001-agentic-harness",
  "unit": {
    "kind": "file",
    "path": "README.md"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "001-agentic-harness",
  "unit": {
    "kind": "file",
    "path": ".claude/rules/"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "001-agentic-harness",
  "unit": {
    "kind": "file",
    "path": ".claude/agents/"
  }
}

Source headings

  1. 048: One spec per pull request
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 4. Functional requirements
  6. 5. Acceptance criteria
  7. 6. Out of scope
  8. 7. Resolved decisions
  9. Verification

Frozen anchors

No frozen anchors declared.