GUIDE — Java + Jakarta EE / MicroProfile under the Discipline, v0.1 (overlay)

§0 additions — baseline

• 04Pin the spec levels, not just the runtime: the target Jakarta EE platform/profile version and MicroProfile version are declared in the build; vendor BOM pinned. Portability is a check, not a hope: cells and seams depend on jakarta.*/org.eclipse.microprofile.* APIs at most (boundary), vendor packages (io.quarkus.., com.ibm.., etc.) are boundary-of-boundary — ArchUnit-enforced, and the rule is what keeps the second implementation possible.
• TCK resonance, used not admired: where a seam wraps a platform service, the platform's own TCK answers "does the runtime behave"; conform answers "does our code behave" — the two suites are complementary GEP rows, not overlap.

§1'/§3' — CDI as composition root

• 05No @Inject, no scopes, no interceptor bindings inside cells. Cells are new-constructed.
• Producers are the registry: explicit @Produces methods in a composition module construct cells with their capabilities — the hand-written switch in CDI clothing:

@ApplicationScoped
public class SolverProducer {
    @Produces @ApplicationScoped
    DepSolver depSolver(AppConfig cfg, DepProvider p, Clock clock) {
        return switch (cfg.solver()) {        // R-001 at the seam
            case SAT   -> new SatDepSolver(p, clock);
            case NAIVE -> new NaiveDepSolver(p);
        };
    }
}

• 07Bean discovery mode annotated (explicit beans.xml), never all — implicit-bean archaeology is the CDI form of component scanning and is banned for the same reason.
• MicroProfile Config is the runtime flag tier, with provenance built in: ConfigSources are ordinal-ordered (system props > env > files > defaults) — the platform ships the Discipline's provenance chain natively; flags resolve once into a config record at the composition root, @ConfigProperty field-sprinkling in domain code is banned.

§4' — boundary machinery

• 08Fault-tolerance annotations (@Retry, @CircuitBreaker, @Timeout, @Fallback) are interceptors — hidden control flow under R-021 — and live only on boundary/orchestration beans. If a retry policy is domain behavior, the cell implements it explicitly against its clock capability, testable without a container.
• JPA entity quarantine: entities are proxy-laden, lazily-loaded, lifecycle-managed objects — citizens of the second language. Entities never cross into cells; persistence sits behind repository seams returning records, mapping done in the adapter. The N+1 problem, detached-entity traps, and dirty-checking surprises all stay in the ring built to contain them.
• JAX-RS resources, servlets, messaging listeners: boundary adapters that parse (DTO → validation → domain types), call seams, translate sealed results to protocol responses with the REQ URI rendered on errors (PROP-014 §2.6). Health (mp-health) and metrics (mp-metrics/Telemetry) are boundary exports.

§8' — additional risk rows

10Overlay note. The platform already believes in specs, implementations, and conformance kits; this overlay only asks the application to live up to its own runtime's governance model. The framework-free-core test from the Spring overlay applies verbatim: cells compile without jakarta.* on the classpath.