neural-bridge.dev
active · since Jun 2026

Bellwether

A private compliance workbench for DORA, the UK Critical Third Parties regime, NIS2, and the Korea Network Act. Combines regime-isolated RFI reuse, a fail-closed cross-family staleness guardrail, an independence-discounted Data Hub semantic layer, 4-route multi-question engagement triage, and 19 regulator personas.

Bellwether is a private regulatory verification, RFI historical reuse, and supervisory submission workbench for Critical Third Party Providers (CTPPs) operating under DORA, the UK Critical Third Parties (UK CTP) regime, NIS2, and South Korea’s Information and Communications Network Act (Korea Network Act). It is not open source.

Bellwether is built on four integrated pillars:

  1. RFI Reuse Engine & 4-Route Engagement Workbench (src/rfi_reuse/): Matches single questions or 20-to-50 question supervisory packs against a regime-isolated vector library, classifies every item into Routes A / B / C / D (with an Incident Path gate and a Route D legal privilege lock), runs a Fail-Closed Temporal Staleness Guardrail on an independent model family, and exports submissions with a W3C PROV-JSON Evidence Appendix.
  2. The Regulatory Semantic Layer - Data Hub (src/data_hub/): Scores canonical golden facts with independence-discounted corroboration (derived_from root-ancestor deduplication) and additive human verification uplift, injects golden facts into the staleness judge, scans the corpus for self-contradictions, and automatically flags dependent RFI answers stale when a canonical fact changes.
  3. 19-Regulator Sufficiency Panel (src/orchestrator/, src/personas/): Nineteen supervisory personas (8 DORA, 3 UK CTP, 5 NIS2, and 3 Korea Network Act: MSIT, KISA, and KCC/PIPC) plus a Chief Compliance Officer (CCO) synthesizer evaluate drafts against primary statutory text.
  4. 3-Ring Evidence Narrative, Firm Voice & Korea Art. 45-3 Governance (src/narrative/, src/voice_agent/, src/korea/): Drafts, challenges (against 35 principles), and promotes long-form submissions with Evidence Ring (Ring 1/2/3) watermarks, alongside dedicated UK CTP Box 2 Self-Assessment and Korea Article 45-3 Local Security Committee (8 statutory topics + subsidiary entity separation) portals.
Bellwether v3.0 closed-loop architecture connecting the Data Hub Semantic Layer, Multi-Question 4-Route Engagement Workbench, Fail-Closed Temporal Staleness Guardrail, Role-Routed Gemini 4 Argon and Claude 5.5 models, and Universal Library Promotion.
Bellwether v3.0 closed-loop architecture · Open full size

Writing

How it works

Bellwether data flow. Regulations, guidance and supervisor statements for DORA, the UK Critical Third Parties regime and NIS2 are parsed, deduplicated, embedded on the machine and stored by regime.
The regulatory corpus and RFI reuse pipeline · Open full size

Regulatory documents enter the corpus through a duplicate check, are chunked and embedded on-device by a small ONNX model, and are stored in a private vector database tagged by framework. RFI reuse checks answers against that corpus.

An incoming RFI question is embedded locally and matched against the library of approved answers, searching only within its own regime. The top similarity score routes it to exact, partial or no overlap, with no LLM in that step. Exact and partial matches go through the staleness guardrail, which marks each answer blocked or reusable. Claude then drafts: the prior answer for an exact match, a reuse-and-gap map for a partial one, or a fresh draft from the corpus with gaps listed when nothing matches. Nothing is sent automatically. A person has to tick “confirm accurate as of today” before Use or Approve is enabled, and an approved answer goes back into the library with a 12-month review-by date.

Submission scoring runs separately. All 16 personas, each modelled on a different regulator, score a draft in parallel at temperature zero. Each score maps to one of five ordinal bands, and the scores combine as a weighted mean: EU-level regulators count 1.5 times as much as national ones, and a persona that fails is left out. The CCO then writes the synthesis.

The staleness guardrail

The first stage is a deterministic age gate. Each answer gets a volatility class with its own time-to-live: 90 days for org structure and metrics, 365 days for policy and forward commitments. The gate escalates an answer that is over its time-to-live, in an event-driven class, of unknown age, or past its review-by date. Anything else is reusable without the more expensive second stage.

The second stage runs on escalated answers. A judge from a different model family re-grounds the answer against the current corpus for its regime, claim by claim, at temperature zero. A forward commitment whose date has passed counts as stale. If the corpus returns nothing for the regime, or the judge errors or replies empty, the check fails closed.

Only a claim found stale blocks reuse. A claim the judge cannot verify is marked unverified and never blocks on its own. The guardrail is advisory: it explains its verdict and leaves the decision to a person.

What calibration found

I calibrate the guardrail on labelled prior answers, each marked fresh or stale with a reason, in three sets: clean, adversarial and borderline. The latest run, on 2026-08-15 with the current judge, covered 69 answers.

The published post reports an earlier run from 2026-07-18, with a different judge and 63 answers: 97% catch, 3.7% false-fresh, 88.9% precision. The judge and the answer set have both changed since, so the two are not a clean comparison.

Shipped in v3.0 (October 2026)

// Posts about this project