state the resource request-ID idempotency key in the control-plane contract #1614

Closed
opened 2026-10-27 13:41:06 +00:00 by sam · 0 comments
Owner

The resource idempotency key is now (org_id, kind, request_id) in code and in the schema -- migration 0021 adds UNIQUE INDEX idx_resource_history_org_kind_request and PutResource's doc comment states the key -- but no document states it.

docs/prds/runtime-control-plane.md says only "Every write records who made it, where it came from, a request ID, and the version being edited", which does not settle whether one request ID may be reused across orgs or across kinds. The schema permits reuse across orgs and across kinds, and nothing tests the cross-org case either way.

Add the clause that states the key and whether a request ID is scoped per org, per kind, or global. docs/prds/orgs-and-access.md sets the precedent to follow: its task idempotency key is org/identity/owner/repo/number, i.e. the org is part of every idempotency key in the per-org world.

Found while closing archie-core-fcvd (the kind-blind dedup bug, already fixed by 62fe55e4 + migration 0021). Editing docs/ stales docs/data/generated/dev-docs.json -- regenerate and commit it with the change.

Notes

Landed in docs/prds/runtime-control-plane.md (the request ID is the idempotency key, scoped per org and per kind: (org_id, kind, request_id), per migration 0021's unique index, matching the task key org/identity/owner/repo/number in orgs-and-access.md) and docs/prds/pr-review-agent.md (the operator-approval gate belongs to the standalone pr-review workflow only; the own-PR splice drops it). Both verified against the schema and the merged decision doc before writing.

Close reason

Closed


Imported from beads archie-core-ut6b · GitHub #1492 · type task · priority P3 · created 2026-09-29 · closed 2026-09-29

The resource idempotency key is now (org_id, kind, request_id) in code and in the schema -- migration 0021 adds UNIQUE INDEX idx_resource_history_org_kind_request and PutResource's doc comment states the key -- but no document states it. docs/prds/runtime-control-plane.md says only "Every write records who made it, where it came from, a request ID, and the version being edited", which does not settle whether one request ID may be reused across orgs or across kinds. The schema permits reuse across orgs and across kinds, and nothing tests the cross-org case either way. Add the clause that states the key and whether a request ID is scoped per org, per kind, or global. docs/prds/orgs-and-access.md sets the precedent to follow: its task idempotency key is org/identity/owner/repo/number, i.e. the org is part of every idempotency key in the per-org world. Found while closing archie-core-fcvd (the kind-blind dedup bug, already fixed by 62fe55e4 + migration 0021). Editing docs/ stales docs/data/generated/dev-docs.json -- regenerate and commit it with the change. ### Notes Landed in docs/prds/runtime-control-plane.md (the request ID is the idempotency key, scoped per org and per kind: (org_id, kind, request_id), per migration 0021's unique index, matching the task key org/identity/owner/repo/number in orgs-and-access.md) and docs/prds/pr-review-agent.md (the operator-approval gate belongs to the standalone pr-review workflow only; the own-PR splice drops it). Both verified against the schema and the merged decision doc before writing. ### Close reason Closed --- _Imported from beads `archie-core-ut6b` · GitHub #1492 · type task · priority P3 · created 2026-09-29 · closed 2026-09-29_
sam added the lowtask labels 2026-10-27 13:41:06 +00:00
sam self-assigned this 2026-10-27 13:41:06 +00:00
sam closed this issue 2026-10-27 13:41:06 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1614