# LOCK v1 — the Magogi engineering standard is locked

> **Status:** LOCKED — corpus **v3.0.0**, federation contract **v2.0** — founder-enacted
> 2026-07-04 (execution delegated to the Court/CTO seat; the enactment record is the merge of
> this file plus the annotated tag `standards-lock-v1`). Court round: `mgf` workspace,
> `court/reviews/2026-07-03-standards-lock/`.
> **What "locked" means:** the surfaces below change ONLY through the amendment classes below.
> The founder's discipline, now mechanical: *maximum scrutiny before the lock; after it, the
> line holds — we do not reopen the basics on a whim.*

## 1. Locked surfaces

- `docs/standards/**` — the 22 rule families (265 MUSTs), the three principles, `rules.json`
  (as generated; regeneration rides every amendment, never freestanding).
- `FEDERATION.md` — the contract (v2.0), incl. the rings, the library-first strategy, the
  conformance levels, and §10's own maintenance discipline.
- Root `SCOPE.md`, `SECURITY.md` (process + distribution/recovery), `PUBLIC_API.{md,json}`
  discipline, `MGF_LIBRARIES.{json,md}` **as data with a locked shape** (membership changes are
  registry events via the generator + REL-13; the generator's self-edge/`?`-version gates are
  part of the lock).
- `templates/**` — policy.toml, gitleaks, woodpecker fragments, the cookiecutter scaffold
  (image-pin currency bumps are CLARIFY-class).
- The gates as *enforcement contract*: `gen_rules_index.py --check` (incl.
  `check_headline_coherence.py`), `gen_mgf_libraries.py --check`, the test suite's rule
  pins, `fleet_ownership_audit.py --check`, `mgf-fed drift-check` shape. Strengthening is
  CLARIFY/EXTEND; weakening or removal is BREAKING.

**Explicitly excluded (working surfaces, not law):** `docs/inprogress/**` (incl. FLEET_AUDIT
trackers), `FEEDBACK.md` + `pending-feedback/` (the queues), `LESSON_LEARNED.md`,
`docs/recipes/**` (operational procedures), `docs/memory/**`, `docs/archive/**`,
`CHANGELOG.md`, and the `mgf.standard` **package version** (0.1.x releases ship the corpus;
REL-13 governs them independently of this lock).

**GATED at lock:** `PRESENTATION_LAYER.md` PR-01..PR-07 (DRAFT pending a second adopter) —
excluded from the locked corpus; promotion to ACTIVE is an EXTEND amendment, ratify-as-built.

## 2. Amendment classes

| Class | What qualifies | Mechanism | Version effect |
|---|---|---|---|
| **CLARIFY** | Wording, typos, links, gate strengthening, template currency; zero semantic change to any MUST | Supervisor/Court stages; lands via normal PR; batch-recorded in CHANGELOG | corpus PATCH |
| **EXTEND** | New rule/family for a new domain; no existing MUST weakened; GATED→ACTIVE promotions; registry membership events | Staged PR + explicit founder enactment (merge is the act); DOC-18 ripple walked in the same change-wave | corpus MINOR |
| **BREAKING** | Changing or removing an existing MUST; weakening a gate; contract-term changes | Founder enacts **plus** mandatory attachments: fleet-impact audit (`fleet_conformance_audit.py` fresh run) + migration note | corpus MAJOR / contract bump — intended frequency: ~never |

## 3. Preconditions verified at the lock commit

`gen_rules_index.py --check` GREEN (265 MUSTs / 22 families / 273 anchored; headline +
version coherence GREEN) · `gen_mgf_libraries.py --check` GREEN + CURRENT (36 libraries, no
self-edges, no unknown versions) · pytest **138 passed** · `fleet_ownership_audit.py --check`
GREEN (post-wave) · `fleet_conformance_audit.py` 39/39, 0 real gaps · `mgf-fed drift-check`
clean for this repo · live CI green on the enacted sweep (PR #189).

## 4. Open-at-lock register (known, bounded)

1. **PAPER-108/113/114** (sooth CI improvements, incl. the `$DEVPI_URL` fragment shape) —
   Court recommends SHIP; disposition is an EXTEND-class template change.
2. **`mgf-fastapi`'s extra gitleaks allowlist entry** — needs the template-vs-subset policy
   decision (mgf-fed PAPER-03 tracks the same); CLARIFY/EXTEND per outcome.
3. **`mgf.standard` 0.1.61 release** to devpi carrying the locked corpus — next REL-13 wave.
4. **README §Versioning "top of this file" wording** — CLARIFY candidate (the corpus version
   lives in CHANGELOG markers + this file, not a header line).
5. The five SCOPE-block non-adopters (`*-web`, `mgf-fedres`, `mgf-test-web`) — owners' opt-in;
   the ownership gate notes, never REDs, on them.

## 5. The shared philosophy clause

The principles trio (`agent-empowerment-charter`, `non-adoption-is-valid`, `audit-outcomes`)
is **intentionally convergent** with `sooth-standard`'s adaptation (their ATTRIBUTION records
the lineage; their LOCK.md carries the mirror of this clause). A semantic change to either
side's trio MUST trigger a cross-family feedback paper to the other. Wording may diverge; the
six licenses and the honesty bar may not — silently.

## 6. Pressure-point register (consciously accepted + relief valves)

- **AG-13 single-supervisor funnel** — kept: it is the consistency engine. Relief: the
  supervisor may delegate a named, scoped wave to an agent cohort (exercised 2026-07-04,
  recorded in the mgf workspace); the delegation is explicit per wave, never standing.
- **REL-13 whole-federation release gate** — kept. Relief: the gate runs per release wave
  from the parent checkout (CI cannot host it — the cohort-release-wave recipe carries the
  mandatory step + the honest note that CI silence is not green).
- **AG-16 private-index corpus extra** — kept while the fleet is private; revisit at the
  public flip (an EXTEND to the contract if the index posture changes).

## 7. Verifying this lock

```sh
python3 scripts/gen_rules_index.py --check && python3 scripts/gen_mgf_libraries.py --check
.venv/bin/python -m pytest -q
git show standards-lock-v1 --no-patch
```
