Walking skeleton: publish, switch, run, reclaim a generation
Goal
A rebuild publishes a new generation, the pointer switches atomically, ori run executes it, and the superseded generation is reclaimable.
Implementation Sketch
Derived from compiler_repo/docs/ori_lang/proposals/approved/binary-generation-lifecycle-proposal.md. Depends on the cache root, budget, collection pass, and D3a in-flight-reference primitive delivered by plans/cache-lifecycle/ (approved cache-lifecycle-proposal.md). Implement the work items in order.
Spec References
- Approved proposal:
compiler_repo/docs/ori_lang/proposals/approved/binary-generation-lifecycle-proposal.md - Depends on:
compiler_repo/docs/ori_lang/proposals/approved/cache-lifecycle-proposal.md(D3a primitive, composed bound) - Umbrella invariant T4:
compiler_repo/docs/ori_lang/proposals/approved/toolchain-philosophy-proposal.md
Work Items
- Thin end-to-end slice:
ori buildpublishes a binary as an immutable generation, the current pointer switches atomically,ori runexecutes the materialized deliverable, and a superseded generation is reclaimed — exercised through theoriCLI