# Created on `2026-05-27`

## Status

`closed`

## Purpose

This note closes the stale-routing gap for the retained support-plane rows that
already sit subordinate to the landed `3R-C` analytics anchor and the landed
`3R-D` browser-viewer / asset-QA anchor:

- `ecomfe/zrender`
- `ecomfe/echarts-gl`
- `google/model-viewer/packages/model-viewer-effects`
- `google/model-viewer/packages/modelviewer.dev`
- `google/model-viewer/packages/render-fidelity-tools`
- `google/model-viewer/packages/space-opera`
- `KhronosGroup/glTF-Sample-Renderer`
- `KhronosGroup/glTF-Sample-Viewer`

The ownership packet, later implementation packets, and later reference
provenance boards already kept these rows subordinate. The stale layer was the
state board and `v6.3` row-source pack still leaving them on the generic
`phase0r_permissive_eval_then_implement` lane.

## Current judgment

- no previously landed product packet needs reopening
- no product code change is justified from this pass
- `Phase 3R-C` remains closed for the landed `apache/echarts` anchor
- `Phase 3R-D` remains closed for the landed `google/model-viewer` anchor
- no default widening packet is open for any subordinate row in this note

## Current live anchors

The practical anchors are already landed:

- `apache/echarts` owns the analytics and reporting lane
- `google/model-viewer` owns the browser presentation, editor, and viewer lane

Later canon already made the adjacent reference and support side explicit
without converting the subordinate rows into separate live implementation
lanes:

- `KhronosGroup/glTF-Sample-Viewer` reference provenance is already explicit
- root `google/model-viewer` reference provenance is already explicit
- `shared-assets` stayed a separate boundary lane
- the closure sweep already treated the viewer support family as canonically
  closed

That means the retained value from the rows below is subordinate support value
only, not new owner-lane authorization.

## Analytics subordinate slices

### `ecomfe/zrender`

Retain only:

- the lower-level `2D` painter and event substrate beneath `apache/echarts`
- scene storage, painter, handler-proxy, and animation patterns that stay
  below the reporting anchor

Do not promote:

- the row into a separate analytics owner
- the row into a general browser-visualization foundation
- the row into a default follow-on widening packet

### `ecomfe/echarts-gl`

Retain only:

- the optional `3D` analytics and explainer sidecar beneath `apache/echarts`
- the bounded GL analytics extension role, not a runtime foundation

Do not promote:

- the row into a separate `3D` owner lane
- the row into a browser-spatial runtime lane
- the row into a default widening packet

## Browser-viewer and asset-QA subordinate slices

### `google/model-viewer/packages/space-opera`

Retain only the bounded browser editor and inspection package beneath the
landed `google/model-viewer` lane.

### `google/model-viewer/packages/model-viewer-effects`

Retain only the subordinate emphasis and effects package beneath the landed
`google/model-viewer` lane.

### `google/model-viewer/packages/render-fidelity-tools`

Retain only the subordinate fidelity-oracle and regression sidecar beneath the
landed `google/model-viewer` lane.

### `google/model-viewer/packages/modelviewer.dev`

Retain only the subordinate docs and demo infrastructure beneath the landed
`google/model-viewer` lane.

### `KhronosGroup/glTF-Sample-Renderer`

Retain only the subordinate renderer/reference substrate beneath the landed
`google/model-viewer` asset-QA lane.

### `KhronosGroup/glTF-Sample-Viewer`

Retain only the subordinate standards-aware asset QA and validation sidecar
beneath the landed `google/model-viewer` lane.

Do not promote any of the rows in this viewer family:

- into a separate browser presentation owner
- into a separate asset-QA owner
- into a default next widening packet

## Sequence correction

Current canon should therefore use:

- `phase2rb_analytics_subordinate_gap_eval_only`
- `phase2rb_browser_viewer_subordinate_gap_eval_only`
- `no default widening packet open`

The generic `phase0r_permissive_eval_then_implement` lane is stale for these
rows because:

- `Phase 2R-B` already froze their ownership and acceptance boundary
- `Phase 3R-C` and `Phase 3R-D` already landed the anchors above them
- later provenance boards made the reference side explicit without promoting
  the subordinate rows into separate live implementation lanes

## Required canon posture

Current authority surfaces should now say all of the following consistently:

- these rows are not straight permissive implementation candidates
- these rows remain subordinate beneath the landed `3R-C` and `3R-D` anchors
- these rows do not reopen analytics, viewer, editor, or asset-QA product-code
  ownership by default
- later widening may happen only if a concrete subordinate-sidecar gap is
  proven after the landed anchors and existing first-party reference-grounded
  support surfaces
