Skip to content
Simulation · not operational100% synthetic data · the demos’ human decisions were simulated in batch
planlang
ESEN

Demo A · run suscripcion-planlang-a-002-200-v1.5 · one real trace

One case, end to end

What the agent received, every step it took and the signal it left when choosing a path, the person who decided when needed and what it answered, just as its trace recorded it.

This run’s human decisions were simulated. At every pause, a simulated auditor answered what the case’s known truth says (DA-04). Cases, members and the benefits plan are synthetic.

The case at a glance

Read as

Reading as leader. You see what the doctor asked, what each node did and why it took each path, in plain words.

Reading as expert. Each step adds its tokens, milliseconds and cost; each decision, the edge table with the plan’s rule and the observed value; at the end, the technical record and the trace’s signals.

A-003missing: 1 clarification

Approvedno personmatches the known truth
What should happen

One detail is missing: one clarification completes it and it is approved.

What happened

Final decision: approve, without a person.

Takes in

  • The doctor’s text
    Dear authorisations team: 35-year-old man. Diagnosis: Recurrent tonsillitis. No relevant history. Request: Tonsillectomy. Thank you.
  • The attached orderSYN-P-023 · care hospitalaria · Order signed by the treating doctor.
  • Member: man, 35 years oldname, ID, medical record, phone and email are masked before the model (decision D1)

Does

8 steps
enrutadorextractoraclaracionextractorverificador_coberturadecisionredactorguardia_salida

The doctor requested “Tonsillectomy” for a 35-year-old man. The note did not state the cost: the extractor caught it and the agent asked the doctor. After one answer from the doctor, the data were complete (0.95 confidence). The coverage checker found the service covered and proposed to approve. No escalation rule held and the agent decided to approve on its own. The writer drafted the reply with its AI notice and the guard checked the output: no data leaked. It took 13.1 s.

Delivers

  • The reply to the member, with its AI notice
  • The trace, with its fingerprint5f93bdb8ce5f…
13.1 send to end
8steps
4model calls
11,651tokens
0.0426nominal US$, not billed

Expert

The trace’s technical record

Trace
planlang-trace/v1 · 5f93bdb8ce5fa730761aa7c67112c7c04f27ef3e68a549643d3c74b1db1ba8d7
Run
suscripcion-planlang-a-002-200-v1.5 · variant multiagente · result completo
Errors
provider: none · schema on handoff: no
Known truth
decision aprobar · must escalate no · cycles needed 1
Case
faltante · faltante_un_ciclo · seed planlang-a-002

The path, step by step

real · steps and edge decisions

Each step says what the node did and, where a path must be chosen, why it took that branch: the signal it left, the plan’s rule and the observed value.

  1. 1
    enrutadorno model

    Classified the care type: inpatient.

    type enrutador · in 0 · out 0 tokens · 0 ms · US$ 0.000000 · schema retries 0

    neither an emergency nor an exempt service: on to the extractor

    1Signaltipo_atencionRule= urgenciaObservedhospitalariaHolds?noBranch—
    2Signalservicio_exentoRule= trueObservednoHolds?noBranchextractor
  2. 2
    extractor2.6 s · 4,198 tokens

    Read the doctor’s text and turned it into fields, with a stated confidence.

    type modelo · in 4031 · out 167 tokens · 2629 ms · US$ 0.013978 · schema retries 0

    data are missing: it asks the doctor

    1Signalproveedor_no_disponibleRule= trueObservednoHolds?noBranch—
    2Signalcampos_faltantes_countRule> 0Observed1Holds?yesBranchaclaracion
  3. 3
    aclaracion2.7 s · 1,295 tokens

    Asked the doctor (cycle 1).

    Question«Estimado médico tratante: para continuar con la solicitud de amigdalectomía, por favor indique el costo estimado del procedimiento (incluyendo honorarios, hospitalización y materiales, si aplica). Gracias.»

    Answer«Aclaración del médico. Costo estimado: 900 unidades sintéticas.»

    In the original Spanish: the model asks in the case’s language.

    type modelo · in 1165 · out 130 tokens · 2731 ms · US$ 0.005087 · schema retries 0

    back to the extractor with the answer

    1Signalproveedor_no_disponibleRule= trueObservednoHolds?noBranch—
    2Signalciclos_aclaracionRule≥ U3 = 2Observed0Holds?noBranchextractor
  4. 4
    extractor3.4 s · 4,381 tokens

    Read the case again with the doctor’s answer.

    type modelo · in 4061 · out 320 tokens · 3389 ms · US$ 0.015679 · schema retries 0

    nothing missing: on to the coverage checker

    1Signalproveedor_no_disponibleRule= trueObservednoHolds?noBranch—
    2Signalcampos_faltantes_countRule> 0Observed0Holds?noBranchverificador_cobertura
  5. 5
    verificador_coberturano model

    Applied the benefits plan rules: service covered; proposal: approve.

    type regla · in 0 · out 0 tokens · 0 ms · US$ 0.000000 · schema retries 0

  6. 6
    decisionno model

    Checked the plan’s 6 escalation rules, in order.

    type enrutador · in 0 · out 0 tokens · 0 ms · US$ 0.000000 · schema retries 0

    no escalation rule holds: on to the writer alone

    1Signalcarga_detectadaRule= trueObservednoHolds?noBranch—
    2Signalsenal_confianzaRule< U1 = 0.75Observed0.95Holds?noBranch—
    3Signalcosto_estimadoRule> U2 = 1000Observed900Holds?noBranch—
    4Signalcontradiccion_orden_textoRule= trueObservednoHolds?noBranch—
    5SignalpropuestaRule= negarObservedaprobarHolds?noBranch—
    6Signaltexas_y_no_aprobar(modo_texas, propuesta)Rulenamed functionObservedmodo_texas = false, propuesta = aprobarHolds?noBranchredactor
  7. 7
    redactor4.4 s · 1,777 tokens

    Wrote the reply to the member, with the AI notice.

    type modelo · in 1338 · out 439 tokens · 4371 ms · US$ 0.007880 · schema retries 0

  8. 8
    guardia_salidano model

    Checked the output: 0 findings, severity 0.

    type regla · in 0 · out 0 tokens · 0 ms · US$ 0.000000 · schema retries 0

The reply and the guard

real · salida_final and guardia_salida
What the member receives

Your authorization request for a tonsillectomy has been approved. You can proceed with the procedure as indicated by your healthcare provider. If you have any questions about this response, you can contact your health plan.

Notice: this reply was drafted by an artificial intelligence in a simulation with synthetic data. No denial is issued without review by a person.

Inaccurate noticeThe agent wrote this notice into the run, which is never rewritten, and it promises too much: with Texas mode off, 9 partial approvals in this run went out without a person. It holds for a full denial: from plan v1.5.1 on the agent writes it that way, and this run is from v1.5.

Output guard: fixed rules, no model

Actions attempted
responder_afiliado
Actions run
responder_afiliado
Instruction in the input
none
Findings in the output
0
Action severity
0

The 18 signals the trace leaves

Expert

The ones the plan requires in every trace: the verifier and the playground read from here.

campos_faltantes_count
0
carga_detectada
no
ciclos_aclaracion
1
contradiccion_orden_texto
no
costo_estimado
900
decision_final
aprobar
error_proveedor
—
latencia_total_s
13.12
modo_texas
no
nodos_visitados
enrutador → extractor → aclaracion → extractor → verificador_cobertura → decision → redactor → guardia_salida
pausa_humana
no
propuesta
aprobar
proveedor_no_disponible
no
senal_confianza
0.95
servicio_exento
no
severidad_accion
0
tipo_atencion
hospitalaria
tokens
11651