elan1 DECIDE · DECISION LEDGER
Every answer, with its route, on the record.
The Decision Ledger is elan1 Decide's audit log of decisions. It keeps every answer with its type, calibrated confidence, route and reviewer, if any. When a decision leads to a write, the ledger entry's digest is bound into that write's proof record in elan1 Govern, so the decision and the action can be read together.
Available now, in every elan1 Decide plan.
- decision_id
- d_specimen_0412
- schema
- claims.fnol_triage · v3
- model
- engine_specimen_a · pinned
- calibration
- cal_v7 · this tenant
- threshold
- 0.85 · policy
- answer
- handling_path: fast_track
- confidence
- 0.93
- route
- auto · action intent to elan1 Govern
- decision_digest
- sha256:7c41a09e…e9b2
- F01 tenant_id
- t_specimen_insurer
- F02 seq
- 41207
- F04 write_id
- wi_specimen_7731
- F05 write_type
- claim.set_handling_path
- F09 actor_id
- agent.decide.router
- F10 actor_kind
- agent
- F14 payload_hash
- sha256:7c41a09e…e9b2
Tap, point at or focus the decision digest, or field F14, to mark both ends of the link.
01What it does
The Ledger explains the decision. The Govern record proves the action. One digest links them.
Decide computes a decision digest, a SHA-256 over the decision's fields. Govern commits it in F14 (payload_hash) of its 16-field proof record. Anyone checking that record can recompute the digest from the Ledger entry.
Who it's for
- Risk and model-risk owners who must explain why a case went the way it did.
- Internal audit, tracing a changed record back to the decision behind it.
- Operations owners measuring automation, review load and backlog.
03How it works
Four rules for every entry.
In the specimen above, point at or focus the decision digest to mark both ends of the hairline.
- Every request, answer and route is written as a new entry. Entries are only ever added.
- Each entry names the schema, model and calibration versions, and the threshold that applied.
- Review answers and outcomes are added as their own entries. They never overwrite the original answer.
- When a route produces an action intent, the decision digest travels with it, and Govern binds it into its record.
04In the console
Decision Ledger in the elan1 Decide console.
A screen from the elan1 Decide console design, shown as an illustrative specimen. Not customer data.
Every decision, route, review and outcome recorded with the exact versions that produced it, searchable by decision or request id.
- Append-only: rows are added, never edited in place.
- Saved views for typed holds, System-2 escalations, review bands and QA samples.
- Each row shows route, minimum confidence, model, latency, cost and caller.
One recorded decision end to end: what was asked, what the model answered, why it routed where it did, and the governance record it is bound to.
- Each step is timestamped, from request received to ledger acknowledgement.
- Pinned versions list everything that produced the route; “latest” is rejected.
- A determinism replay re-runs the route from the recorded answers and versions.
What it connects to
Writes go through elan1 Govern.
Writes go through elan1 Govern, which binds the decision digest into F14. Your own agents can read the Ledger through the elan1 Decide MCP server and API: decide, explain, get_decision, list_schemas and report_outcome. None of these calls writes to a system of record.
What it costs
Decision Ledger is included in every elan1 Decide plan. Entries are not charged on their own; the decision is the unit.
| What | Price · excl. GST | Includes |
|---|---|---|
| Growth — self-serve and developer teams | ₹4,80,000 per year | Typical volume 1,00,000 decisions a month |
| Mid-market | ₹36,00,000 per year | Typical volume 15,00,000 decisions a month |
| Enterprise — BFSI and insurers | ₹1,50,00,000 per year | Typical volume 1 crore decisions a month; SSO and SLA |
| Decisions beyond the plan allowance | ₹30 per 1,000 decisions | |
| A write intent Govern refuses | 40% of a governed action | Metered by elan1 Govern, not by Decide; the decision itself is counted once, as a decision |
All prices are exclusive of GST. Prices are current list prices; GST is added at the applicable rate on the invoice.
- The governed write that follows is Govern's unit. Decide never counts it again.
All prices are exclusive of GST. GST is added at the applicable rate on the invoice.
Status
- Available in every elan1 Decide plan.
- Governed actions in Mode B, through elan1 Govern: available.
- Each new schema runs in shadow until it reaches parity, before any route acts on its own.
- Govern records signed and checkable offline: available with L2 Attested.
Available now. See what’s next
What it does not do
- It is not a proof record. Only elan1 Govern's record shows that an action was allowed.
- It makes no integrity claim of its own. We call it append-only and recorded. Govern's record is tamper-evident at L1.
- It does not make you compliant with any regulation.
FAQ
Every elan1 Decide answer, with its type, calibrated confidence, route and reviewer, if any. It is the audit log of decisions, kept apart from the proof records of writes.
When a decision leads to a write, the ledger entry's digest is bound into the proof record elan1 Govern writes for that write, in field F14. Reading the two together shows which decision led to which action.
No. A decision is an answer, metered by elan1 Decide; a governed action is a committed write, metered by elan1 Govern. Only the writes that follow a decision pass through Govern, and nothing is counted twice.
For a decision, the Ledger shows what was answered and how it was routed. For a write, the auditor checks Govern's proof record, which carries the digest. Checking it offline, without us, comes with L2 Attested.
Erasure under India's DPDP Act and an append-only record pull in different directions. We are settling the approach with counsel and publish it on What's next. Until then, we agree how erasure applies in your deployment before go-live.
In India first. Outside India, Decide runs as decision-only pods until an elan1 residency domain exists there.
Next steps
One write path, four layers
Work and Decide propose. Govern and Run assure. Only Govern allows.
// elan1 DECIDE · DECISION LEDGER
Trace one decision to the write it caused.
Read how Govern's proof record carries the decision digest, then bring one high-volume decision to a lighthouse.