Skip to content

Product Decision: Proceed after ANU-10

Decision

  • Decision: Proceed
  • Decision maker: Girish
  • Decision date: 2026-07-25
  • Parent change: ANU-8
  • Feasibility child: ANU-10

Product Main accepts the revised ANU-10 feasibility evidence and authorizes the production implementation sequence to proceed through ANU-11 and its dependent children. ANU-10 is Done, and its implementation was merged through Anuva Bento PR #2 as 94d7f05c0717d6e0d29b99c1d202978fa5824c29.

This is a product gate decision, not final acceptance of ANU-8. ANU-8 remains In Progress until every required production child is terminal and the cross-repository completion review passes.

Accepted evidence

Product Main accepts the ANU-10 Completion Report as sufficient evidence to proceed because it demonstrates:

  • a reproducible Bento v1.0.8 downstream baseline;
  • an isolated Anuva adapter and build-entry boundary;
  • a provisional three-surface envelope and versioned player protocol;
  • deterministic Web-host reset, absolute seek, and external tick behavior;
  • transparent transient Emphasis behavior;
  • embedded-font and external non-font asset readiness;
  • hard-offline behavior without public update or collaboration dependencies;
  • semantic template reapplication with explicit unsafe-mapping results; and
  • a zero-conflict upstream synchronization rehearsal with regression checks.

The provisional envelope and API remain feasibility artifacts. ANU-11 owns the normative production contract and exact player behavior.

Explicit deferrals

Product Main accepts these ANU-10 deferrals:

  1. Unity/Vuplex verification is deferred. ANU-10 does not establish Unity compatibility, three-player Vuplex behavior, capture behavior, or Web/Unity runtime parity. These remain mandatory acceptance work in ANU-15.
  2. Performance testing is deferred. ANU-10 does not establish startup, memory, CPU/GPU, frame-time, or concurrent-player thresholds. Three-WebView profiling and either approved thresholds or a Product Main-reviewed alternative remain mandatory in ANU-15.

These deferrals move verification to the production Unity child; they do not waive the corresponding ANU-8 product acceptance criteria. ANU-8 cannot complete until ANU-15 supplies the missing evidence and the final Product Main completion review accepts it.

Consequences

  • ANU-11 may start under its normal implementation-plan approval workflow.
  • ANU-12 through ANU-16 remain governed by their existing dependency graph and individual approval boundaries.
  • No child is started automatically by this decision.
  • No production package is published and no active Reveal path is removed by this decision.
  • The upstream rewritten-release provenance risk and the narrow slides/src/update.ts seam remain tracked during production work.
  • There is no release impact yet; this decision authorizes implementation only.