M45

Updates

Short shipping notes from M45.

May 27, 2026

Project-first artifact ingestion

  • •Upload a PDF into a project; M45 prepares it for workflows automatically
  • •Source files, extracted text, figures, progress, and metadata now stay together on the artifact
  • •Longer specs and regulatory PDFs use a more resilient page-by-page extraction path
May 27, 2026

Regulatory Intelligence rebuilt for faster work

  • •A redesigned answer experience makes regulatory research easier to read, refine, and reuse
  • •Teams can work with responses in a more flexible shape instead of forcing every question into the same format
  • •Saved research still stays attached to the project for continuity and traceability
May 25, 2026

Safer artifact management

  • •PDFs are versioned, so teams can update source documents without losing prior extraction history
  • •Version history is collapsible, display names can be renamed, and large uploads show clearer progress
  • •Provenance metadata is easier to inspect when teams need to know where an artifact came from
May 20, 2026

More engineering artifacts in one project record

  • •One upload flow now handles ReqIF, PDF, Markdown, and TTL files
  • •TTL ontology files can be reviewed alongside requirements, PDFs, Markdown notes, Slack context, and saved regulatory answers
  • •Duplicate uploads now warn users without blocking legitimate reuse of the same artifact in more than one place
May 18, 2026

Folders for artifacts and linked systems

  • •Projects now have folders for organizing artifacts by source, workflow, supplier, subsystem, or review context
  • •System folders keep Slack channels and saved Regulatory Intelligence answers findable without mixing them into ordinary uploads
  • •Folder navigation now gives loading feedback for slower project workspaces, so users know the action is still moving
May 11, 2026

Requirements Architecture Review

  • •Find structural gaps: requirements with no architecture behind them, architecture with no requirements supporting it
  • •Hazard analysis linked to the affected requirements
  • •Now in the main app
May 8, 2026

PDF to Markdown for project ingestion

  • •Aerospace specs and regulatory documents arrive as long PDFs; M45 now reads them
  • •Initial chunked processing made larger documents practical
  • •This work has since moved into project artifact upload
Apr 20, 2026

Regulatory Intelligence refinements

  • •Regulatory answers are organized by authority, with citations and escalation cues
  • •Saved answers stay attached to the project, so regulatory research becomes part of the engineering record
  • •Workflow reference →
Apr 17, 2026

Slack as project context

  • •Selected Slack channels can be retained in a project, so decisions made in chat do not disappear from the engineering record
  • •Engineers can browse retained channel history alongside uploaded artifacts and workflow outputs
Apr 16, 2026

Project sharing with roles

  • •Projects now support owner, editor, and viewer roles
  • •Teams can share a workspace without giving every collaborator the same level of control
Apr 16, 2026

ReqIF upload hardening

  • •M45 is more tolerant of real-world ReqIF files that are malformed, incomplete, or exported differently by different tools
  • •Interrupted uploads are easier to recover from, reducing the chance that teams have to restart ingestion work
  • •ReqIF schema reference →
Mar 20, 2026

Regulatory Intelligence Assistant

Mar 3, 2026

More predictable project access

  • •Project and review pages now follow the same authenticated access model
  • •Shared workspaces behave more predictably as teams move between project views, review workflows, and APIs
  • •AI conversations can now be scoped to a project, so future assistance can stay tied to the relevant workspace
Feb 18, 2026

Faster review operations

  • •Recommendations can now be scanned across a full review iteration instead of reviewed one unit at a time
  • •Issue and recommendation tables are sortable and filterable, making large reviews easier to triage
  • •Iteration closeout and export flows were tightened so teams can move from review to reporting faster
Feb 12, 2026

Recommendations tied back to requirements

  • •Recommendations can now feed back into stored requirement and artifact records instead of disappearing after a review pass
  • •Review units are grouped around selected intent axes, so analysis follows the dimensions the team actually wants to inspect
  • •Reviews infer only the selected axes, reducing irrelevant analysis and noise
Feb 6, 2026

Per-requirement recommendations and export

Feb 4, 2026

First intent review proof of concept