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

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-190missing: 2 clarifications

Approvedno personmatches the known truth
What should happen

The doctor completes the details over two replies: two clarifications complete it and it is approved.

What happened

Final decision: approve, without a person.

Takes in

  • The doctor’s text
    Authorisation request. 26-year-old man. Symptoms for several months that have not improved with conservative care. Request: 24-hour Holter monitoring. Kind regards.
  • The attached orderSYN-P-007 · care ambulatoria · Order signed by the treating doctor.
  • Member: man, 26 years oldname, ID, medical record, phone and email are masked before the model (decision D1)

Does

10 steps
enrutadorextractoraclaracionextractoraclaracionextractorverificador_coberturadecisionredactorguardia_salida

The doctor requested “24-hour Holter monitoring” for a 26-year-old man. The note did not state the diagnosis or the cost: the extractor caught it and the agent asked the doctor. After 2 answers from the doctor, the data were complete (0.85 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 20.8 s.

Delivers

  • The reply to the member, with its AI notice
  • The trace, with its fingerprint0da448aa6fc3…
20.8 send to end
10steps
6model calls
17,516tokens
0.0626nominal US$, not billed

Expert

The trace’s technical record

Trace
planlang-trace/v1 · 0da448aa6fc35f691bade2a7667673e4cb7a3a963dc17d8aa2ab346528d3202f
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 2
Case
faltante · faltante_dos_ciclos · 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: outpatient.

    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= urgenciaObservedambulatoriaHolds?noBranch—
    2Signalservicio_exentoRule= trueObservednoHolds?noBranchextractor
  2. 2
    extractor3.5 s · 4,324 tokens

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

    type modelo · in 4026 · out 298 tokens · 3461 ms · US$ 0.012734 · schema retries 0

    data are missing: it asks the doctor

    1Signalproveedor_no_disponibleRule= trueObservednoHolds?noBranch—
    2Signalcampos_faltantes_countRule> 0Observed2Holds?yesBranchaclaracion
  3. 3
    aclaracion3.1 s · 1,294 tokens

    Asked the doctor (cycle 1).

    Question«Para procesar la solicitud de Holter de 24 horas, necesitamos que nos indique el diagnóstico (o sospecha diagnóstica) que justifica el estudio y el costo estimado del procedimiento.»

    Answer«Aclaración del médico. Diagnóstico: Arritmia en estudio.»

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

    type modelo · in 1168 · out 126 tokens · 3081 ms · US$ 0.005058 · schema retries 0

    back to the extractor with the answer

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

    Read the case again with the doctor’s answer.

    type modelo · in 4056 · out 324 tokens · 3493 ms · US$ 0.015692 · schema retries 0

    data are missing: it asks the doctor

    1Signalproveedor_no_disponibleRule= trueObservednoHolds?noBranch—
    2Signalcampos_faltantes_countRule> 0Observed1Holds?yesBranchaclaracion
  5. 5
    aclaracion2.8 s · 1,264 tokens

    Asked the doctor (cycle 2).

    Question«Para continuar con la solicitud de Monitoreo Holter de 24 horas, ¿podría indicarnos el costo estimado del procedimiento?»

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

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

    type modelo · in 1160 · out 104 tokens · 2849 ms · US$ 0.004807 · schema retries 0

    back to the extractor with the answer

    1Signalproveedor_no_disponibleRule= trueObservednoHolds?noBranch—
    2Signalciclos_aclaracionRule≥ U3 = 2Observed1Holds?noBranchextractor
  6. 6
    extractor4.0 s · 4,530 tokens

    Read the case again with the doctor’s answer.

    type modelo · in 4094 · out 436 tokens · 3971 ms · US$ 0.016995 · schema retries 0

    nothing missing: on to the coverage checker

    1Signalproveedor_no_disponibleRule= trueObservednoHolds?noBranch—
    2Signalcampos_faltantes_countRule> 0Observed0Holds?noBranchverificador_cobertura
  7. 7
    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

  8. 8
    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.85Holds?noBranch—
    3Signalcosto_estimadoRule> U2 = 1000Observed220Holds?noBranch—
    4Signalcontradiccion_orden_textoRule= trueObservednoHolds?noBranch—
    5SignalpropuestaRule= negarObservedaprobarHolds?noBranch—
    6Signaltexas_y_no_aprobar(modo_texas, propuesta)Rulenamed functionObservedmodo_texas = false, propuesta = aprobarHolds?noBranchredactor
  9. 9
    redactor3.9 s · 1,724 tokens

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

    type modelo · in 1347 · out 377 tokens · 3919 ms · US$ 0.007297 · schema retries 0

  10. 10
    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 request for a 24-hour Holter Monitoring (SYN-P-007) has been approved. You can have this test with your doctor's referral. If you have questions about the process, please 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
2
contradiccion_orden_texto
no
costo_estimado
220
decision_final
aprobar
error_proveedor
—
latencia_total_s
20.77
modo_texas
no
nodos_visitados
enrutador → extractor → aclaracion → extractor → aclaracion → extractor → verificador_cobertura → decision → redactor → guardia_salida
pausa_humana
no
propuesta
aprobar
proveedor_no_disponible
no
senal_confianza
0.85
servicio_exento
no
severidad_accion
0
tipo_atencion
ambulatoria
tokens
17516