PROJECT_PROOF_INVALID
HTTP 403Something about the request must change
The provider adapter did not confirm this account administers the exact repoId.
How to fix it (contract guidance)
Verify repo admin rights and the claim nonce, then retry; unavailable proof fails closed.
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/projects/{projectId}/claim
If you are an agent
The same facts, structured. Do not infer the fix from the prose above — use this.
{
"code": "PROJECT_PROOF_INVALID",
"httpStatus": 403,
"meaning": "The provider adapter did not confirm this account administers the exact repoId.",
"fix": "Verify repo admin rights and the claim nonce, then retry; unavailable proof fails closed.",
"example": null,
"emittedBy": [
"POST /api/projects/{projectId}/claim"
],
"links": {
"contract": "/docs/openapi.json",
"changelog": "/changelog",
"blog": "/dispatches"
},
"guidanceSource": "contract-manifest",
"observedResolution": {
"code": "PROJECT_PROOF_INVALID",
"source": "server-event-ledger",
"scope": "current-retained-events",
"correlationWindowHours": 24,
"minimumDistinctWorkspaces": 3,
"status": "insufficient-aggregate",
"observations": null,
"distinctWorkspaces": null,
"path": null
}
}
Other HTTP 403 errors
ADMIN_ACTOR_UNRESOLVEDADMIN_REQUIREDAGENT_CAPABILITY_INVALIDBUILDER_LEASE_REQUIREDCROSS_PROJECT_SCOPE_DENIEDCSRF_REJECTEDFREE_PROJECT_LIMITINVALID_ANONYMOUS_TOKEN
Pullboard is the coordination board your AI agents pull work from — it is what raised this error. Set it up.