Needlepath · Decision replay

Watch Needlepath decide.

One support agent, one refund ticket, and a pile of records that will not all fit. Below are five real calls to the context selection API. The requests and the responses are baked into this page exactly as they came back: which records survived, what each one scored, why it was kept, and the tokens before and after.

operating point np-2026-07-r2 policy version np-2026-07-r2 5 calls, replayed
The setup

The 12 records the agent sent.

Invoice 4471. The customer paid for two chairs with expedited shipping, the parcel is late, and they want their money back. Every card below is one record the agent handed to Needlepath, labelled with the kind it carries on the wire. Each one is sent with the same importance, so nothing on this page is explained away by a thumb on the scale.

  1. tool result get_invoice(4471) billing-api
  2. document Refund policy v4 handbook
  3. document Shipping and delivery policy v2 handbook
  4. document Data retention policy v7 handbook
  5. tool result get_shipment(4471) logistics-api
  6. tool result get_account(acct-2213) billing-api
  7. user input Customer, message 1 chat
  8. model reply Agent, message 1 chat
  9. user input Customer, message 2 chat
  10. error record gateway timeout on refund preview payments-api A failed tool call from earlier in the session, sent to Needlepath like any other record. Recent errors earn their place: a model about to promise a refund needs to know the refund preview just failed.
  11. tool schema issue_refund tools
  12. document SSO and SCIM provisioning guide, revision 12 knowledge-base

The knowledge base article is the interesting one: a long guide about single sign-on that has nothing to do with a refund. It is there because it is there in real systems, and it is what makes the arithmetic below worth looking at.

The calls

Five decisions. Five real responses.

Step through them. Four of the five calls send the same twelve records, so the question and the budget are the only things that move. The stand down is the one call with a different, smaller set.

DECISION 1 OF 5 · THE PILE

Twelve records, one question.

An AI support agent is handling a refund ticket, with twelve items from different data sources available as context: tool call results like the invoice and shipment lookups, policy documents from the knowledge base, the conversation history, and one error from a failed refund check. Only a few of them belong in front of the model. Needlepath reads the full context and the question, keeps four items, and drops the rest before they go through expensive LLM processing.

Task prompt

Can invoice 4471 still be refunded, and for how much?

Budget

200 tokens

12 records sent
The records the agent sent 4 of 12 kept
  • get_invoice(4471) tool result not selected
  • Refund policy v4 document 42 tok
    score 4.93 kept: a recent relevant result, keyword overlap

    Refund policy v4. A paid order may be refunded within 30 days of the invoice date. Refunds are issued to the original payment method and settle within 10 business days.

  • Shipping and delivery policy v2 document not selected
  • Data retention policy v7 document not selected
  • get_shipment(4471) tool result not selected
  • get_account(acct-2213) tool result not selected
  • Customer, message 1 user input 36 tok
    score 44.97 kept: matches the current request, keyword overlap, topic overlap

    Hi, I paid for two chairs on invoice 4471 with expedited shipping and they still are not here. I do not want them anymore. Can I get my money back?

  • Agent, message 1 model reply not selected
  • Customer, message 2 user input 22 tok
    score 38.98 kept: matches the current request, topic overlap

    Thank you. If the refund goes through, does the expedited shipping I paid come back too?

  • gateway timeout on refund preview error record 35 tok

    A failed tool call from earlier in the session, sent to Needlepath like any other record. Recent errors earn their place: a model about to promise a refund needs to know the refund preview just failed.

    score 12.97 kept: a recent error

    {"error": "upstream_timeout", "operation": "refund_preview", "invoice_id": 4471, "attempt": 1, "retryable": true}

  • issue_refund tool schema not selected
  • SSO and SCIM provisioning guide, revision 12 document not selected
Tokens
before
1,660
after
135
saved
1,525
91.9% of the packet removed decided in 1.58 ms
The verdict, on the wire

The engine selected. The packet above is what the model reads, assembled from your own records.

fallback_used
false
tokens_saved
1,525
gate.engaged
true
gate.reason
engage:needle
usage.outcome
engaged
usage.charge_multiplier
1.0
Read the raw request and response for decision 1, with the wire reason strings
request · task and budget
{
  "request_id": "nm-demo-2026-08-m1",
  "task": {
    "prompt": "Can invoice 4471 still be refunded, and for how much?"
  },
  "budget": {
    "max_context_tokens": 200,
    "operating_point": "np-2026-07-r2"
  }
}
response
{
  "request_id": "nm-demo-2026-08-m1",
  "policy_version": "np-2026-07-r2",
  "rendered_context": "Relevant State\n\n1. gateway timeout on refund preview (payments-api)\n{\"error\": \"upstream_timeout\", \"operation\": \"refund_preview\", \"invoice_id\": 4471, \"attempt\": 1, \"retryable\": true}\n\n2. Customer, message 1 (chat)\nHi, I paid for two chairs on invoice 4471 with expedited shipping and they still are not here. I do not want them anymore. Can I get my money back?\n\n3. Refund policy v4 (handbook)\nRefund policy v4. A paid order may be refunded within 30 days of the invoice date. Refunds are issued to the original payment method and settle within 10 business days.\n\n4. Customer, message 2 (chat)\nThank you. If the refund goes through, does the expedited shipping I paid come back too?",
  "selected": [
    {
      "record_id": "r-payment-error",
      "kind": "error",
      "title": "gateway timeout on refund preview",
      "source": "payments-api",
      "score": 12.970833333333333,
      "reason": "hard context: recent error",
      "excerpt": "{\"error\": \"upstream_timeout\", \"operation\": \"refund_preview\", \"invoice_id\": 4471, \"attempt\": 1, \"retryable\": true}",
      "excerpt_format": "plain",
      "selected_tokens": 35
    },
    {
      "record_id": "r-turn-1",
      "kind": "user_input",
      "title": "Customer, message 1",
      "source": "chat",
      "score": 44.97,
      "reason": "hard context: current request: current request; keyword overlap; semantic tag overlap",
      "excerpt": "Hi, I paid for two chairs on invoice 4471 with expedited shipping and they still are not here. I do not want them anymore. Can I get my money back?",
      "excerpt_format": "plain",
      "selected_tokens": 36
    },
    {
      "record_id": "r-refund-policy",
      "kind": "external_data",
      "title": "Refund policy v4",
      "source": "handbook",
      "score": 4.929166666666666,
      "reason": "hard context: recent relevant result: keyword overlap",
      "excerpt": "Refund policy v4. A paid order may be refunded within 30 days of the invoice date. Refunds are issued to the original payment method and settle within 10 business days.",
      "excerpt_format": "plain",
      "selected_tokens": 42
    },
    {
      "record_id": "r-turn-3",
      "kind": "user_input",
      "title": "Customer, message 2",
      "source": "chat",
      "score": 38.98166666666667,
      "reason": "hard context: current request; semantic tag overlap",
      "excerpt": "Thank you. If the refund goes through, does the expedited shipping I paid come back too?",
      "excerpt_format": "plain",
      "selected_tokens": 22
    }
  ],
  "tokens_before": 1660,
  "tokens_after": 135,
  "tokens_saved": 1525,
  "records_available": 12,
  "records_selected": 4,
  "fallback_used": false,
  "selection_error": null,
  "reduction_ratio": 0.9186746987951807,
  "engine_latency_ms": 1.5790799999990668,
  "gate": {
    "engaged": true,
    "reason": "engage:needle"
  },
  "usage": {
    "outcome": "engaged",
    "charge_multiplier": "1.0",
    "currency": "USD"
  }
}
DECISION 2 OF 5 · NEW QUESTION

Same pile. Different question. Different answer.

Nothing about the twelve items changed, but the customer now asks where the parcel is. The shipment lookup suddenly matters and the refund policy does not, so the kept set changes with the question. There is no stored ranking to go stale: the context rides in on every call, and every call is decided from scratch.

Task prompt

What is the carrier tracking number and the last scan location for the parcel?

Budget

200 tokens

12 records sent
The records the agent sent 4 of 12 kept
  • get_invoice(4471) tool result not selected
  • Refund policy v4 document not selected
  • Shipping and delivery policy v2 document not selected
  • Data retention policy v7 document not selected
  • get_shipment(4471) tool result 93 tok
    score 6.92 kept: a recent relevant result, keyword overlap

    {"invoice_id": 4471, "carrier": "Vantage Freight", "tracking": "VF889210043US", "service": "expedited", "commitment_date": "2026-07-14", "status": "in_transit", "last_scan": {"at": "2026-07-16T04:10:00Z", "location": "Reno NV", "event": "departed sort facility"}}

  • get_account(acct-2213) tool result not selected
  • Customer, message 1 user input 30 tok
    score 38.97 kept: matches the current request, topic overlap

    Hi, I paid for two chairs on invoice 4471 with expedited shipping and they still are not here. I do not want them anymore.

  • Agent, message 1 model reply not selected
  • Customer, message 2 user input 22 tok
    score 38.98 kept: matches the current request, topic overlap

    Thank you. If the refund goes through, does the expedited shipping I paid come back too?

  • gateway timeout on refund preview error record 35 tok

    A failed tool call from earlier in the session, sent to Needlepath like any other record. Recent errors earn their place: a model about to promise a refund needs to know the refund preview just failed.

    score 12.97 kept: a recent error

    {"error": "upstream_timeout", "operation": "refund_preview", "invoice_id": 4471, "attempt": 1, "retryable": true}

  • issue_refund tool schema not selected
  • SSO and SCIM provisioning guide, revision 12 document not selected
Tokens
before
1,660
after
180
saved
1,480
89.2% of the packet removed decided in 1.74 ms
The verdict, on the wire

The engine selected. The packet above is what the model reads, assembled from your own records.

fallback_used
false
tokens_saved
1,480
gate.engaged
true
gate.reason
engage:needle
usage.outcome
engaged
usage.charge_multiplier
1.0
Read the raw request and response for decision 2, with the wire reason strings
request · task and budget
{
  "request_id": "nm-demo-2026-08-m2",
  "task": {
    "prompt": "What is the carrier tracking number and the last scan location for the parcel?"
  },
  "budget": {
    "max_context_tokens": 200,
    "operating_point": "np-2026-07-r2"
  }
}
response
{
  "request_id": "nm-demo-2026-08-m2",
  "policy_version": "np-2026-07-r2",
  "rendered_context": "Relevant State\n\n1. gateway timeout on refund preview (payments-api)\n{\"error\": \"upstream_timeout\", \"operation\": \"refund_preview\", \"invoice_id\": 4471, \"attempt\": 1, \"retryable\": true}\n\n2. Customer, message 2 (chat)\nThank you. If the refund goes through, does the expedited shipping I paid come back too?\n\n3. get_shipment(4471) (logistics-api)\n{\"invoice_id\": 4471, \"carrier\": \"Vantage Freight\", \"tracking\": \"VF889210043US\", \"service\": \"expedited\", \"commitment_date\": \"2026-07-14\", \"status\": \"in_transit\", \"last_scan\": {\"at\": \"2026-07-16T04:10:00Z\", \"location\": \"Reno NV\", \"event\": \"departed sort facility\"}}\n\n4. Customer, message 1 (chat)\nHi, I paid for two chairs on invoice 4471 with expedited shipping and they still are not here. I do not want them anymore.",
  "selected": [
    {
      "record_id": "r-payment-error",
      "kind": "error",
      "title": "gateway timeout on refund preview",
      "source": "payments-api",
      "score": 12.970833333333333,
      "reason": "hard context: recent error",
      "excerpt": "{\"error\": \"upstream_timeout\", \"operation\": \"refund_preview\", \"invoice_id\": 4471, \"attempt\": 1, \"retryable\": true}",
      "excerpt_format": "plain",
      "selected_tokens": 35
    },
    {
      "record_id": "r-turn-3",
      "kind": "user_input",
      "title": "Customer, message 2",
      "source": "chat",
      "score": 38.98166666666667,
      "reason": "hard context: current request: current request; semantic tag overlap",
      "excerpt": "Thank you. If the refund goes through, does the expedited shipping I paid come back too?",
      "excerpt_format": "plain",
      "selected_tokens": 22
    },
    {
      "record_id": "r-shipment",
      "kind": "tool_result",
      "title": "get_shipment(4471)",
      "source": "logistics-api",
      "score": 6.9225,
      "reason": "hard context: recent relevant result: keyword overlap",
      "excerpt": "{\"invoice_id\": 4471, \"carrier\": \"Vantage Freight\", \"tracking\": \"VF889210043US\", \"service\": \"expedited\", \"commitment_date\": \"2026-07-14\", \"status\": \"in_transit\", \"last_scan\": {\"at\": \"2026-07-16T04:10:00Z\", \"location\": \"Reno NV\", \"event\": \"departed sort facility\"}}",
      "excerpt_format": "plain",
      "selected_tokens": 93
    },
    {
      "record_id": "r-turn-1",
      "kind": "user_input",
      "title": "Customer, message 1",
      "source": "chat",
      "score": 38.97,
      "reason": "hard context: current request; semantic tag overlap",
      "excerpt": "Hi, I paid for two chairs on invoice 4471 with expedited shipping and they still are not here. I do not want them anymore.",
      "excerpt_format": "plain",
      "selected_tokens": 30
    }
  ],
  "tokens_before": 1660,
  "tokens_after": 180,
  "tokens_saved": 1480,
  "records_available": 12,
  "records_selected": 4,
  "fallback_used": false,
  "selection_error": null,
  "reduction_ratio": 0.891566265060241,
  "engine_latency_ms": 1.7367620000072748,
  "gate": {
    "engaged": true,
    "reason": "engage:needle"
  },
  "usage": {
    "outcome": "engaged",
    "charge_multiplier": "1.0",
    "currency": "USD"
  }
}
DECISION 3 OF 5 · ROOM TO SPARE

A budget is a ceiling, not a target.

The refund question again, with a budget forty times bigger. A method that spends what it is given would fill the room with policy documents. Compare this packet with the first decision: the budget went up and the selection did not move. A budget is a ceiling, not a target, so more headroom never means more tokens through the model.

Task prompt

Can invoice 4471 still be refunded, and for how much?

Budget

8,000 tokens

12 records sent
The records the agent sent 4 of 12 kept
  • get_invoice(4471) tool result not selected
  • Refund policy v4 document 42 tok
    score 4.93 kept: a recent relevant result, keyword overlap

    Refund policy v4. A paid order may be refunded within 30 days of the invoice date. Refunds are issued to the original payment method and settle within 10 business days.

  • Shipping and delivery policy v2 document not selected
  • Data retention policy v7 document not selected
  • get_shipment(4471) tool result not selected
  • get_account(acct-2213) tool result not selected
  • Customer, message 1 user input 36 tok
    score 44.97 kept: matches the current request, keyword overlap, topic overlap

    Hi, I paid for two chairs on invoice 4471 with expedited shipping and they still are not here. I do not want them anymore. Can I get my money back?

  • Agent, message 1 model reply not selected
  • Customer, message 2 user input 22 tok
    score 38.98 kept: matches the current request, topic overlap

    Thank you. If the refund goes through, does the expedited shipping I paid come back too?

  • gateway timeout on refund preview error record 35 tok

    A failed tool call from earlier in the session, sent to Needlepath like any other record. Recent errors earn their place: a model about to promise a refund needs to know the refund preview just failed.

    score 12.97 kept: a recent error

    {"error": "upstream_timeout", "operation": "refund_preview", "invoice_id": 4471, "attempt": 1, "retryable": true}

  • issue_refund tool schema not selected
  • SSO and SCIM provisioning guide, revision 12 document not selected
Tokens
before
1,660
after
135
saved
1,525
91.9% of the packet removed decided in 1.59 ms
The verdict, on the wire

The engine selected. The packet above is what the model reads, assembled from your own records.

fallback_used
false
tokens_saved
1,525
gate.engaged
true
gate.reason
engage:needle
usage.outcome
engaged
usage.charge_multiplier
1.0
Read the raw request and response for decision 3, with the wire reason strings
request · task and budget
{
  "request_id": "nm-demo-2026-08-m4",
  "task": {
    "prompt": "Can invoice 4471 still be refunded, and for how much?"
  },
  "budget": {
    "max_context_tokens": 8000,
    "operating_point": "np-2026-07-r2"
  }
}
response
{
  "request_id": "nm-demo-2026-08-m4",
  "policy_version": "np-2026-07-r2",
  "rendered_context": "Relevant State\n\n1. gateway timeout on refund preview (payments-api)\n{\"error\": \"upstream_timeout\", \"operation\": \"refund_preview\", \"invoice_id\": 4471, \"attempt\": 1, \"retryable\": true}\n\n2. Customer, message 1 (chat)\nHi, I paid for two chairs on invoice 4471 with expedited shipping and they still are not here. I do not want them anymore. Can I get my money back?\n\n3. Refund policy v4 (handbook)\nRefund policy v4. A paid order may be refunded within 30 days of the invoice date. Refunds are issued to the original payment method and settle within 10 business days.\n\n4. Customer, message 2 (chat)\nThank you. If the refund goes through, does the expedited shipping I paid come back too?",
  "selected": [
    {
      "record_id": "r-payment-error",
      "kind": "error",
      "title": "gateway timeout on refund preview",
      "source": "payments-api",
      "score": 12.970833333333333,
      "reason": "hard context: recent error",
      "excerpt": "{\"error\": \"upstream_timeout\", \"operation\": \"refund_preview\", \"invoice_id\": 4471, \"attempt\": 1, \"retryable\": true}",
      "excerpt_format": "plain",
      "selected_tokens": 35
    },
    {
      "record_id": "r-turn-1",
      "kind": "user_input",
      "title": "Customer, message 1",
      "source": "chat",
      "score": 44.97,
      "reason": "hard context: current request: current request; keyword overlap; semantic tag overlap",
      "excerpt": "Hi, I paid for two chairs on invoice 4471 with expedited shipping and they still are not here. I do not want them anymore. Can I get my money back?",
      "excerpt_format": "plain",
      "selected_tokens": 36
    },
    {
      "record_id": "r-refund-policy",
      "kind": "external_data",
      "title": "Refund policy v4",
      "source": "handbook",
      "score": 4.929166666666666,
      "reason": "hard context: recent relevant result: keyword overlap",
      "excerpt": "Refund policy v4. A paid order may be refunded within 30 days of the invoice date. Refunds are issued to the original payment method and settle within 10 business days.",
      "excerpt_format": "plain",
      "selected_tokens": 42
    },
    {
      "record_id": "r-turn-3",
      "kind": "user_input",
      "title": "Customer, message 2",
      "source": "chat",
      "score": 38.98166666666667,
      "reason": "hard context: current request; semantic tag overlap",
      "excerpt": "Thank you. If the refund goes through, does the expedited shipping I paid come back too?",
      "excerpt_format": "plain",
      "selected_tokens": 22
    }
  ],
  "tokens_before": 1660,
  "tokens_after": 135,
  "tokens_saved": 1525,
  "records_available": 12,
  "records_selected": 4,
  "fallback_used": false,
  "selection_error": null,
  "reduction_ratio": 0.9186746987951807,
  "engine_latency_ms": 1.5870350000000144,
  "gate": {
    "engaged": true,
    "reason": "engage:needle"
  },
  "usage": {
    "outcome": "engaged",
    "charge_multiplier": "1.0",
    "currency": "USD"
  }
}
DECISION 4 OF 5 · STAND DOWN

When trimming would not pay, it steps aside.

A different, smaller call: three tool results and nothing else. There is no noise to remove, so the engine steps aside and hands everything straight back, and you send what you were going to send. Look at the receipt in the response: the charge multiplier is zero. When it cannot help, it says so on the wire, and it costs nothing.

Task prompt

Pull the numbers we need to answer the customer on invoice 4471.

Budget

4,000 tokens

3 records sent
The records the agent sent 3 of 3 handed back
  • get_invoice(4471) tool result handed back
  • get_shipment(4471) tool result handed back
  • get_account(acct-2213) tool result handed back
Tokens
before
286
after
0
saved
0
0% of the packet removed decided in 0.21 ms

The after figure counts the packet the engine would substitute, and here there is none. Your own context goes through whole.

The verdict, on the wire

The engine stood down. It returned no substitute packet, so you send the context you already had, unchanged.

fallback_used
true
tokens_saved
0
gate.engaged
false
gate.reason
standdown:insufficient_candidates
usage.outcome
stood_down
usage.charge_multiplier
0

A stand down is a 200 with a usable body, and the response carries a charge multiplier of 0 for that call. Wrong optimization is worse than no optimization, so when there is nothing to win, the engine takes nothing.

Read the raw request and response for decision 4, with the wire reason strings
request · task and budget
{
  "request_id": "nm-demo-2026-08-m5",
  "task": {
    "prompt": "Pull the numbers we need to answer the customer on invoice 4471."
  },
  "budget": {
    "max_context_tokens": 4000,
    "operating_point": "np-2026-07-r2"
  }
}
response
{
  "request_id": "nm-demo-2026-08-m5",
  "policy_version": "np-2026-07-r2",
  "rendered_context": "Relevant State: none selected.",
  "selected": [],
  "tokens_before": 286,
  "tokens_after": 0,
  "tokens_saved": 0,
  "records_available": 3,
  "records_selected": 0,
  "fallback_used": true,
  "selection_error": null,
  "reduction_ratio": 0,
  "engine_latency_ms": 0.21158800001330746,
  "gate": {
    "engaged": false,
    "reason": "standdown:insufficient_candidates"
  },
  "usage": {
    "outcome": "stood_down",
    "charge_multiplier": "0",
    "currency": "USD"
  }
}
DECISION 5 OF 5 · THE SQUEEZE

Forced to keep one thing, it keeps the one that prevents damage.

A stress test, not a configuration you would run: we cut the budget to forty tokens, room for exactly one item, to see what the engine protects. It keeps the error from the failed refund check. That looks surprising next to the customer’s messages until you ask what the model would do with each one alone: given only the message, it might promise a refund. Given only the error, it knows the one thing that prevents the worst answer, which is promising money movement while payments is down. Under normal budgets you never make this trade; under an impossible one, the engine gives up the conversation before it gives up the warning.

Task prompt

Can invoice 4471 still be refunded, and for how much?

Budget

40 tokens

12 records sent
The records the agent sent 1 of 12 kept
  • get_invoice(4471) tool result not selected
  • Refund policy v4 document not selected
  • Shipping and delivery policy v2 document not selected
  • Data retention policy v7 document not selected
  • get_shipment(4471) tool result not selected
  • get_account(acct-2213) tool result not selected
  • Customer, message 1 user input not selected
  • Agent, message 1 model reply not selected
  • Customer, message 2 user input not selected
  • gateway timeout on refund preview error record 35 tok

    A failed tool call from earlier in the session, sent to Needlepath like any other record. Recent errors earn their place: a model about to promise a refund needs to know the refund preview just failed.

    score 12.97 kept: a recent error

    {"error": "upstream_timeout", "operation": "refund_preview", "invoice_id": 4471, "attempt": 1, "retryable": true}

  • issue_refund tool schema not selected
  • SSO and SCIM provisioning guide, revision 12 document not selected
Tokens
before
1,660
after
35
saved
1,625
97.9% of the packet removed decided in 1.82 ms
The verdict, on the wire

The engine selected. The packet above is what the model reads, assembled from your own records.

fallback_used
false
tokens_saved
1,625
gate.engaged
true
gate.reason
engage:needle
usage.outcome
engaged
usage.charge_multiplier
1.0
Read the raw request and response for decision 5, with the wire reason strings
request · task and budget
{
  "request_id": "nm-demo-2026-08-m3",
  "task": {
    "prompt": "Can invoice 4471 still be refunded, and for how much?"
  },
  "budget": {
    "max_context_tokens": 40,
    "operating_point": "np-2026-07-r2"
  }
}
response
{
  "request_id": "nm-demo-2026-08-m3",
  "policy_version": "np-2026-07-r2",
  "rendered_context": "Relevant State\n\n1. gateway timeout on refund preview (payments-api)\n{\"error\": \"upstream_timeout\", \"operation\": \"refund_preview\", \"invoice_id\": 4471, \"attempt\": 1, \"retryable\": true}",
  "selected": [
    {
      "record_id": "r-payment-error",
      "kind": "error",
      "title": "gateway timeout on refund preview",
      "source": "payments-api",
      "score": 12.970833333333333,
      "reason": "hard context: recent error",
      "excerpt": "{\"error\": \"upstream_timeout\", \"operation\": \"refund_preview\", \"invoice_id\": 4471, \"attempt\": 1, \"retryable\": true}",
      "excerpt_format": "plain",
      "selected_tokens": 35
    }
  ],
  "tokens_before": 1660,
  "tokens_after": 35,
  "tokens_saved": 1625,
  "records_available": 12,
  "records_selected": 1,
  "fallback_used": false,
  "selection_error": null,
  "reduction_ratio": 0.9789156626506024,
  "engine_latency_ms": 1.8176219999759269,
  "gate": {
    "engaged": true,
    "reason": "engage:needle"
  },
  "usage": {
    "outcome": "engaged",
    "charge_multiplier": "1.0",
    "currency": "USD"
  }
}
What you just watched

Three properties, visible in the responses above.

SELECTION, NOT REWRITING

Your own words survive

Every excerpt above is built from the record it came from. No second model writes replacement prose, so invoice numbers, tracking codes and policy wording arrive the way you sent them.

THE TASK DECIDES

No stored ranking to go stale

Decisions one and two send the same records and get different packets, because the question changed. Records ride in on the request. Nothing is stored between calls.

IT CAN DECLINE

Standing down is a result

The stand down decision returns your context intact, with a charge multiplier of zero on the call. An engine that only ever trims is an engine that trims when it should not.

All responses on this page are unedited output from the live API. Fields the page does not render were dropped from the stored copies, never changed, and every figure above is read out of those files at build time.

Now do it with your records.

This page replays a ticket we wrote. The interesting version is the one that runs on your traces, where the pile is yours and so is the number at the end.