Inventory ownership data missing after switching Access enforcement on

POST
/v1/access/ownership/plan

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
AuthorizationBearer <token>

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"    }  ]}