Reference · development snapshot

Implementation status and open work

The development snapshot supports a bounded path from source custody through compilation and accepted revisions to named views. Capability boundaries, failures and historical provenance remain visible.

Current-state snapshot 5 October 2026 · historical areas: 24 August 2026

This page separates the current source and implementation snapshot from the historical work-area register. It exists for transparency and provenance, not as a release plan.

Development directionAreas and priorities may change. The historical ledger retains recorded hashes and dates, but its timestamp proof files are not included in this preview and cannot be verified here.

Current state

What can be inspected today. The site provides a worked behavioral example, draft semantic explanations, the reference architecture and sanitized source snapshots. All remain in development. The next public formal release will be later than MC-SPEC 0.4.20.

What the local implementation does. A bounded path links source custody and candidate interpretation to semantic checks, accepted world revisions and task-qualified views. It retains attributable attempts and computations as well as accepted changes. World admission has its own checks; producing a decision record does not establish that an external action ran.

What remains unestablished. General belief closure, planning and governed action execution are not established. Retained reviews identify temporal/context failures in RDF consumers, native joins without identity and missing measured-evidence carriage. Perspective-specific views do not establish confidentiality controls. These limitations prevent a full conformance claim. A stronger coherent-witness policy for displayed support remains an open semantic choice.

Evaluation. The earlier Results pages have been withdrawn because their methodology was flawed. They are not used to support the current design. A separate benchmark page will be added later. The six-stage evaluation ladder currently consists of selected blank test templates, with no runs recorded in this source snapshot. Retained implementation probes contain failures and resource costs and do not establish a general benefit.

Development snapshot identifiers

These identify the inspected sources, not a unified product release: formal development reference MC-SPEC 0.4.20; ontology mc-core 0.4.20.2; native core 1.0.1; admission contract 0.2.0; selected maintained-world integration v025. The prepared v026 integration has not been promoted. See baseline provenance and limits.

Historical register belowThe area register retains July 2026 ledger entries. Current activity has not been independently assessed, so no recency claim is made. Hashes and counts alone establish neither correctness nor capability; proof availability is a separate question.

States

recorded historical entry; current activity not assessedpublished an existing public artifact is linked

Areas

Area	Focus	State	First recorded	Ledger	Published
A01	Core ontology & semantics	recorded	2026-07-11	L0002	concept DOI
A02	Conformance & verification tooling	recorded	2026-07-11	L0003
A03	Worked maneuver records	recorded	2026-07-11	L0001
A04	Adversarial review & remediation	recorded	2026-07-11	L0004	Withdrawn evaluation
A05	Public site, documentation & brand	published	2026-07-11	L0005	maneuvercalculus.org
A06	Landscape & positioning analysis	recorded	2026-07-11	L0006
A07	Knowledge-base ingestion & reconciliation	recorded	2026-07-11	L0007
A08	Provenance & roadmap tooling	recorded	2026-07-11	L0008

How provenance works

The ledger records a hash, declared snapshot date and area for each retained entry. The intended verification procedure uses OpenTimestamps proofs, but all eight referenced proof files are absent from this preview. Every row therefore marks proof availability as pending. The dates and anchoring claims have not been independently verified here. A root hash alone proves neither authorship, conformance nor the substance of the work. See the ledger’s scope and verification limits.

Changelog

2026-10-05, v4 review iteration: Reading path aligned; remaining claim, terminology and metadata inconsistencies corrected. The disputed ATT&CK Software correspondence was removed pending further discussion. The planned public contact channel is project email; its address is pending.
2026-10-05, v3 review iteration: Results withdrawn; capability and version status clarified; A06 restored; historical activity relabeled as unassessed; missing proofs explicitly marked.
2026-10-05, first preview: Architecture and current-state orientation added.
2026-07-11: Original work-area ledger recorded L0001–L0008. Its proof files are unavailable in this checkout.