Complete shipped schema residency and initialization certification #46

Acceptance Criteria

• Finish compiler/library-owned layout, immutable/shared ownership and constructor/initialization envelopes for the actual closure, reusing completed metadata/NFA/one-pass/DFA/cache components.
• Deliver the common C/I descriptor generation and source proofs; target-specific ABI/physical validation is owned by #72 through #75. Reject unsupported owners instead of assigning zero or treating a shallow layout observation as a whole-heap bound.

Blocking And Review Gates

• Blocked by: #33.

Use native blocked-by/blocking links for unconditional issue relationships. Conditional target gates are not universal blockers; link only the selected applicable path after its contract is frozen.

Shared Acceptance Requirements

Every implementation issue ships its own unit/conformance, failure, resource and privacy tests. A later integration issue does not postpone those checks. New untrusted decoders include generated hostile-input controls; changed hot paths include repeatable measurements. Use the existing engine, host services, validated config/push path and EdgeZero handler registration. Preserve privacy, authorization, cookie integrity, HTTPS/SSRF protections, deadlines, exact sent coverage, authoritative bidder/alias attribution and bounded work/storage. Standalone and embedded behavior share policy rather than fork implementations.

No issue may claim a missing capability from metadata import, compilation, observed allocations, a signed cookie, or a different artifact's old evidence. New public/configuration behavior requires its reviewed design before execution. No workload reduction, raised ceiling or replacement budget equation is implied. Bodies and evidence must not publish credentials, identifiers, raw consent, private provider addresses or customer configuration.

Technical Ownership

Sources: M7-R0 design/plan, ISSUES.md resource rows and schema qualification record.

Approved Integration Contract

PR #152 merged the specification and delivery plan at 9b83deaa680ad8e867169db3b4ebb195b8a1b33c. Their shared requirements apply: whole-catalog reports with verified skipped: not_implemented rows, positive qualification of every implemented identity/alias on all four adapters, existing build discovery and the qualified common native_only retirement. The first Trusted Server host remains Fastly display; Trusted Server #1505 coordinates host-owned work. The planning merge is not implementation or qualification evidence and changes no workload limit, resource ceiling or configuration mechanism.

Discovery And Descriptor Scope

• Derive the schema closure from discovered executable definitions and bidder-owned schema/provenance, not priority/supplemental delivery lists. Retain original captured evidence without using it as an activation list.
• Generate common resident/initialization descriptors for the actual implemented closure. Reconcile exact whole-catalog report coverage separately from executable registry coverage; source-only identities sharing an implementation owner do not become implemented aliases.
• Coordinate the target-independent descriptor/admission change with Complete validation work, scratch and stack certification #47 and the actual adapter owners; remove native-only assumptions only in the accepted common cutover. Reuse existing source proofs and test ownership rather than adding another registry or proof crate.

Source Contracts

• Approved roadmap
• Product vision
• Issue ledger and qualification limitations
• Schema qualification record

Retired Ledger Reconciliation

• Include metadata/registry/schema residency and initialization contributions beyond requested-layout census: physical/allocator and linked code/data bounds, justified sharing, aggregate descriptors and matched catalog-growth measurements against the original source-bound baseline.
• Reuse completed immutable metadata, NFA/capture, one-pass and literal-DFA components. Do not reopen controlled-native dispatch/precharging or require every imported but unreachable backend as a prerequisite. A newly reachable backend needs its proof in the first affected expansion wave.

Source: retired schema-resource ledger.

Resource Proof Responsibilities

Responsible technical role: schema/compiler maintainers.

Next verification action: complete the common C/I source and descriptor proofs for the discovery-selected shipped closure, including independently compiled owners, already-live retained programs, cold or failed initialization and allocator overlap. Reuse completed component certificates. Actual target ABI, physical bounds and linked-artifact verification remain with #72 through #75.

Source: approved shared resource ownership contract, delivered for review in #162. This records responsibility and the next verification action, not completed proof, target qualification, changed workload limits or permission to close this issue.