Skip to main content
Parmana is Execution Trust Infrastructure. Traditional systems establish trust by recording who approved an action and when. Parmana extends this by making execution itself verifiable — establishing an immutable chain between authority, intent, execution, evidence, and cryptographic proof.

​
Core principle

Execution technology changes. Trust should not.
Parmana separates execution from trust so organizations can verify execution regardless of the underlying execution engine — whether that’s enterprise software today, or AI agents, robotics, or distributed systems tomorrow.

​
Design goals

  • Deterministic execution
  • Immutable trust artifacts
  • Cryptographic verification
  • Replayable execution
  • Independent auditability
  • Technology-agnostic execution
  • Long-term algorithm agility

​
Canonical trust model

Authority
    |
    v
Intent
    |
    v
Policy
    |
    v
Decision
    |
    v
Business Transaction
    |
    v
Execution
    |
    v
Verification
    |
    v
Receipt
    |
    v
Execution Trust Record
Every artifact in this chain is immutable, and every artifact contributes evidence to the whole. See Concepts Overview for what each artifact means.

​
Guiding principles

PrincipleWhat it means in practice
Immutable by defaultNo domain object supports an update operation.
Deterministic by designSame policy + same inputs → same decision, always.
Verifiable by evidenceEvery claim is backed by cryptographic evidence, not trust in the runtime.
Replayable by constructionAny past decision can be deterministically re-derived.
Storage agnosticThe Runtime doesn’t know or care which storage adapter is behind the repository interfaces.
Execution agnosticExecution engines are swappable without changing the trust model.
Cryptographically verifiableHashing and signatures are core, not bolted on.
Future-ready through algorithm agilityCryptographic algorithms are replaceable implementation details, not fixed domain concepts — e.g. a future move to post-quantum signatures wouldn’t require an architectural change.

​
Next

Runtime Architecture

How the Runtime orchestrates execution without embedding business logic.

Package Architecture

How responsibilities are split across the eight monorepo packages.

Security Model

Immutability, append-only evidence, and cryptographic guarantees.

Repository Model

How storage is abstracted behind interfaces.