Skip to content

Progress: Anuva Bento Integration

Product change

Item State Evidence
Linear parent ANU-8 In Progress Linear issue
Product planning branch Merged Product Main PR #12, merged 2026-07-24
Product plan preview Approved Change overview
Plan approval Approved Girish approved the plan as written on 2026-07-24 at 06:06 UTC
Planning PR Merged #12, merged at 2026-07-24 06:11 UTC
Bootstrap child Done ANU-9; Bento PR #1; Product Main PR #13; completion report
Feasibility spike Done ANU-10; Bento PR #2; completion evidence
Product go/no-go Proceed Decision, recorded 2026-07-25; Unity/Vuplex and performance testing deferred to ANU-15
Production children Ready ANU-11 through ANU-16 are created and governed by their dependency graph
Product completion review Not started Gated on terminal required children

Current decisions

  • Approved: adopt an independent private anuva-bento downstream with preserved upstream ancestry.
  • Approved: treat Product Main invariants as normative while the downstream owns executable schemas, player/editor builds, templates, and artifacts.
  • Approved: require one three-surface aggregate and one authoritative timeline.
  • Approved: require Web/Unity exact-runtime parity, offline deterministic playback, and a clean development-phase Reveal cutover.
  • Approved: bootstrap the new repository/harness before creating Bento-owned Linear issues.
  • Approved: require a completed feasibility spike and a separate explicit Product Main go/no-go decision before production implementation starts.
  • Approved on 2026-07-25: proceed from ANU-10 into production implementation based on the revised Web-feasibility evidence.
  • Deferred from ANU-10: Unity/Vuplex verification and performance profiling. Both remain mandatory in ANU-15 and final ANU-8 acceptance.

Current gate

ANU-11 is the next unblocked implementation child. Starting it still requires the normal issue-start mutation and separate approval of its generated Implementation Plan. This proceed decision does not start any child automatically.

Next proposed sequence

  1. Start and deliver ANU-11 through its implementation-plan approval boundary.
  2. Deliver ANU-12 and ANU-13 after ANU-11.
  3. Deliver ANU-14 after ANU-12 and ANU-13.
  4. Deliver ANU-15 after ANU-11 and ANU-13, including the deferred Unity/Vuplex verification and three-WebView performance evidence.
  5. Deliver ANU-16 after ANU-13 and ANU-15.
  6. Perform the Product Main completion review only after every required child is terminal, then use the guarded ANU-8 Done transition.