Standards (reference-only)
These 6 type-standards define the required anatomy each deliverable type follows.
In this monorepo they are reference documents, not enforced gates — the engine’s
skeletons (engine/mbse/skeletons/) stamp the anatomy, and type discipline is the
operator’s call at authoring time (picking a skeleton = picking a type).
| Type | Standard | Skeleton |
|---|---|---|
| profile | PROFILE-STANDARD.md | engine/mbse/skeletons/profile.md |
| report | TEMPLATE-STANDARD.md | engine/mbse/skeletons/report.md |
| retained service | SERVICE-STANDARD.md | engine/mbse/skeletons/service.md |
| system | SYSTEM-STANDARD.md | engine/mbse/skeletons/system.md |
| geospatial | GEO-STANDARD.md | engine/mbse/skeletons/geospatial.md |
| package | PACKAGE-STANDARD.md | engine/mbse/skeletons/package.md |
These standards were adapted from the discipline cell that first proved the type anatomy; its build toolchain, scaffolding pipeline, and project-tracking notes have been removed. What remains is the type anatomy each deliverable follows firm-wide.