elan1 DECIDE · DECISION STUDIO
Write the question before anyone answers it.
Decision Studio is the elan1 Decide module where a team defines a decision before any model answers it. Each decision is typed as a Boolean, a Choice or a Score, with a fixed shape, so every answer can be checked, calibrated, routed and recorded in the same way, whatever model produces it.
Available now, in every elan1 Decide plan.
- version
- v3 · pinned · never “latest”
- lint
- passed · published versions never change
Questions
- policy_in_force
- Booleanyes | no
- handling_path
- Choicefast_track | standard | investigate
- damage_severity
- Score0 to 100, integer
What the model may see
- context
- loss_date, policy_status, loss_description, sum_insured
- redaction
- names, phone numbers and IDs removed before the call
Policy
- threshold
- 0.85 · set by your policy · also declared as an elan1 Govern rule
- used_by
- Router · Calibration Lab · Decision Ledger
01What it does
A schema is the contract for one decision.
A schema says what the question is, which answers are allowed, what the model may see, and how sure an answer must be before it can act without a person. Studio keeps the registry of schemas and versions. Nothing resolves to 'latest': every decision names the exact schema version behind it.
Who it's for
- Decision owners in claims and AML operations, who own the policy behind each case type.
- Analysts who keep schemas current as rules change.
- Platform teams wiring elan1 Decide into an intake flow over the API or MCP.
03How it works
Five steps from a question to a pinned version.
Focus or point at a step to mark the matching field on the specimen.
- Pick the shape. Boolean for yes or no. Choice for one of a fixed list. Score for a number in a declared range.On the specimen: the three typed questions
- Declare the context. Set which fields of a case the model may see. Personal data is redacted before the call.On the specimen: context and redaction
- Set the threshold. Confidence is data; the threshold is policy. You declare it in the schema, and again as an elan1 Govern rule.On the specimen: threshold
- Lint and pin. A published version never changes. A change is a new version.On the specimen: version and lint
- Hand it on. The Router routes on it, the Calibration Lab tests it, and the Decision Ledger names it on every answer.On the specimen: used_by
Focus or point at a step to mark its part of the specimen.
- version
- v3 · pinned · never “latest”
- lint
- passed · published versions never change
Questions
- policy_in_force
- Booleanyes | no
- handling_path
- Choicefast_track | standard | investigate
- damage_severity
- Score0 to 100, integer
What the model may see
- context
- loss_date, policy_status, loss_description, sum_insured
- redaction
- names, phone numbers and IDs removed before the call
Policy
- threshold
- 0.85 · set by your policy · also declared as an elan1 Govern rule
- used_by
- Router · Calibration Lab · Decision Ledger
04In the console
Decision Studio in the elan1 Decide console.
A screen from the elan1 Decide console design, shown as an illustrative specimen. Not customer data.
Where a decision is defined: typed questions, state fields and a governed action, linted as you type and signed off by two named people before it can publish.
- Seven steps from Author to Compile, each with a visible status.
- Every answer is Boolean, Choice or Score, so it can be calibrated and audited.
- The same lint rules (DS-01 to DS-10) run in CI with no platform present.
What it connects to
Writes go through elan1 Govern.
A schema never writes to a record. When a decision leads to a change, the Router builds an action intent, and writes go through elan1 Govern over KernelPort, in Mode B: evaluated and recorded. Decision Studio is not Govern's Declaration Studio. Declaration Studio holds the rules for writes; Decision Studio holds questions.
What it costs
Decision Studio is included in every elan1 Decide plan. Decide charges for one thing it can count: decisions.
| 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.
- First purchase: an LLM Decision Offload audit that leads to a plan, or a claims or AML lighthouse.
Each layer charges for one thing it can count, and nobody pays twice for the same action.
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 does not decide. It defines the question.
- It does not hold rules for writes. Those live in elan1 Govern.
- It does not change a schema under a live decision.
- It does not choose your threshold for you.
FAQ
A typed decision is a question with a fixed answer shape: a Boolean (yes or no), a Choice from a set list, or a Score on a defined scale. Because every answer has the same shape, it can be checked, calibrated, routed and recorded in the same way, whatever model produces it.
So the answer can be checked. A question written in advance fixes what counts as an answer, which lets the Calibration Lab test it on your cases and lets the Router apply your threshold. An open question cannot be calibrated or routed.
Yes. A changed decision is a new schema, so it runs in shadow and must be calibrated again before any route acts on its own. Answers already in the Decision Ledger stay as they were recorded.
You do, as policy. Decide reports how sure each answer is. Your threshold decides what that number permits, and Govern re-checks it without a model.
No. Every answer is Boolean, Choice or Score, which is what makes calibration and routing possible. An explanation can sit beside an answer, but it never feeds the route.
No. Declaration Studio belongs to elan1 Govern and holds the rules a write must pass. Decision Studio holds the questions.
Next steps
Related reading
One write path, four layers
Work and Decide propose. Govern and Run assure. Only Govern allows.
// elan1 DECIDE · DECISION STUDIO
Bring one decision to a lighthouse.
Pick a high-volume decision. We run it in shadow beside your current process before any route goes live.