> ## Documentation Index > Fetch the complete documentation index at: https://docs.parmanasystems.com/llms.txt > Use this file to discover all available pages before exploring further. # Reject a pending policy change (checker) > Rejects a Pending Policy Change (checker). Same discipline as approve (human, maker != checker, step-up authorization), but never touches the live policy file, a rejection is purely a repository state transition with no PolicyChangeApprovalRecord of its own. ## OpenAPI ````yaml /openapi.bundled.yaml post /policies/pending-changes/{id}/reject openapi: 3.1.0 info: title: Parmana API version: 1.0.0 description: > Parmana is an Execution Trust Infrastructure that ensures there is no gap between what humans decide and what AI systems do. The API enables creation, execution, verification, replay, and auditing of Business Transactions through cryptographically verifiable Execution Trust Records. **Every route requires a caller bearer key**, except the liveness/readiness probes and documentation/verification routes that must be reachable with no credential: GET /health, GET /ready, GET /openapi.yaml, GET /documentation, GET /reference, POST /refusal/verify, POST /audit/verify, GET /keys/{keyId}, and GET /.well-known/jwks.json. Send `Authorization: Bearer ` on every other request. Keys are issued by `scripts/generate-api-key.ts` and configured server-side via `PARMANA_API_KEYS`; only a hash of each key is ever held by the server, verified in constant time. A missing or invalid credential returns 401 before a Business Transaction is even constructed, independent of Policy evaluation and gateway attestation, see `packages/api/src/middleware/caller-auth.ts` and [Authentication](/api-reference/authentication). Local development may set `PARMANA_AUTH_DISABLED=true` to skip this middleware entirely; that flag must never be set in a real deployment. contact: name: Parmana Systems email: founder@parmanasystems.com license: name: Proprietary, source-available for evaluation only, see LICENSE url: https://github.com/pavancharak/AgentLabsBuildathon/blob/main/LICENSE servers: - url: http://localhost:3000 description: Local (packages/api, PORT env var, default 3000) security: - bearerAuth: [] tags: - name: Execution description: >- Executes a Business Transaction through the complete Execution Trust pipeline - name: Transactions description: Business Transaction creation and retrieval - name: Verification description: Deterministic verification of an Execution Trust Record - name: Receipts description: Cryptographically signed Execution Trust Receipts - name: Trust Records description: Execution Trust Record retrieval - name: Replay description: Deterministic replay of a recorded Execution Trust Record - name: Policies description: Policy existence/readability check - name: Policy Governance description: Maker-checker proposal, listing, approval, and rejection of policy changes - name: Refusal Records description: >- Durable, signed evidence that a policy decision rejected a transaction (RFC-0021) - name: Audit description: >- Signed caller-authentication audit events, independently third-party-verifiable - name: System description: Operational endpoints paths: /policies/pending-changes/{id}/reject: post: tags: - Policy Governance summary: Reject a pending policy change (checker) description: > Rejects a Pending Policy Change (checker). Same discipline as approve (human, maker != checker, step-up authorization), but never touches the live policy file, a rejection is purely a repository state transition with no PolicyChangeApprovalRecord of its own. operationId: rejectPolicyChange parameters: - name: id in: path required: true schema: type: string requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/reject-policy-change-request.schema' responses: '200': description: Rejected. content: application/json: schema: $ref: '#/components/schemas/pending-policy-change.schema' examples: rejected: summary: Real captured response value: pendingPolicyChangeId: 5617ba3c-fb07-437d-9131-232b84bbb863 policyName: openapi-capture-demo-reject policyVersion: 1.0.0 proposedContent: policyId: openapi-capture-demo-reject policyVersion: 1.0.0 schemaVersion: 1.0.0 rules: - id: always-approve condition: always: true outcome: action: approve reason: OpenAPI spec capture fixture proposedBy: human-maker proposedAt: '2026-09-15T03:48:09.512Z' status: REJECTED reason: >- Capture a real rejected Pending Policy Change for the OpenAPI spec resolvedBy: human-checker resolvedAt: '2026-09-15T03:48:21.422Z' rejectionReason: Does not meet the bar for this fixture '400': description: rejectionReason missing or empty. content: application/json: schema: $ref: '#/components/schemas/error.schema' '401': $ref: '#/components/responses/Unauthorized' '403': description: >- NON_HUMAN_CALLER_DENIED, SAME_ACTOR_CANNOT_APPROVE_OWN_CHANGE, or STEP_UP_AUTHORIZATION_INVALID. content: application/json: schema: $ref: '#/components/schemas/error.schema' '404': description: No Pending Policy Change exists for this id. content: application/json: schema: $ref: '#/components/schemas/error.schema' components: schemas: reject-policy-change-request.schema: title: Reject Policy Change Request description: Request body for POST /policies/pending-changes/{id}/reject. type: object additionalProperties: false required: - rejectionReason - stepUpAuthorization properties: rejectionReason: type: string description: Free-text reason. Required, non-empty. stepUpAuthorization: $ref: '#/components/schemas/policy-change-step-up-authorization.schema' examples: - rejectionReason: Does not meet the bar for this fixture stepUpAuthorization: payload: version: 1 nonce: 4807fe45-0379-415b-9455-b8cb84eb5554 pendingPolicyChangeId: 5617ba3c-fb07-437d-9131-232b84bbb863 action: reject authorizedAt: '2026-09-15T03:48:16.755Z' expiresAt: '2026-09-15T03:50:16.755Z' signature: >- Wu5/oibGCjvkTklGQPiDMDemqxCVbSyuoVT7WHW63rGq8Av5KFTW6vMkUCP03pANv8bDu60bZVuVcTDVmLXpDA== keyId: human-checker-step-up-key algorithm: ed25519 pending-policy-change.schema: title: Pending Policy Change description: >- A proposed change to a policy's content, held in a durable pending state until a second, distinct human explicitly approves or rejects it (Policy Governance, maker-checker). Only ever moves from PENDING_APPROVAL to APPROVED or REJECTED, exactly once. type: object additionalProperties: true required: - pendingPolicyChangeId - policyName - policyVersion - proposedContent - proposedBy - proposedAt - status - reason properties: pendingPolicyChangeId: type: string description: Unique Pending Policy Change identifier. policyName: type: string description: >- The policy this proposal targets, same identifier as Policy.policyId. policyVersion: type: string description: >- The existing version this proposal is a change against ("the version being replaced"). Not necessarily equal to proposedContent's own declared version: an in-place patch and a version bump are both legitimate. proposedContent: type: object description: >- The full proposed policy.json content, in its entirety, not a diff or patch. additionalProperties: true proposedBy: type: string description: >- Identity of the proposer (maker). Always a human-authenticated (credentialHolderType USER) caller. proposedAt: type: string format: date-time status: type: string enum: - PENDING_APPROVAL - APPROVED - REJECTED reason: type: string description: Free-text justification from the proposer, required at creation. resolvedBy: type: string description: >- Identity of the resolver (checker). Absent while PENDING_APPROVAL. Never equal to proposedBy. resolvedAt: type: string format: date-time description: Absent while PENDING_APPROVAL. rejectionReason: type: string description: Present only when status is REJECTED. coverageWarnings: type: array description: >- Present only when non-empty: uncovered-fact warnings from PolicyValidator.findUncoveredFacts against proposedContent. items: type: string ruleConflicts: type: array description: >- Present only when non-empty: advisory rule-conflict warnings from PolicyValidator.findRuleConflicts against proposedContent, never blocking. items: type: string examples: - pendingPolicyChangeId: 6f4e4020-adf5-4449-938d-27aab58f66b7 policyName: openapi-capture-demo policyVersion: 1.0.0 proposedContent: policyId: openapi-capture-demo policyVersion: 1.0.0 schemaVersion: 1.0.0 rules: - id: always-approve condition: always: true outcome: action: approve reason: OpenAPI spec capture fixture proposedBy: human-maker proposedAt: '2026-09-15T03:47:13.920Z' status: APPROVED reason: Capture a real Pending Policy Change for the OpenAPI spec resolvedBy: human-checker resolvedAt: '2026-09-15T03:48:03.586Z' error.schema: title: Error Response description: >- Shared error envelope produced by packages/api/src/middleware/error-handler.ts and by every route's inline validation checks. error is always a plain human-readable string (never a nested object). code is present only when the failure was a RuntimeError subclass reaching the centralized error handler (VerificationFailedError, ReceiptGenerationError, or an uncategorized RuntimeError); it is absent from every inline route-level check (businessTransactionId format/required checks) and from BusinessTransactionValidationError, PolicyValidationError, SignalValidationError, PolicyNotFoundError, DuplicateBusinessTransactionError, and the generic 500 fallback. POST /policies/validate does NOT use this envelope at all. See its own response schema. For the triggering condition and recommended caller action behind any specific error/code/status combination, see the Error catalog at /api-reference/error-catalog. type: object additionalProperties: false required: - error properties: error: type: string description: Human-readable error message. code: type: string description: >- Stable machine-readable error code. Only present for errors that reach the handler as a RuntimeError. examples: - RUNTIME_ERROR - VERIFICATION_FAILED - RECEIPT_GENERATION_FAILED examples: - error: businessTransactionId must be a valid UUID. - error: >- Business Transaction 'eed2a972-1bf5-4166-8472-761f76fbf1b2' already exists. - error: >- Execution rejected: Vendor payment rejected because the assessed payment risk exceeds the maximum permitted threshold. code: RUNTIME_ERROR policy-change-step-up-authorization.schema: title: Policy Change Step-Up Authorization description: >- Signed envelope proving a checker's explicit, fresh intent to approve or reject one specific Pending Policy Change (Policy Governance, Layer 4). Produced by PolicyChangeStepUpAuthorizationSigner (@parmana/crypto) using the checker's own step-up private key, never the bearer API key. Verified server-side against: the checker's registered stepUpPublicKey, payload.pendingPolicyChangeId matching the URL's {id}, payload.action matching the endpoint (approve vs reject), payload.expiresAt not yet passed, and payload.nonce not previously seen (single-use, replay-rejected on a second attempt with the same envelope). type: object additionalProperties: true required: - payload - signature - keyId - algorithm properties: payload: type: object additionalProperties: true required: - version - nonce - pendingPolicyChangeId - action - authorizedAt - expiresAt properties: version: type: integer nonce: type: string description: >- Single-use value; a second request replaying the same envelope is rejected. pendingPolicyChangeId: type: string action: type: string enum: - approve - reject authorizedAt: type: string format: date-time expiresAt: type: string format: date-time signature: type: string description: >- Base64-encoded signature over the canonical payload, signed with the checker's step-up private key. keyId: type: string algorithm: type: string examples: - ed25519 examples: - payload: version: 1 nonce: 343ee454-92c6-4ef9-9cfe-e98329e51f53 pendingPolicyChangeId: 6f4e4020-adf5-4449-938d-27aab58f66b7 action: approve authorizedAt: '2026-09-15T03:47:51.939Z' expiresAt: '2026-09-15T03:49:51.939Z' signature: >- keOXnzUk8KcGrQTkpXC4Ki8ps3GTvMANwqq96b+toxba07gjkcmpyL/vaPZ7+pPZ1HAOJOOy3rj5XfhcwOTnAw== keyId: human-checker-step-up-key algorithm: ed25519 responses: Unauthorized: description: >- Missing or invalid caller credential (StaticKeyAuthenticator returned no identity). Real captured response, packages/api/src/middleware/caller-auth.ts. content: application/json: schema: $ref: '#/components/schemas/error.schema' examples: authRequired: summary: Real captured response, missing or invalid Authorization header value: error: authentication required securitySchemes: bearerAuth: type: http scheme: bearer description: > Caller API key issued by scripts/generate-api-key.ts. Sent as Authorization: Bearer . Verified against a stored SHA-256 hash in constant time by packages/api/src/auth/StaticKeyAuthenticator.ts. Required on every route not listed as exempt in this document's top-level description. See /api-reference/authentication. ````