Status and Evolution

This page summarizes the current state of the M45 product and documentation.

Documentation status note

The public docs include both:

  • the workflow and data model exposed by the current application
  • the target semantic model M45 is being built toward

Where those differ, this page describes the current implementation first.

Current Status

M45 is in active development.

The current application is centered on a review workflow built around:

  • projects
  • iterations
  • review units
  • intent hypotheses / intent elements
  • exceptions
  • recommendations and recommendation bundles

This workflow is exposed through the live project review routes and API surface, including:

  • /app
  • /intent-review
  • /projects/[id]/review
  • /projects/[id]/review/[iterationId]
  • /regulatory-intelligence
  • app/api/projects/**
  • app/api/regulatory-intelligence/**

The runtime model today is workflow-centric and requirement-centric.

The public conceptual pages also describe a broader target semantic model built around immutable intent snapshots, formal decision records, project intent profiles, and axis packages. That target model remains useful as the semantic direction of the system, but it is not yet the full end-user storage and workflow contract of the current app.

What Is Live Today

Review workflow

The shipped product currently supports an engineer-in-the-loop review flow over imported requirement data:

  • ingest project artifacts, especially ReqIF requirements
  • create iterations
  • cluster requirements into review units
  • generate and review intent hypotheses
  • run alignment checks and surface exceptions
  • generate recommendations and recommendation bundles
  • export workflow data and reports

Human review remains authoritative throughout this flow.

Regulatory intelligence assistant

M45 includes a regulatory intelligence assistant that allows engineers to query regulatory frameworks (such as DO-178C and related guidance) in a conversational interface. The assistant supports follow-up questions, session history, and saved projects. See the regulatory intelligence assistant workflow for details.

Reference docs that are current

The most implementation-aligned public docs today are:

These pages are closely tied to the current code and should be read as the most reliable public references for live structures.

Git-first storage

M45 has a functional git-backed storage layer. The GitStorageAdapter uses isomorphic-git for repository management, stores workspace manifests in YAML, and supports remote synchronization with any git provider. Workflow data — iterations, review units, hypotheses, exceptions, and recommendations — can be persisted as file-native entities with full commit history. See Git-First Architecture for the full description.

The product is bridging between workflow-oriented coordination data (Supabase) and this file-native, git-backed architecture that carries audit history and decision logs more directly.

Version History

Current documentation baseline

Reviewed: March 20, 2026

The docs set is mixed:

  • implementation-bound reference docs are current
  • conceptual and schema docs are useful, but some describe the target model rather than shipped behavior
  • the regulatory intelligence assistant and git-first storage layer are now documented on this page

Semantic schema status

The public Intent Snapshot Schema currently documents Version 0.6 as a draft semantic contract.

That schema should be read as the direction of the system-of-record model, not as a statement that the application already uses intent snapshots as its primary runtime object.

Roadmap

Near-term emphasis

  • keep the current review workflow accurate, inspectable, and engineer-controlled
  • continue tightening requirement ingestion and review-unit analysis
  • improve recommendation generation and workflow exports
  • keep public docs aligned with the real workflow surface

Ongoing architecture work

  • complete the transition from Supabase-first to git-backed, file-native storage as the primary persistence layer
  • preserve rebuildable history, auditability, and portability
  • expand beyond requirement-centric review into a broader engineering context graph

Target model

The longer-term semantic model described throughout these docs includes:

  • immutable intent snapshots
  • formal decision records
  • configurable project intent profiles
  • axis packages as reusable semantic frames

Those concepts remain the intended direction, but readers should not assume they are already the dominant runtime entities in the shipped product.

How To Read The Docs

Use this reading order if you want the most accurate picture of M45 today:

  1. This page for the current-state caveats
  2. Implementation-bound reference pages such as ReqIF Schema and Review Signals
  3. The conceptual pages for the target semantic model

Read the conceptual and schema pages as defining the meaning M45 is trying to preserve, not as a literal description of every active database table, route, or UI state.

Contributing

M45 documentation is continuously evolving. If you have suggestions or find issues, please contact the M45 team.

Changelog

March 2026

  • Added regulatory intelligence assistant to the status page
  • Updated git-first storage from architecture direction to live feature
  • Expanded reference docs list to include all eight current reference pages
  • Updated review date to March 20, 2026
  • Rewrote the status page to distinguish current implementation from target semantic model
  • Added scope notes to conceptual and reference pages that were easy to misread as shipped-product contracts

Earlier

  • Initial documentation release
  • Core conceptual and reference pages added