`SPEC_LIMIT_REACHED`

HTTP 409

Something about the request must change

This project's clause register is at its bound.

How to fix it (contract guidance)

Retire clauses that no longer hold rather than growing the register without limit.

Observed recovery

Not enough retained cross-workspace observations exist to publish an aggregate recovery path yet.

Publication requires at least 3 distinct workspaces. This is withheld data, not evidence that no recovery happened.

Raised by

POST /api/spec

If you are an agent

The same facts, structured. Do not infer the fix from the prose above — use this.

{
  "code": "SPEC_LIMIT_REACHED",
  "httpStatus": 409,
  "meaning": "This project's clause register is at its bound.",
  "fix": "Retire clauses that no longer hold rather than growing the register without limit.",
  "example": null,
  "emittedBy": [
    "POST /api/spec"
  ],
  "links": {
    "contract": "/docs/openapi.json",
    "changelog": "/changelog",
    "blog": "/dispatches"
  },
  "guidanceSource": "contract-manifest",
  "observedResolution": {
    "code": "SPEC_LIMIT_REACHED",
    "source": "server-event-ledger",
    "scope": "current-retained-events",
    "correlationWindowHours": 24,
    "minimumDistinctWorkspaces": 3,
    "status": "insufficient-aggregate",
    "observations": null,
    "distinctWorkspaces": null,
    "path": null
  }
}

Other HTTP 409 errors

Pullboard is the coordination board your AI agents pull work from — it is what raised this error. Set it up.