Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.manthan.systems/llms.txt

Use this file to discover all available pages before exploring further.

When policy evaluation rejects a request, governance does not end — it escalates. Override workflows are the mechanism by which a rejected execution can be reconsidered through human review, authorized at an appropriate level, and then executed with full governance continuity. The critical property is that an override does not bypass governance. Every step in the override workflow is recorded in the append-only lineage. The override authorization itself becomes part of the cryptographic proof.

​
Override Continuity

​
The override sequence

Policy Rejection — The policy evaluation layer determines that the request does not meet the criteria for autonomous execution authority. This is a legitimate governance outcome, not an error. Escalation — The rejection is escalated to a human reviewer. The escalation record is written to the lineage, preserving the full context of what was rejected and why. Human Review — A reviewer with appropriate authority examines the rejection. The review is bounded by policy — reviewers can only override within their defined authorization scope. Override Authorization — The reviewer issues an override authorization. This is a signed governance event, not an informal approval. The override itself is subject to cryptographic attestation. Execution Authority — The override authorization yields bounded execution authority for the specific action that was rejected. The authority is scoped to that execution and cannot be reused. Append-Only Lineage — Every step — rejection, escalation, review, override, execution — is written to the append-only lineage. The complete override chain is auditable and portable.

​
Why overrides must be governed

An ungoverned override is indistinguishable from a policy bypass. If override actions are not recorded in the lineage, the audit trail has gaps. If the override authorization is not cryptographically signed, it cannot be independently verified. Parmana treats overrides as first-class governance events. The compliance evidence for an overridden execution is richer than for a straightforward approval — it includes the rejection, the reviewer identity, the authorization scope, and the execution.

​
See also