# HyperTwist ECharts Reference Incorporation Provenance Board - 2026-05-27

## Status

This document is the source-backed provenance and hierarchy note for the live
repo-backed reference-incorporation side currently materialized from
`apache/echarts`.

It closes the source-specific reference side that remained implicit after the
landed `Phase 3R-C` packet and the broader live-lane audit.

It answers one narrow question:

- do the live `apache/echarts` reference targets reopen already landed
  first-party analytics, reporting, export, and timing-trend implementation, or
  do they instead need a reference-side provenance-board and canon backfill

Result:

- no product-code reopening is required
- yes reference-side provenance-board and feature-canon backfill is required

## Source basis

- `C:\HyperTwist\docs\HT_REPO_INCORPORATION_AUDIT_2026-05-11.md`
- `C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md`
- `C:\HyperTwist\docs\HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md`
- `C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md`
- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`
- `C:\HyperTwist\UnrealHyperTwist\Content\HyperTwistTraining\MaterializedCatalog\hypertwist-reference-incorporation-targets.json`
- `C:\HyperTwist\UnrealHyperTwist\Content\HyperTwistTraining\MaterializedCatalog\raw-extracts\apache-echarts-reference-pages.jsonl`

## Counts confirmed from current first-party materialization

Current live `apache/echarts` reference-incorporation targets:

- `4` total rewritten reference targets
- all `4` are under `Training Analytics`
- all `4` stay inside the already-landed `Phase 3R-C` bounded lane

Exact surfaces:

1. `reference/apache-echarts-analytics-reference-page-session-outcome-and-progress`
   - `SurfaceType`: `analytics-reference`
   - `IncorporationChannel`: `analytics-report-contract`
   - `TargetAssetFamily`: `dashboard-report`
2. `reference/apache-echarts-report-export-reference-page-data-view-and-export`
   - `SurfaceType`: `report-export-reference`
   - `IncorporationChannel`: `report-export-contract`
   - `TargetAssetFamily`: `export-note`
3. `reference/apache-echarts-analytics-interaction-reference-page-timing-trend-history`
   - `SurfaceType`: `analytics-interaction-reference`
   - `IncorporationChannel`: `analytics-interaction-contract`
   - `TargetAssetFamily`: `interaction-note`
4. `reference/apache-echarts-analytics-explainer-reference-page-optional-3d-sidecar`
   - `SurfaceType`: `analytics-explainer-reference`
   - `IncorporationChannel`: `analytics-sidecar-boundary`
   - `TargetAssetFamily`: `explainer-note`

Important adjacent fact:

- all four targets preserve option/data layering, report export, timing-trend
  interaction, and subordinate sidecar-boundary semantics already enforced by
  the landed lane
- `ecomfe/echarts-gl` and `ecomfe/zrender` remain explicit support-only lanes
  beneath the landed `apache/echarts` owner

## Slice-local verdict

| Slice | Primary authority | Secondary value kept | Result |
|---|---|---|---|
| First-party analytics, reporting, export, and timing-trend implementation | first-party current code plus landed `Phase 3R-C` packet | retained `apache/echarts` reference targets stay subordinate provenance-grounding surfaces | unchanged live implementation owner |
| Rewritten session-outcome, export, and timing-history grounding | `apache/echarts` retained permissive lane | factual option layering, dataset separation, report export, zoom-history, and rolling-window semantics are preserved while prose remains first-party | unchanged retained reference-grounding surface beneath first-party contracts |
| Optional richer explainer and renderer-boundary grounding | `apache/echarts` retained permissive lane | subordinate `echarts-gl` and `zrender` support-only posture stays explicit in first-party notes | unchanged bounded sidecar-boundary surface |

## Why no product-code reopening is required

The live surfaces here are already rewritten first-party targets, not copied
donor docs, donor component shells, donor analytics UI, or a silent upstream
private fork.

The checked targets explicitly require:

- preserving bounded option layering, dataset separation, report export,
  history-aware timing inspection, and sidecar-boundary semantics
- rewriting donor source text, donor component names, donor framework naming,
  donor shell assumptions, and donor chart-shell presentation

That means the retained surfaces are provenance and factual grounding, not
donor analytics-shell ownership.

So this pass does not reopen:

- the closed `Phase 3R-C` first-party analytics/reporting lane
- any generic BI or dashboard-shell owner lane
- any separate live-lane claim for `ecomfe/echarts-gl`
- any separate live-lane claim for `ecomfe/zrender`

## Current exact grounded role

`apache/echarts` currently grounds four live rewritten first-party
contract/reference targets for `Training Analytics`:

- session outcome and progress reporting
- analytics data-view and export posture
- timing-trend history and overview interaction
- optional richer explainer or sidecar boundary

These targets preserve bounded analytics semantics while keeping all surfaced
prose and shell framing first-party.

## Backfill result

### Earlier incorporation audit reopened

- `C:\HyperTwist\docs\HT_REPO_INCORPORATION_AUDIT_2026-05-11.md`

### Feature canon reopened

- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`

## Final call

The live `apache/echarts` reference-incorporation side is now explicit:

- `4` rewritten first-party contract/reference targets
- all `4` remain inside the landed `Phase 3R-C` analytics/reporting lane
- report/export, timing-history, and subordinate `echarts-gl` or `zrender`
  boundary posture stay explicit

This closes the `apache/echarts` reference side without reopening product
code.
