Skip to content

Progress: Bento readiness gate for ANU-14

Product change

Item State Evidence
Linear parent ANU-17 In Progress Linear issue; started 2026-07-27
Planning branch Merged Product Main PR #17, merged 2026-07-27
Product plan Approved Change brief and repository impact
Plan preview Verified Change overview; strict preview verified 2026-07-27
Plan approval Approved Girish approved the plan as written on 2026-07-27 at 15:06 UTC
Planning PR Merged #17
Bento implementation child Done ANU-18
Bento artifact delivery Accepted Bento PR #6, merged; CompletionReport
Product completion branch Active codex/anu-17-anuva-bento-fix-for-anu-14-readiness-gate-completion
Product completion review Approved Completion review; approved by Girish on 2026-07-28 at 02:16 UTC
  • ANU-11 is Done and supplies the accepted contract/player baseline.
  • ANU-12 is Done and supplies editor/contract 1.0.0.
  • ANU-13 is Done and supplies the CMS PresentationConfig v2 baseline.
  • ANU-14 is In Progress, but its approved implementation plan stops before CMS code changes until the Bento-owned readiness artifact is reviewed.
  • ANU-18 is Done. Its merged 1.1.0 source, artifact identities, and Completion Report satisfy the Bento readiness gate, so ANU-14 may resume after ANU-17 completion under its existing approved CMS workflow.

Current decisions

  • Reuse the existing validated editor-save path for both manual and autosave host requests.
  • Keep sceneId -> slideId mapping in CMS; Bento validates only surface and slide ownership.
  • Package the Signal/Paper catalog from the same source used by the runtime.
  • Advance editor protocol, editor artifact, and contract package together to 1.1.0.
  • Do not change the presentation contract, player protocol, renderer, or template-family object version unless implementation finds a real shape change and returns for plan revision.
  • Create one Bento implementation child; create no CMS, Python, Unity, or Product Main implementation child.

Current gate

Every implementation child is terminal, the Bento PR is merged, and Product Main acceptance review is approved. The next gate is guarded completion-PR delivery while ANU-17 remains In Progress.

Next proposed sequence

  1. Create, ready, and merge the Product Main completion PR while ANU-17 remains In Progress.
  2. Run the guarded Linear completion command with the absolute CompletionReview path and verify ANU-17 moves to Done.
  3. Resume ANU-14 under its independently approved CMS plan.