Common questions

MC supplies a model of security behavior and defensive reasoning. A semantic world-state system connects that model to sources, claims and retained revisions. A semantic compiler is a component that checks structured input and computes consequences under selected contracts; acceptance of a world revision is separate. The 5 October development snapshot describes a bounded implementation with known failures. This site supplies a prepared walkthrough and inspectable records.

Follow the conceptual flow or inspect implementation boundaries.

MC is in development. Formal specifications, ontologies, implementations and cases have separate identities. The 5 October development snapshot identifies MC-SPEC 0.4.20 and ontology mc-core 0.4.20.2; the September case uses different, provisional bindings. There is no single version that proves all these parts compatible.

The next public formal release will be later than MC-SPEC 0.4.20. A future public version is not assigned here. See the source versions and qualifications.

You can study the case, model procedures by hand, compare interpretations and inspect the draft artifacts and development source summaries. The Build page identifies what is included and its limitations. General planning, operational action execution and whole-system conformance are not established.

MC describes procedures and defensive reasoning alongside external catalogs. The catalog identifiers retain their publisher-defined meaning. A correspondence is not equivalence between entire ontologies or catalogs.

The Alignment page preserves scope and unresolved relations. In particular, the implementation-variant to Software correspondence was removed pending discussion; no replacement connection is accepted. Version-specific comparison with the current defensive-measurement framework release also remains to be checked.

No general scientific-validation claim is made. The earlier Results pages were withdrawn for flawed methodology. The six selected evaluation templates have no completed runs in their source snapshot. Retained implementation probes include failures and added resource costs; they do not establish general practical advantage. Research separates hypotheses, actual evidence and proposed tests.

It is a prepared presentation of archived records. The archive is dated 5 September 2026; its registry distinguishes full-text retrieval labels, excerpts and unavailable items. All requirements are inferred, and no perturbation experiments were run. It explains the model's reasoning and limitations; it is not live threat intelligence, current patch advice or measured control efficacy. Inspect the case and its evidence.

A schema can check structure. It cannot by itself establish source truth, interpretation faithfulness, semantic conformance, world admission or a defensive result. Those claims need their own contracts and evidence. Archived ontology bindings also remain provisional because their specification pins differ.

For this draft, cite the page title, Maneuver Calculus, its snapshot date and the exact artifact version inspected. Distinguish a site's presentation snapshot from the archived case's export version and from a formal specification version. The existing project concept DOI does not identify every unpublished artifact; do not use it to imply such a deposit. A new public formal release identifier is not assigned on this site.

Choose evidence, analysis, theory or tooling, and prepare the affected claim, versions, proposed change and reviewable support. The planned project email alias has not been announced; no public submission channel is available in this draft. Formal meaning changes require an explicit scoped decision.

The current website repository includes Apache-2.0. Refer to the license attached to the material you use; third-party sources and unpublished or future artifacts are not automatically covered. The project principles welcome commercial products and services on shared open foundations. Durable rights and governance still need concrete instruments.

Jacob Schorr is the principal author and current steward. The project is currently author-led, with intended progression toward defined maintainer authority and durable open governance. No later institutional arrangement is asserted to exist. See current responsibility and the maturation path.