Conventions (patterns verify does not enforce)

Cell bodies

  • [BRACKETED CAPS] placeholders; italic guidance line under each heading; numbered ”## N.” sections; markdown tables for every matrix; “END OF ” terminator. No live tool names in deliverable bodies.
  • Altitude rule: specialize every skeleton section to the deliverable or cut it; never pad. (From the type standards; the load-bearing quality rule.)
  • Mandatory verbatim blocks (grading matrices, ethics caveats, duty-to-warn, handling caveats) come from the cc02 type standards; never paraphrase them.
  • No em dashes in deliverable cells; hyphens or restructure instead.

Edges

  • inputs = upstream cells this one consumes; produces_for = strict inverse; related = explicitly contrasted siblings only, not same-capability neighbors.
  • Seams (provides/requires) are for cross-domain flows only; intra-domain dependency always uses inputs/produces_for.
  • processes and resources stay empty lists (reserved for a future methods and sources layer).

Collections (D-01)

  • Frontmatter-free by design; first line ”# - Collection Map”; numbered ”## NN .” branches 00-99; blockquote lines are XMind node notes; shapes per collections/_SHAPES.md. Authored per cell as it reaches drafted.

Cell lifecycle (status field)

Vocabulary is engine-enforced (engine/mbse/cells.py STATUSES); transition criteria are convention:

  • stub: scaffolded by mbse new; frontmatter valid, body is skeleton only. No one may cite a stub as doctrine.
  • drafted: author asserts content-complete against the type standard and the cold-start operator test (an operator executes from the cell plus its referenced artifacts alone); mbse verify exits 0; em-dash and placeholder discipline hold. Entered by the author.
  • needs-revision: a reviewer found a defect after drafted. Entered only by the reviewer, with defects listed in the dispatch/report or commit message. Exit back to drafted is by rework plus author re-check.
  • approved: reviewer confirmed the drafted bar independently (re-ran verify, swept style, checked traceability and seam closure) AND a named operator performed the cold-start validation test AND the accountable owner signed off (the V1/V2/V3 promotion gate in cc03 METHODOLOGY.md). Entered only by the reviewer; never by the authoring agent in the same change that wrote the content. Content changes to an approved cell reset it to drafted and bump the minor version.

Forward path: stub drafted ( needs-revision drafted)* approved. Deprecation is a registry state, not a status; DIDs never recycle.

Git and delivery

  • Conventional-ish commits: feat/fix/docs(scope): summary. One commit per coherent change; run uv run mbse verify before committing.
  • Engagement builds follow cc03 METHODOLOGY.md (CONTEXT, ADRs, BUILD_LOG, HANDOFF, gated specs).
  • Personnel by initials only; secrets by env-var indirection (CLASSIFICATION.md).

Classification vocabulary

internal (default) | client-confidential | public. Set per cell; rules in cc02-standards/CLASSIFICATION.md.