Backfill TalkingHead reference provenance

This commit is contained in:
axiomlogicnexus 2026-05-27 17:00:59 +02:00
parent 0c1bf3a419
commit 07b84f7456
3 changed files with 149 additions and 2 deletions

View file

@ -392,12 +392,15 @@ are now explicit, and the `cutelyaware/magiccube4d` legacy `4D` reference side
is now explicit too, and the `cubing/cubing.js` classic-cubing semantic and
compliance reference side is now explicit too.
The `met4citizen/TalkingHead` embodied companion and narration reference side
is now explicit too.
The next clean bounded move is a source-backed pass on the remaining
repo-backed reference-incorporation families whose hierarchy or canon
follow-through is still only implicit in
`hypertwist-reference-incorporation-targets.json`, starting with
`met4citizen/TalkingHead` if you want the adjacent permissive companion and
narration reference side closed to the same standard.
`apache/echarts` if you want the adjacent analytics and report reference side
closed to the same standard.
For the readable all-rows follow-up board that pairs this audit with the reset schedule, use:

View file

@ -0,0 +1,143 @@
# HyperTwist TalkingHead 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
`met4citizen/TalkingHead`.
It closes the source-specific reference side that remained implicit after the
landed `Phase 3R-E` packet and the broader live-lane audit.
It answers one narrow question:
- do the live `met4citizen/TalkingHead` reference targets reopen already landed
first-party embodied companion, narration, subtitle or viseme, gesture, and
avatar-embed 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_E_TALKINGHEAD_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\met4citizen-talkinghead-reference-pages.jsonl`
## Counts confirmed from current first-party materialization
Current live `met4citizen/TalkingHead` reference-incorporation targets:
- `6` total rewritten reference targets
- all `6` are under `Embodied Companion and Narrated Coaching`
- all `6` stay inside the already-landed `Phase 3R-E` bounded lane
Exact surfaces:
1. `reference/met4citizen-talkinghead-companion-reference-page-narration`
- `SurfaceType`: `companion-reference`
- `IncorporationChannel`: `narration-contract`
- `TargetAssetFamily`: `companion-note`
2. `reference/met4citizen-talkinghead-companion-subtitle-reference-page-sync`
- `SurfaceType`: `companion-subtitle-reference`
- `IncorporationChannel`: `subtitle-sync-contract`
- `TargetAssetFamily`: `subtitle-checklist`
3. `reference/met4citizen-talkinghead-companion-avatar-reference-page-embed`
- `SurfaceType`: `companion-avatar-reference`
- `IncorporationChannel`: `avatar-embed-contract`
- `TargetAssetFamily`: `embed-note`
4. `reference/met4citizen-talkinghead-companion-gesture-reference-page-presets`
- `SurfaceType`: `companion-gesture-reference`
- `IncorporationChannel`: `gesture-mood-contract`
- `TargetAssetFamily`: `gesture-note`
5. `reference/met4citizen-talkinghead-companion-listening-reference-page-lifecycle`
- `SurfaceType`: `companion-listening-reference`
- `IncorporationChannel`: `listening-lifecycle-contract`
- `TargetAssetFamily`: `listening-note`
6. `reference/met4citizen-talkinghead-companion-boundary-reference-page-adapter`
- `SurfaceType`: `companion-boundary-reference`
- `IncorporationChannel`: `vendor-adapter-boundary`
- `TargetAssetFamily`: `boundary-note`
Important adjacent fact:
- all six targets preserve queue lifecycle, subtitle and viseme sync,
avatar-only embed, gesture or mood posture, listening lifecycle, and
vendor/asset adapter boundary semantics already enforced by the landed lane
## Slice-local verdict
| Slice | Primary authority | Secondary value kept | Result |
|---|---|---|---|
| First-party embodied companion, narration, subtitle or viseme, gesture, avatar-embed, and vendor-boundary implementation | first-party current code plus landed `Phase 3R-E` packet | retained `met4citizen/TalkingHead` reference targets stay subordinate provenance-grounding surfaces | unchanged live implementation owner |
| Rewritten narration, subtitle-sync, avatar-embed, gesture/mood, and listening-lifecycle grounding | `met4citizen/TalkingHead` retained permissive lane | factual companion timing, sync, embed, gesture, mood, queue, and listening semantics are preserved while prose remains first-party | unchanged retained reference-grounding surface beneath first-party contracts |
| TTS and asset adapter boundary grounding | `met4citizen/TalkingHead` retained permissive lane | configurable voice-service, asset-seam, and demo-only boundary posture stays explicit in first-party notes | unchanged bounded boundary-grounding surface |
## Why no product-code reopening is required
The live surfaces here are already rewritten first-party targets, not copied
donor docs, donor demo shell, donor vendor text, or a silent upstream private
fork.
The checked targets explicitly require:
- preserving bounded narration, subtitle timing, viseme alignment, avatar
embedding, gesture and mood, listening lifecycle, and configurable adapter
semantics
- rewriting donor example-shell framing, donor vendor-specific copy, donor
asset assumptions, and donor avatar-demo wording
That means the retained surfaces are provenance and factual grounding, not
donor shell ownership.
So this pass does not reopen:
- the closed `Phase 3R-E` first-party embodied companion lane
- any separate first-party speech-input or queue-owner lane
- any separate voice-output or TTS provider sidecar
- any sample-asset, demo-shell, or vendor-branded donor ownership posture
## Current exact grounded role
`met4citizen/TalkingHead` currently grounds six live rewritten first-party
contract/reference targets for `Embodied Companion and Narrated Coaching`:
- queued companion narration
- subtitle timing and viseme-envelope synchronization
- avatar-only external-scene embed posture
- gesture, mood, and coach-facing pose cues
- streaming playback and listening lifecycle
- TTS and asset adapter boundary posture
These targets preserve bounded embodied-companion 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 `met4citizen/TalkingHead` reference-incorporation side is now
explicit:
- `6` rewritten first-party contract/reference targets
- all `6` remain inside the landed `Phase 3R-E` embodied companion lane
- queue lifecycle, subtitle/viseme sync, avatar-only embed, gesture/mood,
listening lifecycle, and vendor or asset boundary posture stay explicit
This closes the `met4citizen/TalkingHead` reference side without reopening
product code.

View file

@ -195,6 +195,7 @@ repo.
| Blindfold memo attempt and validation benchmark | Deep-source grounded retained | `ambisinister/blindsolve` retained clean-room benchmark lane | Retained as `A1 + R4 + F2` only for a narrow blindfold memo attempt-phase loop, conceal/reveal validation, letter-pair token entry, parity-aware memo expectation, and lightweight repeat cadence. This does not displace the first-party timing-policy templates, coaching-memory/follow-up surfaces, replay-verification blindfold event taxonomy, or the broader memory doctrine. |
| Smartcube-aware practice-shell and review/SRS UX comparison | Deep-source grounded retained | `poliva/cubedex` restrictive reference row | Retained as `A1 + R4 + F2` only for smartcube-aware practice-shell comparison, offline-first drill UX composition, review/SRS workflow presentation, recognition-versus-execution timing presentation, and local stats/history comparison. This does not displace the current first-party training-session, review-plan, coaching, `KubeTimr` timer substrate, `CubeDesk` smart-device workflow composition, or the landed permissive trainer-foundation lanes. |
| Embodied companion/narration adjunct | Implemented now | landed `TalkingHead` packet | Live bounded avatar/narration family. |
| Rewritten embodied companion and narrated coaching reference grounding | Implemented now | `met4citizen/TalkingHead` retained permissive lane + first-party current code | Current live `Embodied Companion and Narrated Coaching` reference side includes six rewritten first-party targets grounded in retained `TalkingHead`: queued companion narration, subtitle and viseme sync, avatar-only embed, gesture and mood cues, streaming/listening lifecycle, and TTS or asset adapter boundary posture. This does not displace the landed `Phase 3R-E` first-party embodied companion owner, any separate speech-input or queue-owner lane, or any separate voice-output provider sidecar. |
| Broader long-horizon coach memory and cognitive state | Deep-source grounded retained | first-party target + memory doctrine | Doctrine-governed future widening; not yet a mature memory system. |
### 4. Catalog, curriculum, and knowledge