Inventory ownership data missing after switching Access enforcement on
Inspect the Scopes that were written while Access was disabled: missing Artifact owners, pending Review Candidates without an owner attestation, and, when named, the background Principal's per-Scope write authority. Produces no change. In enforced mode completes as a deployment administrator; in disabled mode completes without authentication because the Server cannot yet protect anything. A background Principal check requires an available Access store; otherwise it reports 503 relationship_management_unavailable. Use the offline ownership command to check the proposed background Principal before enforcement is enabled.
Authorization
BearerAuth Bearer credential resolved to an opaque authenticated Principal by the Server deployment.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/access/ownership/plan" \ -H "Content-Type: application/json" \ -d '{}'{ "mode": "disabled", "scopes": [ { "scope_id": "string", "artifact_gaps": [ { "kind": "artifact_owner", "scope_id": "string", "family": "string", "artifact_id": "string", "entry_id": "string", "candidate_id": "string", "version": 1, "conflict_code": "string" } ], "candidate_gaps": [ { "kind": "artifact_owner", "scope_id": "string", "family": "string", "artifact_id": "string", "entry_id": "string", "candidate_id": "string", "version": 1, "conflict_code": "string" } ] } ], "background": [ { "scope_id": "string", "principal_id": "string", "allowed": false, "reason_code": "string" } ]}Authenticated instance control, permission checks and durable result exchange POST
Served by the optional standalone Source manager. Instances initiate every exchange; this is not a Server or public MCP endpoint. The operation path chooses owner/connect/poll/reply/sync/execution/results/stopped-targets/close and the applicable fields. Source observations continue to go directly to the PC Server.
Backfill missing Artifact owners and Candidate owner attestations POST
Grant the missing ownership data to the explicitly named Principal; the Server never derives it. Existing Artifact owners and Candidate attestations are preserved and reported as conflicts when they disagree with the named Principal. Identities with recorded ownership recovery evidence are reported as conflicts and must retain their original attribution. Every item is one idempotent write, so interrupted or repeated runs refill only still-missing items. Set dry_run first to preview the exact items. Requires a deployment administrator; while Access is disabled the Server has no ownership store and reports 503 ownership_migration_unavailable.

