Obligente Request Access

Process engine · pre-production · uncertified

Evidence season,
cancelled.

Obligente runs your regulated processes and writes the audit trail as it goes. When the auditor asks, the answer already exists.

Request Access See How It Works

demo ledger head 962ac5342796e340 · recompute it yourself

A team around a table celebrating together, relaxed and laughing

Scenario vignettes — what week one is designed to feel like

A woman leaning back from her desk with her eyes closed, visibly relieved

The Friday the evidence chase didn't happen.

Every run already recorded itself as it happened — submission, verification, approval — as hash-chained events. Nothing to gather, because nothing was ever loose.

ledgerevidence.verified · 3b81ee73fd0b27d3

Two pairs of hands passing a stapled paper report across a desk

The audit where nobody rebuilt a spreadsheet.

A run's state is replayed from its own events, not reconstructed from memory. The report is a view of the ledger — it cannot drift from what actually happened.

ledgerrun.completed · 962ac5342796e340

Three colleagues reading a printed page together at a desk

The process change nobody re-argued.

Proposed changes cite the exact ledger events that justify them — pointers anyone can resolve and recompute. The argument is a citation, not a meeting.

ledgerapproval.recorded · 26369cdbcd51a547

Departures · audit season

Every item, suddenly on time.

The things you dread pulling together are the things the ledger already holds. Each row below is tied to a shipped mechanism — and each hash is a real SHA-256 prefix.

ItemMechanismStatus
Q3 vendor review hash-chained ledger · fb82d7238c2bfd6a READY · verifiable
SOC-prep evidence pull evidence binding · 7b240e002244071f READY · verifiable
Change approval trail separation of duties · d6458bd14c78d631 READY · verifiable
Process revision history proposal loop · e9c23ac8b445dff0 READY · verifiable

“Verifiable” means recomputable: h(n) = SHA-256(h(n−1) ‖ payload(n)), genesis sixty-four zeros, over the eight demo payloads published in docs/CLAIMS.md. Tamper-evident within a stated threat model — see limits.

The loop

The process improves itself.
People stay in charge.

the ruleA machine draft never publishes itself: the database refuses.

A man writing in a paper notebook beside a closed laptop in a workshop office

Who this is for

The person who already knows how the process works.

Not the org chart — the one who wrote the runbook, keeps the exceptions in their head, and gets called at 8pm during audit week. Obligente is built so that knowledge stops living in one person and starts living in the record, without taking it away from them.

the ruleNothing publishes without a person saying yes.

Said plainly

What this does not claim.

It is not certified.
No SOC 2, ISO 27001, PCI DSS, or HIPAA attestation exists for Obligente, and none is claimed here.
Tamper-evident, within a stated threat model.
The chain detects modification by a party that cannot also rewrite the verification path and every stored digest. It is not a defence against an operator with full control of storage and verifier — no hash chain is.
It is pre-production.
The ledger, evidence verification, approvals, retention, isolation, the proposal loop and the SOP studio are built and gated. Autonomy beyond human-approved proposals is deliberately not built.
It is not deployed.
Obligente has run against a local stack and its own test suites. It has not carried anyone's regulated workload.

Bring us your worst audit story.

Obligente is pre-production and pre-attestation. The useful conversation right now is with people who want to test the mechanism, not watch a demo.

Request Access Read the Limits First