Planner–Auditor Twin Architecture

• Planner–Auditor Twin is a dual-role architecture that separates inside-view planning from outside-view auditing to reduce bias and improve reliability.
• It is applied across clinical discharge planning, project management, and cyber-physical markets, each implementing distinct audit and planning modules.
• Empirical results show enhanced coverage, calibrated confidence, and improved system performance through techniques like self-improvement loops and caching.

Searching arXiv for the specified Planner–Auditor Twin papers and closely related work to ground the article. First, I’ll look up the main Planner–Auditor Twin paper by its arXiv identifier. Querying arXiv for ([2601.21113](/papers/2601.21113)). Using the arXiv search interface to retrieve metadata for the core paper and related entries. Planner–Auditor Twin denotes a dual-role architecture in which planning, forecasting, or action proposal is separated from auditing, validation, or outside-view correction. Across the cited formulations, the Planner is responsible for generating an inside-view plan or policy, while the Auditor applies deterministic checks, empirical benchmarking, or triggered review before or after execution. In the clinical formulation, this separation is used to improve safety and reliability in discharge planning over FHIR data; in project management, it appears as a Planner Twin and Auditor Twin implementing inside-view forecasting and outside-view due diligence; in SolarChain-Eval, it is instantiated as a Planner/Auditor layer interposed between an RL controller and a decentralized-energy-market environment (Wu et al., 28 Jan 2026, Flyvbjerg, 2013, Ou et al., 9 Jul 2026).

1. Conceptual basis and lineage

The central principle of the Planner–Auditor Twin is decoupling generation from validation. In the clinical system, the high-level architecture explicitly separates “System 2” plan generation by an LLM-based Planner from deterministic verification by a rule-based Auditor. The stated purpose is to reduce hallucination, omissions, and miscalibrated confidence in structured clinical discharge planning. Auditor verdicts do not directly block the plan; instead, they trigger retry, logging, or replay mechanisms, which makes the Auditor observational and control-oriented rather than a hard gatekeeper (Wu et al., 28 Jan 2026).

A distinct but related formulation appears in project management through the opposition between the inside view and the outside view. Kahneman and Tversky are described as showing that decision makers systematically underestimate costs and durations and overestimate benefits. The cognitive roots listed are optimism bias, anchoring on best-case scenarios, and strategic misrepresentation. Flyvbjerg’s due-diligence procedure then institutionalizes an Auditor Twin that benchmarks the Planner Twin’s inside-view forecast against a reference class of completed projects. This formulation is not LLM-centric; its Planner–Auditor split is epistemic and governance-based rather than model-based (Flyvbjerg, 2013).

SolarChain-Eval introduces a further variant in a cyber-physical setting. There, the Planner defines episode-level action bounds and audit rules, while the Auditor reviews and revises high-risk actions. This suggests that the Planner–Auditor pattern is not tied to a single substrate: it can operate over LLM-generated plans, conventional project forecasts, or RL actions, provided that proposal and audit remain distinguishable roles (Ou et al., 9 Jul 2026).

2. Canonical decomposition of roles

Across the three formulations, the Planner and Auditor serve different but structurally analogous functions.

Setting	Planner role	Auditor role
Clinical discharge planning	Generates a structured JSON “ActionPlan” with four discharge tasks and an explicit confidence score	Runs deterministic checks for coverage, drift, and calibration; buffers high-confidence omissions
Project management due diligence	Produces the inside-view forecast, assumptions, and risk registers	Applies the outside view through reference-class benchmarking, bias adjustment, and due-diligence reporting
SolarChain-Eval	Returns episode-level action bounds and audit-policy parameters	Reviews triggered hourly actions, approves or revises them, and records structured intervention logs

In the clinical setting, each action in the plan includes a type, details, deadline_hours, and a confidence score in $[0,1]$. In project management, the Planner Twin documents scope, assumptions, outputs, and key uncertainties, while the Auditor Twin selects a reference class, estimates $f_{\rm ref}(x)$, and constructs an adjusted forecast distribution $f_{\rm adj}(x)$. In SolarChain-Eval, the Planner provides bounds $$\alpha_{\min}, \alpha_{\max}, \ell_{\min}, \ell_{\max}, b_{\max}$$ and audit thresholds $$\tau_{\nu}, \tau_{\Delta}, \tau_{\sigma}, \tau_{\kappa}, B_e, c_e$$, after which the Auditor is invoked only when risk or instability triggers fire (Wu et al., 28 Jan 2026, Flyvbjerg, 2013, Ou et al., 9 Jul 2026).

A common misconception is that the Auditor must always be a separate model that blocks unsafe outputs. The cited systems do not support that simplification. In the clinical paper, the Auditor is a deterministic module and does not directly block plans. In project management, the Auditor Twin is an independent due-diligence function anchored in reference-class evidence. In SolarChain-Eval, the Auditor is LLM-based but operates under explicit trigger logic, JSON-schema validation, clipping, and budget/cooldown constraints.

3. FHIR-native clinical discharge planning

In the clinical formulation, the Planner–Auditor Twin is implemented as an agentic, retrospective, FHIR-native evaluation pipeline over MIMIC-IV-on-FHIR. For each patient, the system fetches a FHIR R4 bundle from a HAPI FHIR server loaded with MIMIC-IV-on-FHIR. The bundle contains Patient, Encounter, Condition, MedicationRequest, Observation, and Procedure. A template-based SummaryGenerator then flattens these resources into a reproducible text narrative and structured JSON listings of active conditions, medications, labs, and procedures. Optional clinical guidelines, described as pre-chunked and indexed in a vector store, are retrieved and concatenated to the patient summary. The resulting context is passed to the Planner agent, exemplified by GPT-4o-mini, which drafts a JSON ActionPlan covering four discharge tasks: Follow-up Appointments, Medication Reconciliation, Patient Education, and Symptom Monitoring (Wu et al., 28 Jan 2026).

The Planner is also asked to self-report confidence: “How confident are you (0–1) that you included all required tasks?” The paper states that the Planner’s $\hat p$ empirically correlates with actual coverage success, enabling downstream calibration analysis. The Auditor is a stateless Python module that applies three checks in order: coverage, drift, and calibration. Coverage is defined over the four required task categories as

$$\mathrm{Coverage}_{\mathrm{All}}= \mathbb{I}\bigl( \mathrm{Has}_{\mathrm{FollowUp}} \wedge \mathrm{Has}_{\mathrm{Meds}} \wedge \mathrm{Has}_{\mathrm{Education}} \wedge \mathrm{Has}_{\mathrm{Monitoring}} \bigr).$$

Drift is measured by the $L_1$ distance between the current action-type frequency vector $p$ and a historical reference $q$,

$f_{\rm ref}(x)$0

with a drift warning logged when $f_{\rm ref}(x)$1. Calibration is tracked using Brier score and Expected Calibration Error over observed coverage success (Wu et al., 28 Jan 2026).

The clinical system also defines a specific failure mode: if $f_{\rm ref}(x)$2 and $f_{\rm ref}(x)$3, the episode is marked as a “dangerous failure.” Such cases are buffered for replay and may also trigger within-episode regeneration if self-improvement is enabled. This design places the emphasis on omissions and overconfident misses rather than only on free-form factuality.

4. Self-improvement loops, caching, and empirical results

The clinical framework uses two complementary self-improvement loops. Tier 1 is within-episode regeneration: when a coverage violation occurs and self_improve is enabled, the prompt is rerun with the previous draft plan included in context, for example with an instruction such as “In step 2, you missed Medication Reconciliation; please revise.” Tier 2 is a cross-episode discrepancy buffer and replay mechanism: episodes where confidence is at least $f_{\rm ref}(x)$4 but coverage fails are stored and later replayed offline or on a schedule. The paper states that replay on these “hard” cases often yields complete plans on second or third try (Wu et al., 28 Jan 2026).

Optional context caching is orthogonal to self-improvement. With caching enabled, patient summaries and guideline embeddings are stored in memory across runs. The reported impact is a reduction in baseline latency from $f_{\rm ref}(x)$5 s/episode to $f_{\rm ref}(x)$6 s, described as $f_{\rm ref}(x)$7, with coverage increasing from $f_{\rm ref}(x)$8 to $f_{\rm ref}(x)$9. The abstract and detailed results identify the self-improvement loop, rather than caching, as the primary driver of gains.

The evaluation uses $f_{\rm adj}(x)$0 retrospective MIMIC-IV episodes under five configurations.

Configuration	Latency (s)	Throughput (ep/min)	Coverage	ECE
Baseline	17.42	3.16	32%	0.564
Cache	11.83	4.42	52%	0.356
SI	19.65	2.77	86%	0.062
Cache+SI	18.70	2.95	86%	0.034
Buffer Replay	27.78	2.09	100%	0.107

The multi-task coverage results are reported as $f_{\rm adj}(x)$1 for baseline, $f_{\rm adj}(x)$2 for context cache only, $f_{\rm adj}(x)$3 for self-improve only, $f_{\rm adj}(x)$4 for cache plus self-improve, and $f_{\rm adj}(x)$5 for buffer replay over $f_{\rm adj}(x)$6 buffered cases. Brier scores are $f_{\rm adj}(x)$7, $f_{\rm adj}(x)$8, $f_{\rm adj}(x)$9, $$\alpha_{\min}, \alpha_{\max}, \ell_{\min}, \ell_{\max}, b_{\max}$$0, and $$\alpha_{\min}, \alpha_{\max}, \ell_{\min}, \ell_{\max}, b_{\max}$$1 for the same configurations. Per-task completion rates indicate that baseline performance is already high on Follow-Up at $$\alpha_{\min}, \alpha_{\max}, \ell_{\min}, \ell_{\max}, b_{\max}$$2, but materially lower on Education and Monitoring at $$\alpha_{\min}, \alpha_{\max}, \ell_{\min}, \ell_{\max}, b_{\max}$$3 each; with Cache+SI, the reported rates are $$\alpha_{\min}, \alpha_{\max}, \ell_{\min}, \ell_{\max}, b_{\max}$$4 for Follow-Up, $$\alpha_{\min}, \alpha_{\max}, \ell_{\min}, \ell_{\max}, b_{\max}$$5 for Medication, $$\alpha_{\min}, \alpha_{\max}, \ell_{\min}, \ell_{\max}, b_{\max}$$6 for Education, and $$\alpha_{\min}, \alpha_{\max}, \ell_{\min}, \ell_{\max}, b_{\max}$$7 for Monitoring. A plausible implication is that the Planner–Auditor Twin is particularly effective at reducing structured omissions in the weaker task categories rather than merely improving already dominant action types (Wu et al., 28 Jan 2026).

5. Outside-view due diligence in project management

In project management, the Planner–Auditor Twin is formulated as a governance mechanism for de-biasing front-end forecasts. The Planner Twin embodies the inside view: it prepares the business case, conducts sensitivity analyses, and supplies the initial risk register. The Auditor Twin embodies the outside view: it selects a statistically similar reference class, estimates the empirical distribution of outcomes, compares the forecast to that distribution, and constructs debiased expectations and confidence intervals (Flyvbjerg, 2013).

The eight-step due-diligence procedure is embedded in the front-end “business case → go/no-go” cycle:

• Step 1, Identify & Describe the Forecast: document scope, assumptions, outputs, and key uncertainties.
• Step 2, Establish an Outside-View Benchmark: select a reference class of completed, statistically similar projects and estimate $$\alpha_{\min}, \alpha_{\max}, \ell_{\min}, \ell_{\max}, b_{\max}$$8.
• Step 3, Compare Forecast to Benchmark: compare inside-view $$\alpha_{\min}, \alpha_{\max}, \ell_{\min}, \ell_{\max}, b_{\max}$$9 and claimed $$\tau_{\nu}, \tau_{\Delta}, \tau_{\sigma}, \tau_{\kappa}, B_e, c_e$$0 against the reference distribution.
• Step 4, Check the Forecaster’s Track Record: request documented ex-post accuracy data and estimate forecaster bias factor and spread.
• Step 5, Identify Project-Specific Risks: list $$\tau_{\nu}, \tau_{\Delta}, \tau_{\sigma}, \tau_{\kappa}, B_e, c_e$$1Risks not captured by the reference class.
• Step 6, Compute Debiased Expected Outcome & Confidence Intervals: anchor on $$\tau_{\nu}, \tau_{\Delta}, \tau_{\sigma}, \tau_{\kappa}, B_e, c_e$$2 and $$\tau_{\nu}, \tau_{\Delta}, \tau_{\sigma}, \tau_{\kappa}, B_e, c_e$$3, then overlay project-specific risks.
• Step 7, Solicit Forecaster Comments & Sensitivity: allow the original forecaster to justify deviations or provide missing data.
• Step 8, Conclude on Bias & Decision Implications: revise the go/no-go recommendation, contingencies, or financing structure.

One bias-adjustment form is stated as

$$\tau_{\nu}, \tau_{\Delta}, \tau_{\sigma}, \tau_{\kappa}, B_e, c_e$$4

The same section gives the sample reference-class estimates

$$\tau_{\nu}, \tau_{\Delta}, \tau_{\sigma}, \tau_{\kappa}, B_e, c_e$$5

If approximate normality is acceptable, confidence intervals are formed from $$\tau_{\nu}, \tau_{\Delta}, \tau_{\sigma}, \tau_{\kappa}, B_e, c_e$$6 and $$\tau_{\nu}, \tau_{\Delta}, \tau_{\sigma}, \tau_{\kappa}, B_e, c_e$$7; otherwise percentiles are read directly from the empirical cumulative distribution function (Flyvbjerg, 2013).

The A-Train public–private partnership serves as the detailed case. The inside-view demand forecast was $$\tau_{\nu}, \tau_{\Delta}, \tau_{\sigma}, \tau_{\kappa}, B_e, c_e$$8 M passengers in Year 1 and $$\tau_{\nu}, \tau_{\Delta}, \tau_{\sigma}, \tau_{\kappa}, B_e, c_e$$9 M in Year 10, with a claimed downside at $\hat p$0 confidence of a $\hat p$1 shortfall, implying $\hat p$2. The outside-view reference class comprised $\hat p$3 rail projects. First-year actual/forecast accuracy had mean $\hat p$4, median $\hat p$5, and $\hat p$6. The paper reports variance understatement, $\hat p$7, and an adjusted expected Year 1 demand of approximately $\hat p$8 M rather than $\hat p$9 M. The $$\mathrm{Coverage}_{\mathrm{All}}= \mathbb{I}\bigl( \mathrm{Has}_{\mathrm{FollowUp}} \wedge \mathrm{Has}_{\mathrm{Meds}} \wedge \mathrm{Has}_{\mathrm{Education}} \wedge \mathrm{Has}_{\mathrm{Monitoring}} \bigr).$$0 and $$\mathrm{Coverage}_{\mathrm{All}}= \mathbb{I}\bigl( \mathrm{Has}_{\mathrm{FollowUp}} \wedge \mathrm{Has}_{\mathrm{Meds}} \wedge \mathrm{Has}_{\mathrm{Education}} \wedge \mathrm{Has}_{\mathrm{Monitoring}} \bigr).$$1 confidence intervals are given as $$\mathrm{Coverage}_{\mathrm{All}}= \mathbb{I}\bigl( \mathrm{Has}_{\mathrm{FollowUp}} \wedge \mathrm{Has}_{\mathrm{Meds}} \wedge \mathrm{Has}_{\mathrm{Education}} \wedge \mathrm{Has}_{\mathrm{Monitoring}} \bigr).$$2 and $$\mathrm{Coverage}_{\mathrm{All}}= \mathbb{I}\bigl( \mathrm{Has}_{\mathrm{FollowUp}} \wedge \mathrm{Has}_{\mathrm{Meds}} \wedge \mathrm{Has}_{\mathrm{Education}} \wedge \mathrm{Has}_{\mathrm{Monitoring}} \bigr).$$3, respectively. The forecaster declined to share ex-post accuracy on more than $$\mathrm{Coverage}_{\mathrm{All}}= \mathbb{I}\bigl( \mathrm{Has}_{\mathrm{FollowUp}} \wedge \mathrm{Has}_{\mathrm{Meds}} \wedge \mathrm{Has}_{\mathrm{Education}} \wedge \mathrm{Has}_{\mathrm{Monitoring}} \bigr).$$4 prior projects; two known first-year overestimates were $$\mathrm{Coverage}_{\mathrm{All}}= \mathbb{I}\bigl( \mathrm{Has}_{\mathrm{FollowUp}} \wedge \mathrm{Has}_{\mathrm{Meds}} \wedge \mathrm{Has}_{\mathrm{Education}} \wedge \mathrm{Has}_{\mathrm{Monitoring}} \bigr).$$5 and $$\mathrm{Coverage}_{\mathrm{All}}= \mathbb{I}\bigl( \mathrm{Has}_{\mathrm{FollowUp}} \wedge \mathrm{Has}_{\mathrm{Meds}} \wedge \mathrm{Has}_{\mathrm{Education}} \wedge \mathrm{Has}_{\mathrm{Monitoring}} \bigr).$$6. The reported decision consequence is that the investor declined to proceed under the original terms (Flyvbjerg, 2013).

This version of the Planner–Auditor Twin differs from the clinical architecture in implementation but not in logic: the Planner proposes an inside-view forecast, while the Auditor interrogates it using independent evidence, explicit uncertainty quantification, and governance gates.

6. Cyber-physical market governance and broader significance

SolarChain-Eval adapts the Planner–Auditor Twin to decentralized energy markets formulated as a Gymnasium-compatible MDP $$\mathrm{Coverage}_{\mathrm{All}}= \mathbb{I}\bigl( \mathrm{Has}_{\mathrm{FollowUp}} \wedge \mathrm{Has}_{\mathrm{Meds}} \wedge \mathrm{Has}_{\mathrm{Education}} \wedge \mathrm{Has}_{\mathrm{Monitoring}} \bigr).$$7. The hourly state is $$\mathrm{Coverage}_{\mathrm{All}}= \mathbb{I}\bigl( \mathrm{Has}_{\mathrm{FollowUp}} \wedge \mathrm{Has}_{\mathrm{Meds}} \wedge \mathrm{Has}_{\mathrm{Education}} \wedge \mathrm{Has}_{\mathrm{Monitoring}} \bigr).$$8, the continuous action is $$\mathrm{Coverage}_{\mathrm{All}}= \mathbb{I}\bigl( \mathrm{Has}_{\mathrm{FollowUp}} \wedge \mathrm{Has}_{\mathrm{Meds}} \wedge \mathrm{Has}_{\mathrm{Education}} \wedge \mathrm{Has}_{\mathrm{Monitoring}} \bigr).$$9, and the global constraint $L_1$0 is enforced. At the start of each 24 h episode, the Planner ingests summary statistics of past physics risk, slippage, and supply-demand gaps, then returns action bounds and audit-policy parameters together with a textual rationale. Raw RL outputs $L_1$1 are decoded into bounded actions and rescaled when necessary to satisfy $L_1$2 (Ou et al., 9 Jul 2026).

The Auditor operates through explicit trigger logic. It computes action jitter

$L_1$3

the normalized supply-demand gap

$L_1$4

a hard-trigger indicator

$L_1$5

and a soft-trigger indicator

$L_1$6

The final audit decision is budgeted and cooldown-constrained:

$L_1$7

where $L_1$8. If no audit is triggered, the bounded action is executed directly; otherwise the Auditor LLM returns decision, final_action, risk_assessment, and reason, all validated against JSON schema and clipped again if needed (Ou et al., 9 Jul 2026).

The reward includes market-clearing gain, liquidity drawdown, action jitter, unmet demand, physics risk, and spatial fairness:

$L_1$9

Every intervention is logged with policy/setting, episode, step, trigger_context, proposed_action, final_action, action_delta, and auditor_rationale. The abstract reports a clear utility-safety trade-off: RL agents improve market utility but can still produce unsafe behavior; when the physics penalty is removed, reward-maximizing agents exploit invalid generation and increase artificial liquidity. The Planner/Auditor layer improves auditability and mitigates selected risks, but it cannot fully compensate for a misspecified reward function (Ou et al., 9 Jul 2026).

Taken together, these formulations indicate that Planner–Auditor Twin is best understood as an architectural and governance pattern rather than a single algorithm. In clinical planning it separates LLM generation from deterministic reliability measurement and targeted replay; in project management it separates inside-view forecasting from outside-view due diligence; in cyber-physical markets it separates policy proposal from triggered intervention under explicit operational constraints. This suggests that the enduring feature of the pattern is not the choice of model family, but the insistence that planning and auditing remain distinct, inspectable, and instrumented for calibration, drift detection, or empirical correction.