{μ} Maneuver Calculus v0.2.1 — current
Sheet MC-04
Working draft MC-SPEC 0.2.1 — the full specification and ontology are not yet published
Overview/Alignment & prior art

3Alignment & prior art

Last updated 11 July 2026 · v0.2.1

Maneuver Calculus is framework-neutral. It does not replace the public threat-informed frameworks; it sits among them and makes their relationships computable. Alignment is by SKOS mappingexactMatch, closeMatch, relatedMatch — never by owl:equivalentClass, never by subclassing into another taxonomy. Nothing in the calculus depends on any one framework's tree surviving its next revision.

3.1Prior art

The calculus stands on public, non-vendor work. Each of the following contributes a piece the calculus adopts by name rather than reinvents:

Summiting the PyramidCenter for Threat-Informed Defense
The source of the robustness scale (L1–L5) and the spanning-versus-discriminating distinction for observables. Adopted directly.
MITRE ATT&CKMITRE
The tactic and technique vocabulary. The calculus sits one altitude below the technique, at the procedure level, and maps up to it.
MITRE D3FENDKaloroumakis & Smith, 2021
The nearest defender-side lineage: countermeasure and digital-artifact vocabulary. The calculus types defenses by a different, coarser cut.
DFIQDigital Forensics Investigative Questions
The investigative-question unit adopted by the investigation layer, bound by dfiqId where a generated question matches a catalogued one.
Malware Behavior CatalogMBC
The primitive / micro-behavior tier — purpose-neutral behaviors (e.g. C0049 read process memory) that variants compose.
Hoare logic · SKOS / OWLfoundations
The precondition → mechanism → postcondition triple shape is Hoare's; the mapping-not-importing discipline is the W3C SKOS/OWL semantic-web stack, used as designed.

3.2The integration matrix

Every correspondence below ships as a SKOS statement in the alignment graph, loaded separately from the core. The relation strength is exact where a term is adopted wholesale, close where the concepts nearly coincide, and related where the two draw a genuinely different cut.

Summiting the Pyramid — the robustness model
Maneuver CalculusFrameworkRelationNote
Robustness L1–L5StP Levels 1–5exactthe evasion-resistance scale, adopted directly
spanning / discriminatingStP D3 observable rolesexactthe grounding-driven role distinction
robustness levelAnalytic Robustness Levelclosesame axis, MC carries it on the observable

Value-add — StP scores a level by hand; the calculus measures robustness empirically (convergent evolution, mutation survival) and consistency-checks the grade against the observable's grounding.

MITRE ATT&CK — the technique vocabulary
Maneuver CalculusFrameworkRelationNote
ObjectivesTactics (TA0001 · TA0006 · TA0010 · TA0040)exactobjectives correspond cleanly to tactics
Defense impairmentDefense Evasion (TA0005)closeMC is the impair-defenses subset
ManeuverTechniquesrelatedmany-to-many, not 1:1 — a technique bundles an objective with an effect; the per-maneuver id is attackTechniqueId
Implementation variantSoftwareclosea variant is finer — one realization path of a core
Actor · CampaignGroups · Campaignscloseattribution layer
MITRE D3FEND — the defender side
Maneuver CalculusFrameworkRelationNote
Defender maneuverDefensive TechniquerelatedMC types a defense by (locus, function); D3FEND by a tactic/technique tree — a different cut
ObservableDigital Artifactrelatedepistemic (telemetry-visible) versus ontic (exists unobserved) — not equivalent
counterscounterscloseMC also pins the (locus, function) cell of the counter
InvestigationModel tactic · analysisrelatedbelief-writing actions, distinct from prevent/detect/react
Invariant coreOffensive Techniquerelatedthe identity-bearing mechanism a defense is keyed against
DFIQ — the investigation layer
Maneuver CalculusFrameworkRelationNote
Investigative questionQuestionexactthe same unit — "what do we need to determine?"
dfiqIdDFIQ idclosethe instance-level bridge to a catalogued question
InvestigationApproachrelatedone-to-many — many approaches answer one question
answersanswersQuestionclosethe resolution relation

Value-add — DFIQ is an authored catalogue; the calculus derives a question mechanically from a discriminating variable, the (role, variable) where surviving reconstruction hypotheses disagree, and binds to a catalogued id where the two coincide.

3.3What the calculus adds

The frameworks above name what a technique is, what a countermeasure is, and what a robustness level is. The calculus supplies the structure that connects them: the procedure altitude below the technique, where a maneuver is objective-rooted and identified by an invariant core; robustness derived-and-checked against grounding rather than scored by hand; observables kept epistemically distinct from the artifacts that produce them; a coverage verdict that is derived from telemetry sourcing and detectability health rather than asserted; and investigative questions generated from where the evidence disagrees. The alignment is the seam — the calculus is what holds across it.

NoteThe alignment graph and the full crosswalks ship with the ontology, which is not yet published. This page states the correspondences the calculus commits to; the machine-readable mappings follow with the specification.
Apache-2.0 · © The Maneuver Calculus contributors