pramaanStart a brief

Build status · 27 July 2026

Claim exactly
what the evidence proves.

Pramaan has a substantial local foundation and joint Loop acceptance. It has not yet completed a live production deployment or a real customer pilot.

Prepare a pilot brief

Current reading

Foundation confidence is high. Product confidence is earned next.

Local checks prove the architecture and failure semantics are coherent. They do not prove cloud identity, operations, deployability, customer integration, or economics. Those are separate gates.

Three proof horizons

Built, production-proved, customer-proved.

Keeping these horizons separate prevents a green test suite from turning into an unsupported market claim.

01Implemented and locally verified

The governed foundation

  • Canonical contracts and generated gateway surfaces
  • Gateway and kernel with a private mutual-TLS boundary
  • PostgreSQL-backed authority, isolation, audit, and metering controls
  • Durable Pramaan ↔ Product Loop capability exchange
  • Adversarial local tests for replay, loss, recovery, isolation, and rotation
02Requires production proof

The live Singapore cell

  • Real provider credentials and workload identities
  • Private-CA issuance, rotation, DNS, and network policy
  • Production PostgreSQL, KMS, content storage, and observability
  • Exact-build deployment, canary, rollback, and incident evidence
  • Signed Phase-0 exit against the deployed release
03Product proof

The first customer vertical

  • Freeze the Audit Log M1 requirements and journey
  • Mount append, query, and export through the real controls
  • Generate the client, documentation, and onboarding path
  • Run a real customer integration and settle its cost
  • Stabilize what the pilot exposes before broad expansion

Loop readiness

Enough to dogfood. Not enough to call finished.

Loop should run alongside the foundation work now, first as a compatibility fixture and evidence collector. It becomes authoritative only as its authoring and runtime enforcement turn green.

Protocol + templatesStrong
Durable Pramaan exchangeLocally verified
Guided brief / PRD authoringBuilding
Operator workbenchBuilding
Live deployment controlNot yet proved
Customer-validated outcome loopNot yet proved

The next sequence

Define → deploy → prove → pilot.

The application should not expand sideways until the first vertical crosses the real boundary.

  1. 01

    Freeze M1

    Requirements, journey, API behavior, acceptance, architecture, and cost envelope.

  2. 02

    Complete production composition

    Credentials, identities, private CA, data stores, KMS, network, and observability.

  3. 03

    Mount the thin vertical

    Audit append, query, and export through gateway, kernel, and real controls.

  4. 04

    Prove staging and rollback

    Exact build, migrations, canary, failure recovery, monitoring, and technical exit.

  5. 05

    Productize and pilot

    SDK, docs, onboarding, live customer integration, cost settlement, then stabilization.

Pilot deliberately

Start with one customer and one exact outcome.

Shape the pilot brief