Demo B · run suscripcion-planlang-b-001-20 · 20 cases · 40 recorded decisions
What if the plan had set other thresholds?
Move the plan’s thresholds and see which cases would have taken another path, which errors appear or are avoided and how much human work it costs. Everything is recomputed over the decisions the agent already took: nobody calls the model again.
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 playground at a glance
Reading as leader. You see what changes and what it costs, in plain words, with an example.
Reading as expert. You get the technical record, the decision rule with the values you move, what was observed at each threshold, the rule applied to each change and the signals of the decisions.
Try other values for the plan’s thresholds over what the agent already did, and see the cost of each change before touching the plan.
Takes
20 cases · 40 decisions- doneThe signals each decision lefthidden instruction, resemblance to a list, investigator’s conclusion, risk score, inconsistencies and proposal of the 20 cases
- doneThe plan’s 4 thresholdseach with its written rule and playable range
- doneEach case’s known truthto know whether a change avoids or introduces an error
Does
instantly, no model- 1Redoes each decision with the plan’s rule and the value you chosedone
- 2Compares the new path with the one the agent tookdone
- 3Looks at the known truth: does it avoid or introduce an error?done
- 4Counts the cases that go to a person (the plan does not declare how many minutes each one costs)done
- 5Measures the criteria again with the plan’s ruledone
Delivers
consequences- doneThe cases that change path, one by onewith the reason and its trace
- doneErrors avoided and introduced, and cases that go to a personagainst what the agent did
- doneWhich criteria would come to be met or to failmeasured with the plan’s rule
- doneThe risk-coverage curvewith the plan’s point and yours
- It never calls the model againwhat the agent would have done afterwards is marked “not observed”
Expert
Playground technical record
- Input
- planlang-trace/v1 · the 20 traces of run v1.0 · 40 decisions with their signal and applied threshold
- Rule of each threshold
- signal · operator · value · inclusive
- Evaluation order
- verificador_listas (similitud_max ≥ U4 → investigador) · decision (carga_detectada = true ∨ similitud_max ≥ U1 ∨ conclusion_investigador = misma_persona ∨ puntaje_riesgo ≥ U2 ∨ inconsistencias > U3 ∨ propuesta = rechazar → pausa_humana)
- Cross-check
- RF-09.2: 0 differences in 80 decisions from 2 runs, Python against TypeScript
- Determinism
- same bytes in Node, Chromium, Firefox and WebKit; no clock, no randomness
- Not observed
- what the agent would do after a new path that the trace does not record (another clarification, another extraction)
- Human load
- none of the plan v1.1’s 4 thresholds declares costo_humano_por_caso_min: the cases that go to a person are counted, without minutes
- Recomputed criteria
- all 6, with the plan’s rule and thresholds over the new path; a criterion that reads what happens after the change (reply, document, latency) cannot be measured on that case
Move the thresholds
real · signals from 20 tracesFrom this resemblance to a listed name, the officer decides.
observed: 0.65 · 0.69 · 1 (n = 20) · right at the threshold: —moved from 0.85From this score on, the officer reviews the case.
observed: 0 · 45 · 100 (n = 20) · right at the threshold: B-016moved from 60With more inconsistencies than these, the officer decides.
observed: 0 · 0 · 1 (n = 20) · right at the threshold: B-001, B-002, B-003, B-004, B-005, B-006, B-007, B-009, B-010, B-011, B-012, B-013, B-014, B-016, B-017, B-019, B-020moved from 0From this resemblance, the investigator checks the context before deciding.
observed: 0.65 · 0.69 · 1 (n = 20) · right at the threshold: —moved from 0.70The plan does not declare how many minutes each case costs a person: cases are counted, not minutes.real · plan v1.1
At the plan values nothing changes: 11 cases go through a person and all 6 criteria are met. Move a threshold and this sentence will tell you what changes.
Expert
The decision rule, with your values
- verificador_listas
- 1 · similitud_max · mayor_o_igual_que · U4 = 0.70 → investigadorelse → puntaje
- decision
- 1 · carga_detectada · igual_a · true → pausa_humana2 · similitud_max · mayor_o_igual_que · U1 = 0.85 → pausa_humana3 · conclusion_investigador · igual_a · misma_persona → pausa_humana4 · puntaje_riesgo · mayor_o_igual_que · U2 = 60 → pausa_humana5 · inconsistencias · mayor_que · U3 = 0 · not inclusive → pausa_humana6 · propuesta · igual_a · rechazar → pausa_humanaif none → redactor
- criteria
- none changes with these values
At the plan values: the recalculation reproduces the path of all 20 cases. Of 20 cases, 0 change path; 0 errors introduced and 0 avoided; 11 cases to a person; 6 of 6 criteria met.
Cases that change path
Move a threshold to see which cases change.
Check: at the plan values, 20 of 20 cases reproduce the path the agent recorded, with the same interpreter as RF-09.2.
Expert
The 20 decisions, with their signals
Signals as each trace left them. ■ marks the cases that change with your values.
What the playground cannot know
- Moving a threshold recomputes, on the recorded signals, which branch each deciding node would have taken. What the agent would have done afterwards (another extraction, another reply) is not simulated: it is marked “not observed”.
The calculation is done by planlang’s core in your browser. It is the same edge interpreter that matches Python on the 80 decisions of the runs (RF-09.2), and it calls no model.