Skip to main content
From version 4.1.0 the TypeScript and Python SDKs can make policy version 2 decisions and read or decide review items: decidePolicyV2, policyV2Review and decidePolicyV2Review in TypeScript, and decide_policy_v2, policy_v2_review and decide_policy_v2_review in Python. The server must also enable each capability. Until it does, a decision for that capability returns HTTP 404 with the error code not_enabled. The SDKs can also replay a recorded decision (policyV2Replay in TypeScript, policy_v2_replay in Python); that is in the SDK source and ships in the next release. The SDKs do not yet expose register writes, the console or the webhooks.
Policy version 2 changes how Parmana decides whether an action may proceed. It keeps the same goal as the current policies: an agent takes only the actions your business has approved. It adds three things: every value a policy uses declares where it came from, every limit is named and has an owner, and every change to the governance itself is recorded.

What a policy declares

A policy names the action it decides (for example erp:pay-invoice), its owner, and every value its rules read. Each value has a provenance, which says where it may come from: Trust comes from the signature, not from the sender. An unsigned value is untrusted, whoever sent it. Rules are checked in a fixed order: refuse, then review, then the two approval tiers, then reject. A rule must name its tier. A policy that fails the validator does not run. Limits are named thresholds with a unit, an owner and an approver. A rule compares a value with a threshold, never with another value, and the only literal number a rule may use is zero.

Reviews and approvals

An action that a rule sends to review is held as a review item. Reviewers decide it from a queue. The requester cannot review its own item, and a high-value item needs two reviewers. A review has a window of at most three business days. If the window passes without a decision, the item expires and is refused. Each reviewer decides once. An approval is tied to the exact values shown to the person who gave it. It is valid for at most 60 minutes and can be used once. Alerts that need action cannot be dismissed. They escalate from the named backup to the Parmana owner and then to Operations.

The register

Who may change a policy is recorded in a register, not assumed. The register holds the sources, thresholds, actions, roles, approver keys, policy versions, reviewer grants and contacts.
  • Only the Parmana owner grants or revokes roles. The last Parmana owner cannot be revoked.
  • A policy version is immutable once proposed. Each action has one approved version at a time.
  • A policy may go live only through the go-live gate. The owner and the successor of an action cannot run that gate, and it needs at least two gate owners who are not the owner or the successor. Every gate owner must hold the operator role.

Evidence

Each decision is written to an evidence log. Each record is linked to the one before it, and the log is append-only: a record cannot be changed or removed at the database. A replay re-runs a recorded decision against the policy it used, so you can check that the same inputs give the same outcome. Every register change writes an audit event in the same transaction as the change, so a change and its record are saved together or not at all.

Status

Sources, the second email provider and the business inputs for each policy are not connected yet. Until they are, sourced values refuse rather than guess.