vex-hyperframes-director

name

vex-hyperframes-director

description

Direct, implement, debug, or review Vex HyperFrames explainer visuals using evidence-backed semantic contracts, curated blueprints, deterministic HTML motion, and semantic QA. Use for Auto Visuals HyperFrames quality work, new semantic scene families, storyboard or production-contract changes, generated HTML safety, renderer failures, irrelevant or fabricated visuals, template replacement, and HyperFrames skill-pack improvements.

Vex HyperFrames Director

Build explanations, not themed slides. Treat transcript evidence as the truth boundary and reject unsupported visuals before HTML generation.

Workflow

1. Inspect visual_explanation.py, vex_hyperframes/compiler.py, and the relevant caller before changing renderer code.
2. Build or validate Visual Explanation IR. Require evidence-backed facts, typed objects, semantic beats, required labels, and explicit rejection reasons.
3. Compile a signed visual claim graph with typed nodes, directed relations, sequence, and blind proof questions.
4. Rank curated blueprints as search priors and generate multiple structurally distinct proof programs.
5. Build a separate production contract for every candidate before composition.
6. Compile only contract-backed content into deterministic, self-contained HyperFrames HTML.
7. Blindly decode sampled frames without exposing the intended answer, then grade the decode against the claim graph.
8. Run relation-ablation and temporal-scramble counterfactuals before visual-quality promotion.
9. Repair only bounded, diagnosable failures after all untouched proof candidates compete.
10. Add golden fixtures and regression tests for every new explanation pattern.

Hard Rules

• Never invent metrics, thresholds, interface states, entities, risks, steps, or outcomes.
• Never silently fall back from an unsupported semantic request to a quote or generic card layout.
• Never let visual polish override a failed grounding, label, object, beat, or screenshot check.
• Keep all motion seekable through window.__timelines[compositionId].
• Keep generated compositions local-only and free of remote URLs, arbitrary scripts, and shell execution.
• Preserve object identity when a state transforms, a token moves, or ownership changes.
• Keep legacy templates backward-compatible, but route automatic generation through semantic blueprints.
• Never treat blueprint selection as the final visual; search over distinct proof encodings.
• Never provide the intended thesis, labels, or relations to the blind inverse decoder.

References

• Read contracts.md when changing IR, storyboard, production contracts, or rejection behavior.
• Read blueprints.md when adding or selecting scene types and blueprint variants.
• Read motion-and-layout.md when implementing HTML/CSS/timeline behavior.
• Read qa-and-repair.md when changing frame inspection, semantic QA, retries, or rerouting.
• Read examples.md for expected contract shapes and user-request mappings.

Verification

Run focused semantic/compiler/composer tests first, then renderer and Auto Visuals tests. Finish with the complete pytest suite when the change affects planning, rendering, QA, or compositing.