Skip to content
Apothem
Governance

Pre-Emission Gate Registry — Mandatory Fifteen-Bar Check

Mandatory fifteen-bar conformity check run before emission of meaningful scope, with failure-action mappings and release-proof schema.

Canonical registry of the fifteen-bar pre-emission gate. This document carries the full fifteen-bar gate table and the release-proof schema YAML block; the substantive table and schema live here, operationalized by src/apothem/rules/pre-emission-gate.md.

Before any artifact emission of meaningful scope (per the trivial-vs-non-trivial threshold at site/content/docs/governance/outward-conformity-registry.mdx §1), run the fifteen-bar pre-emission gate. Mechanise via PreToolUse hooks where possible (the mechanical greps at src/apothem/conformity/*-grep.py orchestrated by src/apothem/conformity/gate.py); reason through where mechanisation is impossible. Failure of any single bar blocks emission; revise until every bar passes; emit with the gate release-proof recorded.

#BarCheck kindFailure → action
1M1 host agnosticismreasonedrevise to match host conventions
2M2 editorial disclosurereasonedadd disclosure ledger
3M3 ten dimensionsmixed (mechanical + reasoned)revise on failing dimension
4M4 self-applicationmechanical (release-proof present)record release-proof
5M5 authoritymechanical (<USER-CONFIRM:…> placeholder grep)re-route to inquiry surface
6M6 expertisereasoned (surfaced-gaps section present)surface gaps; cite
7M7 option annotationmechanical (option set carries recommended marker)annotate
8M8 definitivenessmechanical (hedging vocabulary grep)promote hedging to conditionals
9M9 visual leveragereasoned (diagram exists where structural)author / refresh diagram
10M10 bidirectional bindingmechanical (binding-reciprocity grep)close half-edges
11M11 agile sprintsreasoned (sprint apparatus instantiated)restructure as sprints
12M12 phase reporting & layoutmechanical (orphan-output grep) + reasonedauthor rollup; relocate
13M13 code craftmechanical (lint / format / type-check; bare-except, magic-number, commented-out grep)revise
14M14 systemicityreasoned (declares upstream / downstream / peers / enforcers)declare; index
15M15 production-readymechanical (production-ready-pr grep) + reasonedadd tests / docs / CHANGELOG

1. Release-Proof Schema

Every gate run records the result in the artifact's working trace (a hidden comment, a metadata block, a separate emission-log file — whichever the host's conventions allow):

conformity-attestation:
  artifact: <path-or-identifier>
  ecosystem-version: <git-commit-sha-or-equivalent ratifying the rule set in force>
  bars:
    M1-host-agnosticism:        pass | n/a (with reason)
    M2-editorial-disclosure:    pass | n/a
    M3-ten-dimensions:          pass | n/a
    M4-self-application:        pass
    M5-authority:               pass
    M6-expertise:               pass | n/a
    M7-option-annotation:       pass | n/a (no option set)
    M8-definitiveness:          pass
    M9-visual-leverage:         pass | n/a (subject not structural)
    M10-bidirectional-binding:  pass
    M11-agile-sprints:          pass | n/a (trivial work)
    M12-phase-layout:           pass | n/a
    M13-code-craft:             pass | n/a (not code)
    M14-systemicity:            pass
    M15-production-ready:       pass | n/a (no host-public-surface change)
  surfaced-gaps: []
  unresolved-inquiries: []
  amendments-disclosed: []
  date: <ISO-8601>

n/a markings are explicit and reasoned — never silent skips. The ecosystem-version field anchors the release proof to a reproducible state of the user-scope ecosystem (the active Apothem source-tree git commit when the gate ran — e.g. the ~/.claude/ checkout for the Claude Code adapter), so future audits can replay the gate against the same rule bodies.

On this page