Overview
This documentation defines the semantic foundations of M45: the concepts and contracts that keep intent, requirements, and decisions connected over time.
Scope note
Most pages in this section describe the semantic model M45 is being built toward. The current application already exposes an engineer review workflow around projects, iterations, review units, hypotheses, exceptions, and recommendations, but it does not yet use the full public snapshot-and-decision-record model as its primary runtime contract.
For the current product state and how to interpret these docs, start with Status and Evolution.
Engineering work produces many artifacts—requirements, designs, analyses, test descriptions, emails, meeting notes. Each artifact expresses part of the system’s meaning. No single artifact is complete or authoritative. Together, they drift, contradict, or lose context as projects evolve.
M45 addresses this by making system intent explicit.
System intent is a structured, inspectable representation of the behaviors, structures, and conditions that artifacts collectively imply. M45 infers candidate intent from artifacts, allows engineers to review and correct it, and records decisions over time. The result is a versioned record of meaning that stays connected to its sources.
What you’ll find here
- What M45 means by system intent
- How intent is inferred and aligned across artifacts
- How human decisions establish authority and ownership
- How intent and decisions evolve over time
What you won’t find here
- Product features or user interfaces
- Inference algorithms or AI models
- Certification or compliance claims
The goal is clarity: definitions you can audit, explain, and rely on as engineering infrastructure.