@parmanasystems/provenance

Portable deterministic provenance infrastructure for immutable governance lineage, audit reconstruction, runtime continuity, and independently verifiable execution evidence.

Overview

@parmanasystems/provenance provides the provenance and evidence layer for Parmana Systems.

The provenance package preserves deterministic governance lineage across:

• execution
• runtime continuity
• policy lineage
• release lineage
• attestation continuity
• replay-safe execution history
• verification evidence

The package enables:

• portable auditability
• independent verification
• deterministic reconstruction
• regulator-side validation
• governance evidence portability
• fail-closed lineage validation

Core Principle

Parmana preserves deterministic evidence for independently verifiable governance reconstruction.

The provenance layer exists to ensure governed execution can be:

• reconstructed
• validated
• audited
• verified
• transported
• independently inspected

without relying on:

• repository state
• hidden runtime assumptions
• mutable execution history.

What This Package Does

@parmanasystems/provenance:

• preserves immutable governance lineage
• records deterministic execution continuity
• preserves runtime provenance
• exports portable governance evidence
• validates provenance continuity
• reconstructs execution lineage
• validates attestation continuity
• enables independent audit reconstruction
• enforces fail-closed provenance semantics

What This Package Does NOT Do

@parmanasystems/provenance does not:

• perform AI inference
• determine business truth
• mutate governance history
• override deterministic execution
• bypass replay protection
• silently repair invalid provenance
• probabilistically reconstruct execution
• permit partial lineage continuity

Installation

npm install @parmanasystems/provenance

Quickstart

Create Provenance Record

import {
  createProvenanceRecord
} from "@parmanasystems/provenance";

const provenance =
  createProvenanceRecord({

    executionId:
      "exec_01",

    policyId:
      "claims-approval",

    policyVersion:
      "1.0.0",

    runtimeHash:
      "sha256:runtime",

    executionHash:
      "sha256:execution"
  });

console.log(
  provenance
);

Export Portable Proof Bundle

parmana export-proof ./execution.json

Produces:

proof-bundle.parmana

Portable proof bundles may contain:

• execution attestations
• runtime provenance
• release lineage
• trust-root continuity
• replay metadata
• canonical hashes
• admissibility evidence

Deterministic Guarantees

@parmanasystems/provenance enforces:

• immutable lineage continuity
• deterministic provenance generation
• replay-safe execution continuity
• canonical provenance hashing
• deterministic reconstruction semantics
• fail-closed lineage validation
• portable audit continuity
• reproducible verification evidence

Identical governed execution produces identical deterministic provenance.

Immutable Lineage Semantics

Provenance records preserve:

• execution identity
• policy lineage
• runtime lineage
• release lineage
• attestation continuity
• replay continuity
• verification evidence

Lineage is intentionally append-only.

Existing deterministic execution history is never mutated.

Runtime Provenance

The provenance layer preserves deterministic runtime continuity including:

• runtime manifests
• runtime hashes
• compatibility lineage
• release continuity
• runtime verification metadata

This enables:

• independent verification
• runtime reconstruction
• portability validation
• external auditability

Replay Continuity

Execution identities represent single-use deterministic governance events.

The provenance layer preserves:

• replay consumption history
• execution uniqueness
• immutable execution continuity
• replay-safe admissibility lineage

Replay violations are preserved as governance evidence.

Audit Reconstruction

The provenance layer enables deterministic reconstruction of:

• execution lineage
• policy lineage
• runtime continuity
• attestation continuity
• replay history
• admissibility evidence

Example:

parmana reconstruct execution-id

Potential reconstruction output:

• signals evaluated
• policy version used
• runtime provenance
• execution attestation
• replay status
• admissibility result

Human-Readable Audit Reports

Generate portable audit evidence:

parmana audit ./execution.json --format markdown

Example report sections:

• execution identity
• runtime provenance
• policy lineage
• replay continuity
• attestation continuity
• verification outcomes

Fail-Closed Provenance Validation

The provenance layer intentionally rejects:

• lineage divergence
• runtime continuity mismatch
• canonical hash mismatch
• attestation divergence
• invalid replay continuity
• incompatible runtime lineage
• incomplete provenance chains

Example:

✖ provenance continuity broken
✖ runtime lineage mismatch
✖ attestation divergence
✖ verification failed

Silent lineage repair is intentionally forbidden.

Architecture Boundaries

@parmanasystems/provenance:

• preserves deterministic governance evidence
• validates lineage continuity
• exports portable audit evidence
• enables reconstruction workflows

The provenance package does not:

• execute governed policy
• replace verification
• determine business correctness
• probabilistically infer missing lineage

Trust Model

The provenance layer preserves deterministic evidence for:

• external auditors
• regulators
• enterprise governance teams
• incident reconstruction
• independent verification workflows

Trust continuity depends on:

• immutable lineage
• canonical provenance hashing
• replay-safe execution semantics
• deterministic attestations
• fail-closed validation

Compatibility Model

The provenance package validates compatibility across:

• runtime versions
• schema versions
• policy lineage
• release lineage
• evidence schema versions
• provenance continuity

Incompatible lineage is rejected.

Evidence Schema Versioning

Portable provenance artifacts may contain:

{
  "evidenceSchemaVersion": "1.0.0"
}

This enables:

• long-term archival validation
• cross-version verification
• deterministic evidence compatibility
• portable governance continuity

Security Model

@parmanasystems/provenance uses:

• canonical provenance hashing
• deterministic lineage continuity
• immutable provenance semantics
• replay-safe execution evidence
• fail-closed validation
• cryptographic attestation continuity

Provenance validation is intentionally deterministic and reproducible.

Portable Verification

The provenance layer is designed for:

• external verification
• clean-room verification
• offline audit portability
• reproducible evidence validation
• regulator-side inspection
• enterprise governance workflows

Verification does not require:

• repository access
• monorepo state
• internal runtime execution
• mutable infrastructure dependencies

Offline Evidence Portability

Future versions will support:

parmana verify-proof ./proof-bundle.parmana --offline

Offline verification goals:

• no network dependency
• no registry dependency
• no repository dependency
• standalone deterministic verification

Example Use Cases

Regulatory Audit Reconstruction

Independently reconstruct deterministic governance lineage for regulatory review.

Incident Investigation

Reconstruct:

• runtime continuity
• replay history
• attestation lineage
• admissibility evidence

from immutable provenance records.

Portable Governance Validation

Transfer governed execution evidence across organizations for independent verification.

Enterprise AI Governance

Preserve immutable governance lineage around AI-recommended execution.

Non-Goals

Parmana provenance does not:

• replace AI systems
• determine factual correctness
• probabilistically infer execution history
• override deterministic governance
• mutate immutable lineage continuity

License

Apache-2.0