Skip to content

How a Decision works.

Follow one Decision, acme/refunds, from the first draft to the refund request your support agent sent at 09:42, and the record it left behind.

Write the judgement down.

A Decision is a short file your team can read: the facts it needs, the rules it follows and the question it answers. Describe it to Claude or Codex and your agent drafts it for you. You read the draft and say when it’s ready to publish.

  • Plain YAML, or JSON if you prefer; what you wrote is kept exactly as you wrote it
  • Checked as you type, down to the exact field that needs work
  • Reviewed by an assistant that flags rules which overlap or contradict each other
More on building a Decision

Prove it on cases you trust.

Save real requests as Worked Examples while you build. The ones you confirm become the test set, and every draft runs against all of them before it can ship. When a case fails you see exactly which one, and why.

  • Only confirmed cases count as evidence; examples you’re still unsure of stay separate
  • Every change is re-run against the whole set, so fixing one case can’t break another without you seeing it
  • Compare models on your own cases before you move to a new one
More on proving it

Release it in versions.

Publishing freezes the Definition and the plan it compiles to, so a release answers the same way for as long as it lives. TypeFuse reads what changed and numbers the release for you: a breaking change is a new major version, anything else is minor or a patch.

  • Callers choose when to move. Each one says which versions it accepts, and a new major waits until its code is ready
  • Promote from Test to Production once you’re happy, with the previous major still answering for the callers on it
  • Replay any release exactly by its number when you need to debug
More on releases

Agents find the right one.

You choose which Decisions your agents can use. An agent with a job to do searches for the judgement it needs, reads what the Decision asks for and calls it. Publish a new one and your agents can find it straight away.

  • Off until you offer it. Nothing is visible to an agent until a person turns on “Offered to agents”
  • Agents search for the kind of judgement. The customer’s details go into the call, never into the search
  • Find once, call many. An agent keeps the Decision’s name and calls it for every item that follows
  • You see what they looked for, including the searches that found nothing
More on discovery

Agents and apps call one copy.

An agent finds the Decision by searching for what it needs, reads what it asks for and calls it. Your apps call it by name with a few lines of code. Either way the work happens on TypeFuse’s servers, so every caller goes through the same checks against the same release.

  • Nothing to bundle. The SDK and CLI are thin clients; the rules never ship inside your app
  • Fast enough to sit in the request. Answers through TypeFuse come back lightning fast, close to calling the model directly
  • If TypeFuse can’t be reached in time, your code gets a clear error and uses its own default
More on calling a Decision
same Decision, same record
// Your agent, over MCP
search_decisions("refund eligibility")
← acme/refunds 1.4.0 · 42/42 tested
call_decision("acme/refunds", {
  days_since_delivery: 12,
  item_condition: "damaged"
})
← route: review · 0.88 · run_demo_1042
On TypeFuse’s serversfor every caller
  1. Check the inputagainst state_schema
  2. Choose the releasethe newest the caller accepts
  3. Ask the modelthe release’s pinned jev-1.13.0
  4. Return the answersnative TypeSafe answers
  5. Record itwithin seconds

Your own keyDefault

Your TypeSafe key goes with each call, or you store one for the environment; nobody can read a stored key back.

Relay

Your key never leaves your app. TypeFuse prepares the request, your app sends it and hands back the answer.

ManagedEnterprise

TypeFuse’s key, with usage billed to you.

Every answer leaves a record.

Each call is recorded within seconds of its answer: who asked, what they sent, which release answered and what it said. The record is sealed, so anyone can check later that it hasn’t changed.

  • Follow one request by its reference, across every Decision it touched
  • See the exact release that answered, with the Definition it was published from
  • Hand over an evidence pack to risk, compliance or a customer, on paid plans
More on records and evidence

Watch it in production.

See how often each Decision is called, by whom, what it answers and how long it takes. When the mix of answers shifts, you can see it and open the calls behind it.

  • Calls, answers and response time for every Decision and every caller
  • Compare with the last period to spot a change in the mix
  • Open any call from a chart straight to its sealed record
More on Insights

Private preview

Own your next decision.

Keep the judgement calls your agents and apps make under your control, with a record of every answer.

  • Your criteriaThe people who own a decision set its rules, and change them when the business changes.The people who own a decision set its rules.
  • Your evidenceEvery release is tested against real cases before your application ever sees it.Every release is tested on real cases first.
  • Your recordEvery answer is traced and sealed, ready for an auditor or the customer who asks why.Every answer is traced and sealed.