---
id: PLN-0094
ticket: vm-render-parallel-execution-boundary
title: Specify Async Render Boundary
status: open
created: 2026-06-05
ref_decisions: [DEC-0031]
tags: [spec, runtime, renderer, architecture]
---

## Briefing

`DEC-0031` needs canonical English spec coverage before worker-oriented code becomes normative.

## Objective

Publish the async render boundary contract in the canonical specs location.

## Dependencies

- Source decision: `DEC-0031`.
- Should run before large worker implementation plans are executed.

## Scope

- Add or update English spec text for packet completeness, handoff, pacing, AppMode policy, epoch ownership, and telemetry.
- Link the spec language to runtime concepts without exposing implementation-only details.
- Keep `DSC-0041` foreground stack details out of this spec pass except as explicit out-of-scope reference.

## Non-Goals

- Do not document future Game3D behavior beyond extensibility notes.
- Do not write lessons; lessons happen after execution.
- Do not encode implementation file paths as spec requirements.

## Execution Method

1. Locate canonical specs for runtime/render/AppMode.
2. Add a section for asynchronous render boundary or update the closest existing spec.
3. Translate normative parts of `DEC-0031` into concise English spec language.
4. Add out-of-scope note for Game pause/resume and VM-backed Shell coexistence under `DSC-0041`.
5. Cross-check terminology against existing specs.

## Acceptance Criteria

- Canonical specs describe the async render boundary in English.
- Spec language covers all seven decision areas.
- No Portuguese text is introduced in specs.
- The spec does not require worker implementation before the plan for it exists.

## Tests

- Documentation review.
- `rg` check for accidental Portuguese in touched spec files.
- Existing doc/spec validation scripts if present.

## Affected Artifacts

- Canonical specs location in the repository.
- `discussion/workflow/decisions/DEC-0031-vm-and-render-parallel-execution-boundary.md` as reference only.