{μ} Maneuver Calculus v0.2.1 — current
Sheet MC-05
Working draft MC-SPEC 0.2.1 — the full specification and ontology are not yet published
Overview/Roadmap & work areas

4Roadmap & work areas

Last updated 11 July 2026 · v0.2.1

This page lists areas of past and ongoing work on Maneuver Calculus. It exists for transparency and provenance, not as a release plan.

Not a commitmentNothing here is a promise to ship, a date, or a feature specification. Areas may change, merge, split, or be dropped without notice, and absence from this list does not mean absence of work. Entries in the provenance ledger cryptographically attest that work in an area existed as of a given date; they disclose nothing about its content.

4.1States

exploring notes, prototypes, open questions; no spec yet active updated within the last 14 days parked no update in 14+ days, but not abandoned published a public artifact exists

4.2Areas

AreaFocusStateFirst anchoredLedgerPublished
A01Core ontology & semanticsactive2026-07-11L0002concept DOI
A02Conformance & verification toolingactive2026-07-11L0003
A03Worked maneuver recordsactive2026-07-11L0001
A04Adversarial review & remediationactive2026-07-11L0004test results
A05Public site, documentation & brandpublished2026-07-11L0005maneuvercalculus.org
A07Knowledge-base ingestion & reconciliationactive2026-07-11L0007
A08Provenance & roadmap toolingactive2026-07-11L0008

4.3How provenance works

Each ledger row commits to a snapshot of files via a published root hash, anchored with OpenTimestamps and mirrored in closed-access Zenodo deposits under the project's concept DOI. When work in an area is published, the corresponding files are revealed and verify against hashes anchored earlier. The public root leaks nothing but a digest and a file count; the per-file manifests stay private. Details: provenance/README.md.

4.4Changelog

Apache-2.0 · © The Maneuver Calculus contributors