Obligente Request Access

Process engine for regulated teams

Evidence season,
cancelled.

Your team runs the process. The audit trail writes itself as they go. Nobody loses the week before the audit to rebuilding evidence. 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

Scenarios: 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.

Each run recorded its own submission, verification and approval as it happened, as hash-chained events. There was 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.

Each run’s state is replayed from its own events, so the report is a view of the ledger. It can’t drift from what happened, because nobody rebuilt it from memory.

ledgerrun.completed · 962ac5342796e340

Three colleagues reading a printed page together at a desk

The process change nobody re-argued.

Each proposed change cites the ledger events that justify it, and anyone can resolve those pointers and recompute them. 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 already in the ledger. Each row below names the shipped mechanism that holds it.

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, set out under 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.

You wrote the runbook, you keep the exceptions in your head, and you’re the one called at 8pm in audit week. Obligente puts that knowledge in the record, where it no longer depends on one person, and you still decide what changes.

the ruleWhoever submits a step can’t also approve it.

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 who controls both storage and verifier, and 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.

Send us the audit week you’d least like to repeat. The most useful conversation right now is with someone who’ll try to break the mechanism.

Request Access Read the Limits First