VámossyResearch

Governance principles

The one idea underneath all of it

Modern LLMs are fluent, confident, and agreeable — a combination that feels like help and behaves like risk in high-stakes work. Every piece here engineers against one facet of that:

  • the Goodhart auditor attacks names that claim more than they check;
  • the maturity classifier attacks confidence that outruns evidence;
  • the containment guard attacks actions that outrun human authority;
  • the patterns keep authority traceable and human-held as systems grow.

A recurring design choice ties them together: the governance components are themselves deterministic and self-testing, because a governance tool that can't demonstrate its own correctness is worse than none. Where a tool has a blind spot, that blind spot is in its test suite, not hidden.

The reachability of the ground truth

Every tool here rests on one question: can you get an independent measure of the truth to check the proxy against? Read across domains, that question has a spectrum of answers, and the honest response scales with it.

At one end sits computational geometry, where the truth is exactly computable. The "edge cases" there are literal — degenerate configurations on the boundary of general position (three collinear points, a query point exactly on an edge), where a floating-point predicate (the proxy) can return the wrong sign for the true, exact answer. Because the truth is reachable, the fix is decisive: compute it exactly (Shewchuk's robust predicates; Yap's Exact Geometric Computation; Edelsbrunner–Mücke's Simulation of Simplicity). Here decoupling is not merely detected but eliminated — the proxy is corrected against an exact ground truth. This is ground_truth_auditor's principle in the domain where it fully succeeds.

The middle is where this toolkit lives: metrics, evaluations, digital twins, mappings, safety-case evidence. The truth is partially and independently observable — enough to catch decoupling (decoupling_monitor), audit the independence of the check itself (ground_truth_auditor), and withhold honestly (UNVERIFIED) where no independent measure exists.

At the far end sits consciousness, where no third-person ground truth exists even in principle. The honest verdict is permanently UNVERIFIABLE (see qualia_report_governor and the Recorded, Not Verified paper) — an edge case of the tool, not the world.

Same structure throughout; only one axis moves — the reachability of the truth — and the honest response moves with it: solve → detect → withhold. The geometry pole matters most for reading the rest: it is the case where an independent ground truth actually closes the gap, which is exactly why its absence elsewhere is meaningful rather than a mere shrug.

Honest positioning (read this before publishing or presenting)

  • This is applied engineering and safety patterns, not new science. It aligns with — and is best presented as a practitioner's synthesis of — human-in-the-loop design, non-agentic tool use, capability control, Goodhart's law, uncertainty quantification, and provenance/audit.
  • Every component is narrow by design and states its limits explicitly. The tools are heuristics and gates, not proofs.
  • Keep this work separate from any speculative or metaphysical material. These pieces stand because they are modest, testable, and honest; adjacency to grand unfalsifiable claims would undercut exactly the credibility that makes them worth publishing.

Applicability and exclusions

This toolkit is not safety-critical software and must not sit on the critical path of any life- or mission-critical control function. It carries none of the assurance evidence such roles require: it is not developed or verified to DO-178C (up to Design Assurance Level A) or DO-254 for airborne systems, to IEC 61508 Safety Integrity Levels (with their quantified dangerous-failure targets — SIL 4 ≈ 10⁻⁴–10⁻⁵ probability of failure on demand), to IEC 61513 / IEC 60880 / IEEE 7-4.3.2 for nuclear Class 1E instrumentation and control, or to MIL-STD-882 system-safety practice; it provides no formal proof, no hardware fault tolerance, no redundancy or diversity, no real-time determinism, and no independent V&V, and its containment gate presumes reversible, bounded actions — so it deliberately (and correctly) refuses the irreversible actuation those domains turn on, such as a reactor-scram thermal transient, a released store, or a launched vehicle. Its legitimate role in nuclear, aerospace, and defense contexts is confined to the non-safety-critical AI and analytical layer — governing ML/LLM components, decision support, evidence-maturity ordering, metric-gaming audits, and non-self-approval of analyses — always advisory, off the critical path, with certified systems and human authorities retaining control. Where its ethos aligns with meaningful-human-control principles (e.g. DoD Directive 3000.09), that is alignment in intent, not certification of fitness: it must not be treated as a control element in flight-critical, reactor-protection, or nuclear command-and-control / weapons-release functions.