SACM

Everything the project maintains about OMG SACM 2.3: what the standard requires, what libs/sacm implements, what has been verified, and the working material behind those decisions.

Twenty-seven pages live in this section, besides this index. Before this index existed, four were reachable from the site and the rest could only be found by browsing the repository tree — which meant a normative project policy and a superseded plan were equally hard to find, and equally easy to mistake for each other.

Each page below carries an authority level, because that is the question a reader actually has:

Level	Meaning
Normative	Project policy. Binding on new work. Change it deliberately.
Reference	Describes what exists. Accurate, but not a rule.
Generated	Produced by a tool. Do not edit; regenerate.
Evidence	A record of what was verified, and when.
Historical	A plan or investigation kept for its reasoning. Superseded — do not follow it as current instruction.

Standards conformance

Page	Authority	What it is
SACM 2.3 conformance statement	Normative	The public claim: which compliance points, and how each release binds the claim to an evidence package.
SACM 2.3 conformance matrix	Normative	The canonical source of requirement IDs. Test names embed them. sacm_matrix_check gates it.
SACM 2.3 compliance points	Normative	Which of the standard's five compliance points are claimed, and which is not. Read before quoting any conformance claim.
Matrix completeness audit	Evidence	The 2026-08-08 independent answer to "is a normative obligation missing from the matrix entirely?" Findings tracked in #333–#337.
SACM integration preservation	Evidence	The long-form record behind the integration rows: every measured loss at the library/legacy-projection seam, and every verifier round.
Verification records	Evidence	One record per sacm-conformance-verifier pass, failures included.
SACM 2.3 metamodel inventory	Generated	Classes, attributes and containments derived from the normative OMG model.
Interoperability corpus	Reference	Every dialect the library claims to read, with provenance.
Diagnostics catalog	Reference	Stable diagnostic codes emitted by libs/sacm. Once released, a code's meaning cannot change.

Policy

Binding on new work in and around the SACM library.

Page	Authority	What it settles
Compliance policy	Normative	Full SACM 2.3 compliance is the target; increments must not be presented as full compliance.
Editing policy	Normative	Editing belongs in the library, not bolted on afterwards.
Layout policy	Normative	Layout, coordinates and rendering are not SACM concerns and stay out of the library API.
Test strategy	Normative	Test at the model/edit/XMI boundary first; UI tests verify projection, they do not define compliance.
Decisions and questions	Normative	Settled points, recorded so they are not silently reopened.

GSN and the standards landscape

Page	Authority	What it is
GSN to SACM 2.3 mapping	Normative	Evidence-backed mappings. Never invent one in code.
GSN / SACM metamodel gaps	Reference	Analysis prepared for the SCSC ACWG and the OMG SACM RTF.
SACM 2.3 specification defects	Reference	Defects in the published SACM 2.3 text and model, found by writing validators against the clauses. Input to the OMG submission.
SACM 2.4 Beta 1 impact analysis	Reference	What OMG published in September 2026, how it differs from 2.3, why it cannot be implemented yet, and when to revisit.
SACM 2.4 Beta 1 inconsistencies to report	Reference	Places where the beta's documents contradict each other, for OMG. Preliminary. Limited to what can be checked from the documents alone, with a locator for each fact about the model; no design opinions and nothing GSN-specific.
SACM 2.4 Beta 1 metamodel inventory	Generated	Every classifier in the beta's model, as published. A baseline for comparing later versions; not a conformance requirement.
SACM 2.4 watch	Historical	Tracking written from draft RTF issues before the beta existed. Overtaken by the impact analysis.
Research notes	Reference	Official references and where they came from.

Library design

Page	Authority	What it is
Library architecture	Reference	The shape of libs/sacm and its public boundary.
Requirement record template	Reference	Starting point for a new requirement record.
Slice brief template	Reference	Starting point for a new implementation slice.
Interop case template	Reference	Starting point for a new interoperability case.

Historical

Kept for the reasoning they contain. Superseded — do not follow them as current instruction. Where they conflict with a Normative page above, the Normative page wins.

Page	Why it is kept
Library implementation plan	The staged plan the library was built to. Useful for why the phases split as they did.
Assurance Forge integration plan	How the application was to become a client of the library.
Stage 3 projection baseline	The measured projection parity result at Stage 3.
Agent operating plan	The original agent workflow. Superseded by the agent architecture work in #294.
Agent pack readme	How the SACM agent pack was installed. Same successor as above.
Prompts	The prompts the implementation was driven with.

Related

• Layers and ownership — where the library sits relative to the application, and what may depend on what.
• ADR 0006 — why SACM 2.3 is an independent reusable library.
• ADR 0003 — why SACM XML is the source of truth.