Skip to main content
These essays explain all of Parmana, one idea at a time, in plain language. Each starts from a concrete situation, explains the idea, shows how Parmana implements it, and says what it does not do. Every claim is backed by the claims register; where a feature is built but not yet in use, or tested but not seen live, the essay says so. Read them in order for the whole system, or start with How Parmana works, end to end, the map the others fill in. The reference for each topic is in Concepts and Guides.

​
Why Parmana exists

  1. Your agent’s claim is not a business fact
  2. Prompt guardrails are advice. Authorization is a gate.
  3. Agents will rewrite themselves. Their authority should not move when they do.
  1. How Parmana works, end to end

​
The decision

  1. Policies as data: same input, same decision
  2. Every action needs a signed human approval, reads included
  3. Giving an agent authority: grants with limits and an end date
  4. Per-request limits are not enough

​
The release

  1. The gateway: why your agent should never hold the keys
  2. Signed, single-use, short-lived: the execution authorization
  3. Approved what, exactly? Binding approval to content
  4. Write it down before you do it
  5. Proving the gateway is the gateway

​
The evidence

  1. An approval you can verify without trusting me
  2. Proving what didn’t happen
  3. Who asked? The caller audit trail
  4. Replay: what it can and can’t re-check
  5. Verify it yourself: offline and in the browser
  6. Choosing signatures: Ed25519, post-quantum, and keys in KMS

​
Governance and operations

  1. Maker checker for one person
  2. Governing the rules
  3. Rotating every key in production in one day
  4. Running Parmana yourself, even with no internet

​
Connecting agents and systems

  1. Connecting an agent
  2. Connecting any system
  3. What a refund agent needs before it touches a payment gateway

​
Proof and honesty

  1. Testing agent controls in production without moving real money
  2. What “done” means: deployed, but not yet deciding anything
  3. What Parmana can’t stop
  4. Mapping to regulation without overclaiming
  5. Where Parmana fits among agent controls
The essays are written in the first person by the person building Parmana and dated October 2026. Where a statement depends on the state of the project, the essay names the date or the record it comes from; the current state is always in Remaining work and the Roadmap.