docs(1.0): ratify A2/A3/A4 — ADR-0035 Accepted

A2 FR-024 declared-API: DEFER (reserved-but-unregistered post-1.0; already absent from
expected-registry.json; additive later) — removes the last breaking-round candidate,
unblocking the quiet period. A3 deprecated codegen-ts/generators export: REMOVE at the
1.0/8.0 cut (G2), not before (removing an export is breaking; the major absorbs it).
A4 own-your-codegen: RATIFIED per-port-idiomatic + documented in the new
docs/features/own-your-codegen.md. ADR-0035 now Accepted (all [RATIFY] items resolved).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GF9xLEQZaPus5Y6opk398n

Author: claude

docs/1.0-readiness.md

@@ -22,13 +22,17 @@ Status legend: ✅ done · 🔶 in progress · ⬜ not started · ❓ **[RATIFY]
   backwards; `1.0.0 < 7.7.1` in every resolver), tied by a shared **`Metamodel 1.0`
   spec version** (OpenTelemetry / protobuf-editions model; the Java jump is the
   Angular 2→4 precedent). *ADR-0035 §2 (rewritten).* Unblocks G1; adds C4.
-- ❓ **A2. FR-024 declared-API: land vs defer.** Land `api.*`/`operation.*`/`binding.*`
-  before 1.0, or defer post-1.0 with the vocabulary *reserved but unregistered* (so
-  adding it later is additive). *Tracked in #10.*
-- ❓ **A3. Deprecated `@metaobjectsdev/codegen-ts/generators` export.** Remove at 1.0
-  (1.0 is the natural major) vs retain one more line.
-- ❓ **A4. Cross-port "own your codegen."** Ratify per-port-idiomatic (TS `meta init`;
-  JVM/Python/C# via build config) **and document it**, vs close a parity gap first.
+- ✅ **A2. FR-024 declared-API — RATIFIED: DEFER.** `api.*`/`operation.*`/`binding.*`
+  stay reserved-but-unregistered post-1.0 (already absent from `expected-registry.json`;
+  additive to add later). Removes the last candidate for a breaking round → unblocks the
+  quiet period (G3). *Tracked in #10.*
+- ✅ **A3. Deprecated `codegen-ts/generators` export — RATIFIED: REMOVE at the cut.**
+  Removed as part of the 1.0/8.0 major bump (**G2**), not before — removing an export is
+  breaking, so the major absorbs it. Consumers use the `meta init`-scaffolded owned
+  copies.
+- ✅ **A4. Cross-port "own your codegen" — RATIFIED: idiomatic + documented.** The
+  per-port split (TS `meta init`; JVM/Python/C# via build config) is intentional, not a
+  parity gap. → **D4** written: `docs/features/own-your-codegen.md`.
 
 ---
 
@@ -39,8 +43,10 @@ Status legend: ✅ done · 🔶 in progress · ⬜ not started · ❓ **[RATIFY]
   CLI surface, scaffold-and-own contract — and what it does *not* (generator
   internals, runtime helper internals, reserved/experimental vocab).
 - ⬜ **B2. Write the `0.x → 1.0` migration guide.** Consolidate the breaking changes
-  adopters must absorb (verify strict-default, jsonb open-bag parsed-value, the
-  deprecated-export removal if A3=remove, any FR-024 vocab if A2=land).
+  adopters must absorb: verify strict-default, jsonb open-bag parsed-value, the
+  metamodel-1.0 vocabulary program, `index.*`/`@unique` removal (ADR-0040), and the
+  deprecated-export removal (A3=remove). FR-024 is deferred (A2), so no declared-API
+  vocab to migrate.
 
 ## C. Metamodel freeze (the durable spine)
 
@@ -78,9 +84,11 @@ Status legend: ✅ done · 🔶 in progress · ⬜ not started · ❓ **[RATIFY]
   `--lax`, `--template-spec`, target/output flags) per port, locked against the CLI
   architecture (ADR-0015) and surfaced in one matrix.
 - 🔶 **D3. Scaffold-and-own contract stable (TS)** — what `meta init` scaffolds + the
-  `Generator` interface owned templates implement; resolve A3.
-- ⬜ **D4. "Own your codegen" documented for every port** (resolve A4): the TS
-  `meta init` flow and the JVM/Python/C# build-config equivalents, side by side.
+  `Generator` interface owned templates implement. A3 resolved: the deprecated
+  `codegen-ts/generators` re-export is removed at the cut (G2).
+- ✅ **D4. "Own your codegen" documented for every port** (A4 ratified) —
+  `docs/features/own-your-codegen.md`: the TS `meta init` flow + the JVM/Python/C#
+  build-config equivalents, side by side.
 
 ## E. Cross-port conformance + wire contract
 

docs/features/own-your-codegen.md

@@ -0,0 +1,53 @@
+# Own your codegen
+
+MetaObjects treats generated code as a **disposable artifact** and the metamodel as
+the **durable spine**. You own the generated code in your repo — it runs without any
+MetaObjects runtime dependency, and if `@metaobjectsdev/*` (or the Maven/PyPI/NuGet
+packages) disappeared, you keep working code.
+
+"Own your codegen" means two related things, and how far each goes is **idiomatic per
+port** — this is intentional (ADR-0035 §3, ratified), not a parity gap:
+
+1. **You own the invocation** — codegen runs through your own build, on your terms,
+   in every port.
+2. **You own the templates** — in TypeScript, `meta init` scaffolds the reference
+   generators *into your repo* so you can edit them (ADR-0034 scaffold-and-own). The
+   JVM/Python/C# ports own codegen through **build configuration** rather than copied
+   template files; template customization there is via the declarative
+   template-codegen surface (`--template-spec` / Mustache) and the generator-selection
+   SPI.
+
+Either way, hand-edits inside a generated file survive regeneration: the TS toolchain
+three-way-merges against a committed merge base, so your edits are preserved.
+
+## Per port
+
+| Port | Invocation | Template ownership model |
+|---|---|---|
+| **TypeScript** | `meta init` → `meta gen` (Bun/Node CLI) | **Scaffold-and-own** — `meta init` copies `entityFile`/`queriesFile`/`routesFile`/`barrel` into `codegen/generators/*.ts`; `metaobjects.config.ts` imports those local copies. Edit them freely. |
+| **C#** | `dotnet meta gen` / `dotnet meta verify` (.NET tool) | Build-config: the generator set (EF Core entities + `AppDbContext` + CRUD routes) is selected via config; customize via template-spec. |
+| **Java / Kotlin** | `mvn metaobjects:generate` / `mvn metaobjects:verify` (`metaobjects-maven-plugin`) | Build-config: generators selected in `pom.xml`, by **stable name** (`entity`/`routes`/…) through the `GeneratorRegistryProvider` ServiceLoader SPI. Kotlin generators run through the same goal. |
+| **Python** | `metaobjects gen` / `metaobjects verify` (console-script) | Build-config: the generator set (Pydantic + FastAPI + SQLAlchemy) selected via config; customize via template-spec. |
+
+*(Full command/flag matrix and rationale: [`docs/features/cli.md`](cli.md), locked per
+ADR-0015. Schema migrations are TypeScript-owned across all ports.)*
+
+## What's shared vs. per-port
+
+- **Shared (the durable contract):** the metamodel vocabulary, the canonical/YAML
+  format, the wire/normalization contract, and the *shape* of the generated artifacts
+  (verified byte-for-byte by the codegen + api-contract conformance corpora across all
+  five ports). A given entity produces the same logical model, routes, and validation
+  everywhere.
+- **Per-port (idiomatic):** *how* you invoke codegen (npm CLI vs `dotnet` tool vs
+  Maven goal vs console-script) and *how far* template ownership goes (TS copies
+  editable templates into your repo; the other ports own codegen via build config +
+  the declarative template surface). This split follows each ecosystem's norms
+  rather than forcing a single mechanism.
+
+## Deprecated (removed at 1.0)
+
+Importing the built-in generators from `@metaobjectsdev/codegen-ts/generators`
+(`entityFile`, `queriesFile`, `routesFile`, `barrel`) is **deprecated** (ADR-0034) and
+**removed at the 1.0/8.0 release**. Use the owned copies `meta init` scaffolds into
+`codegen/generators/*` and import those from your `metaobjects.config.ts`.

spec/decisions/ADR-0035-one-zero-stability-commitment-and-version-unification.md

@@ -2,15 +2,19 @@
 
 ## Status
 
-**Proposed** (2026-06-29; §2 version-line strategy **ratified 2026-07-02** — decouple).
+**Accepted** (2026-06-29; all **[RATIFY]** items resolved 2026-07-02).
 Companion checklist: [`docs/1.0-readiness.md`](../../docs/1.0-readiness.md).
 
-This ADR frames the decisions a 1.0 release commits to; the bracketed **[RATIFY]**
-items are open calls for the maintainer to confirm before this moves to *Accepted*.
-It does not itself change any code or contract. **§2 (version-line strategy) is
-ratified: decouple — npm/PyPI/NuGet `→1.0.0`, Java/Kotlin `→8.0.0`, tied by a shared
-`Metamodel 1.0` spec version.** The §3 items (A2 FR-024, A3 deprecated export, A4
-own-your-codegen) remain open.
+This ADR frames the decisions a 1.0 release commits to. All bracketed **[RATIFY]**
+items are now resolved:
+- **§2 version-line strategy — decouple:** npm/PyPI/NuGet `→1.0.0`, Java/Kotlin
+  `→8.0.0`, tied by a shared `Metamodel 1.0` spec version.
+- **§3 A2 FR-024 — defer** (reserved-but-unregistered post-1.0).
+- **§3 A3 deprecated export — remove at the 1.0/8.0 cut** (G2, not before).
+- **§3 A4 own-your-codegen — ratified per-port-idiomatic + documented.**
+
+It does not itself change code; the one-time moves it commits to (version
+re-baselining, the export removal) execute at the cut per `docs/1.0-readiness.md` §G.
 
 ## Context
 
@@ -126,18 +130,28 @@ by the conformance matrix. Pre-cut the vocabulary is "Metamodel 0.x / in
 development"; the cut *freezes* it as `1.0` (mirroring OTel's own 0.x→1.0). Tracked
 in `docs/1.0-readiness.md` (§C).
 
-### 3. Gating items — the breaking-change consolidation window — **[RATIFY each]**
-
-Treat the next one or two `0.x`/`7.x` releases as the window to land every breaking
-change we still want, then freeze. Before cutting 1.0:
-- **FR-024 declared-API:** land it, **or** explicitly defer post-1.0 with
-  `api.*`/`operation.*`/`binding.*` *reserved but unregistered* (so adding them later
-  is additive, not breaking). **[RATIFY: land vs defer]**
-- **Deprecated `codegen-ts/generators` export:** remove at 1.0 (1.0 is the natural
-  major for it), **or** consciously retain one more line. **[RATIFY: remove vs keep]**
-- **Cross-port "own your codegen":** ratify that it is *per-port-idiomatic* (TS
-  `meta init`; JVM/Python/C# via build config) and **document that explicitly**, OR
-  close a parity gap first. **[RATIFY: idiomatic-and-document vs close-gap]**
+### 3. Gating items — the breaking-change consolidation window — **[RATIFIED 2026-07-02]**
+
+Treat the next one or two releases as the window to land every breaking change we
+still want, then freeze. Before cutting 1.0:
+- **FR-024 declared-API — [RATIFIED: DEFER].** `api.*`/`operation.*`/`binding.*` stay
+  **reserved but unregistered** post-1.0 (they are already absent from
+  `expected-registry.json`; ADR-0030 defines the shape). Adding them later is
+  *additive*, so deferral costs nothing and keeps the declared-API surface out of the
+  1.0 breaking window. This is what makes the quiet period achievable — it removes the
+  only remaining candidate for another breaking round (§C3). Tracked in #10.
+- **Deprecated `codegen-ts/generators` export — [RATIFIED: REMOVE at the cut].** The
+  `@deprecated ADR-0034` re-exports (`entityFile`/`queriesFile`/`routesFile`/`barrel`
+  from `@metaobjectsdev/codegen-ts/generators`) are removed **as part of the 1.0/8.0
+  major bump (G2)** — *not before*. Removing an export is itself a breaking change;
+  doing it at the major absorbs it, whereas doing it during the run-up would restart
+  the quiet-period clock (§G3). Consumers migrate to the `meta init`-scaffolded owned
+  copies under `codegen/generators/*`.
+- **Cross-port "own your codegen" — [RATIFIED: idiomatic + document].** The per-port
+  split is intentional and *not* a parity gap to close: TS uses `meta init`
+  scaffold-and-own; the JVM/Python/C# ports own their codegen via build config
+  (Maven `metaobjects:gen`, `metaobjects gen`, `dotnet meta gen`). Documented in
+  `docs/features/own-your-codegen.md` (readiness D4).
 - **Metamodel freeze:** the metamodel-1.0 vocabulary program (`0.15.0`/`7.7.0`;
   ADR-0036/0037/0038) was the intended finalization, and ADR-0037 sets the framework
   for future additions; `registry-conformance` is the enforcer. **The actual last