Narrow lifecycle execution contracts

[PraneethMerugu]

Summary

• prepare compact accepted-update recipes containing only incrementally maintained trackers, while reconstruction-only minima remain owned by LocalMath reconstruction
• pass narrow, readable tracker, state, structure, ownership-transfer, relationship and cadence payloads across device-reachable lifecycle boundaries instead of broad runtime/program objects
• reuse tracker-reduction plans during publication and enforce the admitted prepared-update allocation contracts
• retain one KernelAbstractions CPU/Metal execution path and unchanged scientific transaction, coercion and rollback semantics
• record reproducible compiler-boundary evidence without turning statement counts or wall time into brittle acceptance thresholds

Behavioral authority

• exact LocalMath parent: f41a37d
• complete CPU suite: 32,877/32,877 across 65 units
• focused lifecycle/relationship cohort: 1,138/1,138
• strict documentation build: pass
• maintained tracker and bounded owner-change witnesses on real Metal: pass
• relationship staging on real Metal: 14/14 with scalar indexing disabled
• hosted package job at the preceding product-identical tip: pass in 2h05m52s

CPU and Metal use the same prepared recipes, validation, mutation and settlement owners. No GPU-only scientific shortcut is introduced.

Compiler and boundary evidence

• lifecycle workspace argument summary: 9,600 to 1,012 bytes
• nonempty relationship staging payload: 26,307 to 2,043 bytes (92.2% reduction)
• final relationship kernel: 546 statements / 278 calls / 166 raw Any SSA entries, zero Any argument slots, concrete Nothing; all 166 are classified non-value control nodes
• prepared owner-transfer boundary: 819 / 454 / 230; proposal leaf: 72 / 35 / 26
• one/two/four/eight/sixteen dense recipe members share one prepared capacity type; seventeen starts the next capacity class
• fresh-process probes distinguish one generated kernel definition from the two admitted action-tag MethodInstances and demonstrate reuse across numerical kind and relationship-count changes

These results treat LLVM and typed IR as diagnostic evidence. Real Metal compilation and behavioral tests remain the authority.

Hosted Metal qualification

The preceding monolithic hosted Metal job reached and passed its semantic groups through lifecycle integer bounds, then hit the existing 180-minute job limit; it did not report a product assertion failure. This tip preserves the exact 25-witness inventory but runs it as three durable semantic groups (8/8/9) and retains one stable aggregate metal status for branch protection and automerge. The new hosted run is active.

Stack

This draft is stacked on CorePotts PR #33 (codex/site-minimum-tracker) at a4fb6c8 and should be retargeted to main only after that parent merges.