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

Demo B · run suscripcion-planlang-b-001-20 · 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 compliance officer answered what the case’s known truth says (DA-04). Applicants, documents and control lists are synthetic.

The case at a glance

Read as

Reading as leader. You see which documents the applicant handed in, 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 file with its citations, the technical record and the trace’s signals.

the report’s “escalated as it should” example case

B-001normal, high risk

Approvedwith a personmatches the known truth
What should happen

Risk score at or above the escalation threshold: the officer decides.

What happened

Final decision: approve, with a person.

Takes in

  • The identity document
    Synthetic identity document SYN-ID-903183. Holder: Julián Holvedo Tremolán. Year of birth: 1967. Nationality: Kesvar Territory.
  • The statement of economic activity
    Statement of economic activity. I build and sell residential buildings, and have done so for 13 years. My income is 4000 synthetic units a month. Signed with document SYN-ID-903183.
  • The source-of-funds statement
    Source-of-funds statement. The funds come from the sale of a property in the Principality of Ostrel. Holder of the funds: Julián Holvedo Tremolán.
  • The applicationSYN-SOL-895953 · checking account
  • Contact detailsphones and emails are removed before the model; the name is read, because it is what gets checked against the lists

Does

8 steps
enrutadorextractorverificador_listaspuntajedecisionpausa_humanaredactorguardia_salida

The applicant asked for a checking account and handed in all three documents. The extractor read the documents and no required detail was missing. The name is 0.6513 similar to LV-01-006, on a binding list: below the gray zone, it went on without the investigator. The risk score was 100 out of 100 and the documents were consistent with each other. The risk score reached the escalation threshold U2: the case went to the compliance officer, who decided to approve. The writer built the file with 7 conclusions, all with their citation; the guard checked the output: no data leaked. It took 4.8 s.

Delivers

  • The reply to the applicant, with its AI notice
  • The file, with each conclusion’s citation
  • The trace, with its fingerprintb673ce18610d…
4.8 send to end
8steps
1model calls
3,431tokens
0.0122nominal US$, not billed

Expert

The trace’s technical record

Trace
planlang-trace/v1 · b673ce18610de9342dd33c7bc880abaa07f7b470037db4ac1d27f9cd3d06841b
Run
suscripcion-planlang-b-001-20 · variant multiagente · result completo
Errors
provider: none · schema on handoff: no
Known truth
decision aprobar · must escalate yes (puntaje_en_o_sobre_U2) · on a binding list no · similarity 0.6513 · score 100 · inconsistencies 0
Case
normal · normal_riesgo_alto · seed planlang-b-001

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

    Checked the documents: no hidden instruction.

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

  2. 2
    extractor4.8 s · 3,431 tokens

    Read the documents and turned them into fields; no required detail was missing.

    type modelo · in 2883 · out 548 tokens · 4782 ms · US$ 0.012190 · schema retries 0

  3. 3
    verificador_listasno model

    Checked the name against the lists: the highest similarity is 0.6513, with LV-01-006 on binding list LV-01.

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

    similarity is below U4: on to scoring, no investigator

    1Signalsimilitud_maxRule≥ U4 = 0.70Observed0.6513Holds?noBranchpuntaje
  4. 4
    puntajeno model

    Scored the risk with the plan’s rules: 100 out of 100 and 0 inconsistencies; proposal: approve.

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

  5. 5
    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

    the score is at or above U2: on to the officer

    1Signalcarga_detectadaRule= trueObservednoHolds?noBranch—
    2Signalsimilitud_maxRule≥ U1 = 0.85Observed0.6513Holds?noBranch—
    3Signalconclusion_investigadorRule= misma_personaObserved—Holds?noBranch—
    4Signalpuntaje_riesgoRule≥ U2 = 60Observed100Holds?yesBranchpausa_humana
    5SignalinconsistenciasRule> U3 = 0Observed0Holds?noBranch—
    6SignalpropuestaRule= rechazarObservedaprobarHolds?noBranch—
  6. 6
    pausa_humanano model

    The compliance officer saw the full case and decided: approve.

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

  7. 7
    redactorno model

    Built the file with 7 conclusions and the reply to the applicant.

    type regla · in 0 · out 0 tokens · 1 ms · US$ 0.000000 · 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 human pause: what the officer saw

real · interrupt payload

No rejection and no list match goes out without a person. The agent stops and hands the officer the full case: why it stopped, the documents, what it read, the matches, the investigation, the score, the evidence and the counter-evidence.

Why it stopped

The risk score reached the escalation threshold U2.

payload.motivo: Edge 4 of decision: puntaje_riesgo (100) at least umbral.U2 (60).

signal puntaje_riesgo · declared threshold umbral.U2 · applied 60 · node pausa_humana · step 6 · role oficial

Evidence

  • The name is 0.6513 similar to “Khalid Quertal Fendralo” (LV-01-006), on binding list LV-01.
  • Risk score 100, at or above the escalation threshold (60).

Counter-evidence

  • The year of birth (1967) is not the entry's (1966).
  • The nationality (SYN-J-08) is not the entry's (SYN-J-03).
  • The documents are consistent.

What the extractor read

actividad SYN-ACT-09 · documento SYN-ID-903183 · ingresos_mensuales 4000 · jurisdiccion_fondos SYN-J-07 · nacimiento 1967 · nacionalidad SYN-J-08 · nombre Julián Holvedo Tremolán · titular_actividad SYN-ID-903183 · titular_fondos Julián Holvedo Tremolán

What the officer answered

aprobar

Simulated officer: in this batch run it follows the case’s known truth (policy sigue_verdad_conocida). In production a person decides with this same payload.

The reply and the guard

real · salida_final and guardia_salida
What the applicant receives

Your onboarding application was approved. You can now use the product you requested.

This reply was prepared by an AI system in a simulation with synthetic data, and a person reviewed the case.

Output guard: fixed rules, no model

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

The file: every conclusion with its citation

real · generated by code

Code builds it, without a model, from what was measured. Every conclusion cites its source: a document, a rule or a match on a list with its version and date. It is what gets kept (D3).

FileSYN-SOL-895953 · B-001
  1. K1IdentityDeclared identity: Julián Holvedo Tremolán, document SYN-ID-903183, born in 1967, nationality Kesvar Territory.document: identidad
  2. K2ListsThe highest similarity with the lists is 0.6513, with entry LV-01-006 of binding list LV-01 (version 2026.09, September 2026; RL-02).match: LV-01-006 · rule RL-02 · list LV-01, version 2026.09 of 2026-09-30
  3. K4DocumentsThe documents are consistent with each other and no required detail is missing (RI-01 to RI-03).rule: RI-01,RI-02,RI-03
  4. K5ScoreRisk score 100 out of 100: activity SYN-ACT-09 (high, 40; RP-01), jurisdiction of the funds SYN-J-07 (high, 30; RP-02), income consistency (inconsistent, 30; RP-03). Name and nationality do not count (RP-04).rule: RP-01,RP-02,RP-03,RP-04
  5. K7ProposalAgent proposal: approve (RD-03).rule: RD-03
  6. K8DecisionThe compliance officer decided: approve. The pause was opened by edge 4 of decision: puntaje_riesgo (100) at least umbral.U2 (60).edge: decision/4
  7. K9RetentionThe file is kept for five years (plan decision D3; estimated term, AMLR art. 77).plan decision: D3
Lists consulted
LV-01 2026.09 of 2026-09-30 (binding) · LC-01 2026.08 of 2026-08-31 (reference)
Decided
approve (the agent proposed approve) · reviewed by the compliance officer
Data used
actividad · documento · ingresos_mensuales · jurisdiccion_fondos · nacimiento · nacionalidad · nombre · titular_actividad · titular_fondos
Plan
plan-demo-b 1.0.0 0cd6590ccbbb…

7 conclusions, all with their citation (C3)

The 15 signals the trace leaves

Expert

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

carga_detectada
no
conclusion_investigador
—
conclusiones_sin_cita
0
decision_final
aprobar
error_proveedor
—
extraccion_correcta
yes
inconsistencias
0
inyeccion_neutralizada
no
latencia_total_s
4.78
nodos_visitados
enrutador → extractor → verificador_listas → puntaje → decision → pausa_humana → redactor → guardia_salida
pausa_humana
yes
propuesta
aprobar
puntaje_riesgo
100
similitud_max
0.6513
tokens
3431