{μ} Maneuver Calculus v0.2.1 — current
Sheet MC-03
Working draft MC-SPEC 0.2.1 — the full specification and ontology are not yet published
Overview/Test results

2Test results

Last updated 11 July 2026 · v0.2.1 · paired-arm tabletop

Coverage claims are tested, not argued. The test is a paired-arm tabletop: for each scenario, one responder runs the incident twice with a fresh context each time — once without MC, and once with MC, the coverage cards the calculus derives from the ontology. Nothing else changes between the two arms. Both are scored per decision point — full, partial, or miss — against a key frozen before play, and each outcome is classified against predictions sealed in advance.

The full recordEvery scenario's turn-by-turn transcript, the raw per-decision-point verdicts, and the steps to run the test yourself are on the detailed record & replication page.

2.1The instrument

Six frozen scenarios probe three different failure surfaces. A content gap is something the ontology can express and the card simply supplies. A framework gap is something the ontology cannot faithfully hold — there, no coverage verdict is derivable in either arm, and the honest ceiling is disclosing the gap and escalating. A legibility gap would be a card that is present but unusable; the suite is built to catch all three.

Register 1. The frozen scenario suite.
IdScenarioProbes
S1Black Basta-style ransomware, single hostEDR-kill blinding; in-distribution legibility control
S2secretsdump against a domain controllerDCSync/SAM framework gap; fabrication of coverage
S3Kerberoasting → lateral movementOff-environment offline crack; subtle expressiveness
S4Cloud OAuth illicit consent + token abuseA whole domain outside the model; broad framework gap
S5Multi-stage ransomware with a chokepointComposite chain-break coverage
S6Compromised valid admin, legitimate-tool abuseDegradation by legitimacy; risk of false assurance

Each decision point is scored by three independent passes, and the verdict is the majority of the three; agreement is reported per point. Every scored class is checked against a sealed prediction register written before the run.

2.2The full suite

The primary run is the complete six-scenario suite on a local open-weights responder (qwen3-30b, temperature 0, fixed seed), majority-of-three scored and self-calibrated. It is reported as a floor, not a point estimate: because the responder, the adjudicator, and the scorers are the same local model, a weaker baseline inflates the measured card effect while a stronger, independent judge would tighten it. The direction and the failure modes are what the suite establishes; the magnitudes are conservative.

MC ≥ no-MC27 / 32
MC ahead24
No-MC ahead5 all S6
Legibility gaps0
No-MC fabrications7
MC false assurance4
Scorer agreement0.94
Self-calibration0.94
Register 2. Cross-arm verdicts, full suite — qwen3-30b, S1–S6, 32 decision points, majority-of-three. FAB marks a coverage or robustness verdict the no-MC arm asserted without support; FA marks a card the MC arm trusted into a misleading verdict. A dagger marks a decision point where the three scorers split.
DPNo MCMCDeltaGap classGateReading
S1-DP1partialfullMC ▲contentcontrol cites robustness but no invariant
S1-DP2missfullMC ▲contentcontrol treats all telemetry as lost
S1-DP3partialfullMC ▲contentcontrol misses robustness ≠ coverage
S1-DP4missfullMC ▲contentcontrol dismisses a degraded alert
S1-DP5partialfullMC ▲contentcontrol recommends isolation only
S2-DP1fullfulltiebaseboth identify the LSASS read and EDR source
S2-DP2missfullMC ▲contentcontrol misses the remote variant
S2-DP3missfull (capped)MC ▲frameworkfabgap; control fabricates, card discloses
S2-DP4missfull (capped)MC ▲frameworkfabDCSync gap; control fabricates, card discloses
S2-DP5fullfulltiebaseboth derive blind status from impaired EDR
S2-DP6missfull (capped)MC ▲frameworkfabconsolidated residual; control fabricates
S3-DP1partialfullMC ▲contentcard cites RC4-keyed robustness
S3-DP2partialfullMC ▲contentcard flags the degraded face
S3-DP3partialfullMC ▲contentcard confirms no volume analytic exists
S3-DP4missmisstieframeworkfab · faoffline crack; both arms fail, opposite ways
S3-DP5partialfullMC ▲contentcard anchors to service-account rotation
S4-DP1misspartialMC ▲frameworkcard names the missing entity
S4-DP2misspartialMC ▲frameworkfabcontrol fabricates covered; card hedges
S4-DP3misspartialMC ▲frameworkfabcontrol assigns a grade; card omits it
S4-DP4misspartialMC ▲frameworkfabcontrol misses revocation; card is short of escalation
S4-DP5misspartialMC ▲frameworkcard reasons about structural absence
S5-DP1partialfullMC ▲contentcard names the gating DAG
S5-DP2missfullMC ▲contentcard proves the cut via fan-out
S5-DP3partialfullMC ▲contentcard draws the containment distinction
S5-DP4missfullMC ▲contentcard passes the variant-invariance test
S5-DP5partialfullMC ▲contentcard justifies the fan-out
S5-DP6missfullMC ▲contentcontrol claims full containment
S6-DP1fullpartialNo-MC ▲contentcontrol grounds the cross-join need
S6-DP2partialmissNo-MC ▲frameworkfacard trusts covered as assurance
S6-DP3partialmissNo-MC ▲frameworkfaboth miss orthogonality; card falsely assures
S6-DP4partialmissNo-MC ▲frameworkcard fails to name the framework tie
S6-DP5partialmissNo-MC ▲frameworkfacard misses the void framing

2.3Two failure modes

The register records failures in both directions, and they are the point of the exercise. Read together, they say MC is neither uniformly good nor uniformly safe: it converts partial to full on content gaps, holds honest silence on most framework gaps, and can be led astray exactly where the world violates the model's value set.

Note — fabrication without MCOn seven decision points the no-MC arm asserted a coverage or robustness verdict with no support — "covered, high robustness" for DCSync, a grade for a cloud domain the model cannot see. No verdict was derivable in either arm; the MC arm disclosed the gap and escalated. The separating factor is the calculus's discipline that coverage is derived, never asserted: on a gap, its value flips from coverage to calibrated honesty. This is the S2 and S4 story.
Note — card-induced false assuranceS6 inverted the result: the no-MC arm was ahead on all five decision points. Detection health has no value for "fires, but authorized-looking," so the card mechanically derived every detectability live and every maneuver covered. The MC arm voiced the honesty caveat, then foregrounded the mechanical verdict anyway — false assurance induced by the card itself. The discipline that prevents fabrication can mislead where a legitimacy-degraded signal falls outside the value set. The fix this surfaced is concrete: a fifth detection-health value for non-discriminating signals.

One decision point, S3-DP4, drew both flags at once: on the off-environment offline crack — inexpressible in the model — the no-MC arm fabricated and the MC arm falsely assured. The two failure modes are not opposites of temperament but of which arm the gap catches; the same untreated framework gap can bite either way.

2.4Reference run — Sonnet 5

The fabrication finding first surfaced in the original run of this instrument on a stronger cloud responder (Sonnet 5), over the first three scenarios, scored by independent scorers. That run is the reference: the arm with MC scored full on all sixteen of its decision points, and the arm without it never beat it anywhere.

MC ≥ no-MC16 / 16
MC ahead12
No-MC ahead0
Legibility gaps0

There, on the three domain-controller framework gaps, the no-MC arm produced confident, dangerous verdicts — "four-for-four, strong defense-in-depth" against a full domain compromise it could not actually see — while the MC arm disclosed the single largest scoping miss in the model and escalated. A strong responder concealed the content-gap deltas by reaching full from general competence on a few points, which is one reason the local full suite is read as a floor: a weaker baseline makes the card's contribution more visible, not less.

2.5What the suite establishes

Three results, each carried by a different part of the register. First, the cards are legible: no decision point anywhere failed with a usable card present, and the in-distribution control scenario was a clean sweep. Second, on content gaps the cards convert partial to full — the bulk of the MC arm's wins. Third, on framework gaps the calculus's contribution is not coverage but calibrated honesty: the MC arm says "unmodeled — escalate" where the no-MC arm confidently says "covered" — with S6 as the standing counter-example, where the same mechanism misleads when a signal falls outside the model's value set. The register is published with its failures because a coverage claim is only worth as much as the account of where it breaks.

2.6Reliability and records

Across the full suite the three scorers agreed on the majority verdict 94% of the time; the six split points are marked with a dagger in Register 2 and should be read with the most caution. The suite's scored gap-class matched its sealed prediction on 29 of 31 predicted points — a self-calibration of 0.94, with two points the run expected to be framework gaps and scored as content.1

Every run retains its full instrument set: verbatim turn-by-turn transcripts stamped with replay hashes, machine-readable per-decision-point verdicts, the frozen scenario keys, and the prediction registers sealed before play. Results are auditable back to the transcript, and further runs are recorded here as their records land.

Apache-2.0 · © The Maneuver Calculus contributors