Demo Material

HVE Core's delivery workflow produces an HTML training deck and a video for each of four depth levels. Each level targets a different audience and builds on the one before it. The catalog reads the published build index and shows links only when that level has a complete passing bundle.

Checking published demo material...

HVE Core demo material publication status

Level	Audience	Length	Published material
L100	New contributors and first-time HVE Core users	4 to 6 min	Status unavailable
L200	Contributors ready to follow a guided task	6 to 8 min	Status unavailable
L300	Engineers choosing an applied workflow	8 to 10 min	Status unavailable
L400	Maintainers and contributors extending HVE Core	10 to 12 min	Status unavailable

L100 and L200 videos show the deck slides. L300 and L400 add live VS Code captures of the repository files they discuss.

The browser slides use the same presenter controls as the HVE Core presentations: arrow keys to move, a slide index, speaker notes, the level's sources, and a reading view. Each is one self-contained HTML file, so you can download it and present offline.

Accessibility

Every level is published with:

• Visible text embedded in the MP4 and as a separate WebVTT file, generated from the authored speaker notes
• A video page with a captioned player and a full transcript listing each slide's title, on-screen text, image descriptions, and narration
• A text transcript describing each slide and live capture; new CI videos have no voiceover or audio stream
• A deck with a title on every slide, alternative text on every image, and the document language set, so screen readers can navigate it
• Browser slides with keyboard navigation, labelled slides, a reading view that reflows on small screens, and speaker notes available to every viewer
• Text colors that meet the WCAG 2.2 AA contrast minimum of 4.5:1

The render workflow checks each item it can verify and withholds a level that fails. Silent CI timing is derived from the notes' word count, not synthesized speech. A human must review reading pace and whether the transcript fully describes each visual. Silent videos do not provide spoken audio description.

How the Material Stays Current

The material is rebuilt by two scheduled workflows, and only for the levels whose source documents changed:

1. The Demo Material Author agentic workflow runs weekly. A deterministic step compares each level's pinned sources with the commit its current material was built from. The agent writes new slide content for changed, failed, or unpublished levels. When every level is current and published, the agent does not run.
2. The Demo Material Render workflow attempts a daily pickup of one eligible successful author run: normally the oldest run the render index has not recorded, or the newest run when no history exists. A backlog of author runs, schedule delays, failed checks, and the first v2 publication can each delay new material, so the schedule is not a publication deadline. It builds each authored level into a HTML deck and a silent video from matching exported slide frames, then scores the checks a machine can verify: timing paired to every slide, absence of an audio stream, the video landing inside the level's length, readable live captures, the pinned house style, the accessibility items above, and browser slides that open offline with no slide overflowing. A level that fails any check keeps its previous files. The later weekly render check forces another authoring attempt for any level whose latest attempt failed or whose first passing bundle is still missing.
3. The documentation deployment publishes the latest passing files. This page reads that same index, so a missing level appears as unavailable rather than linking to files that do not exist.

New CI builds are silent: no speech service or speech model is used. Local narrated production uses an AI-generated Azure AI Speech voice. During regeneration, a level retains its previous compatible passing files until a replacement passes. The published index records narration_engine and the timing basis for new renders. The level contracts and sources define what each level covers.

Build Status

Current delivery uses demo-material-content/v2, demo-material-site/v2, manifest6 and render-result2. HTML, raw/final MP4, captions, transcript and hash-bound evidence must agree. Old metadata can trigger fresh authoring but cannot certify a new delivery. The catalog hides obsolete or incomplete links.

The first v2 publication requires explicit maintainer approval and preservation of existing published media. Recovery/deployment stop on incompatible old bundles rather than resetting the index or publishing an empty directory. The v2 migration runbook gives the maintainer-owned procedure: inventory, archive, the migrate-from-v1 render, validation, publication, and rollback criteria. This source change performs no publication.

The build index records, for each level, the commit it was built from, when it was rendered, its measured length, and the result of every check, including the most recent failed attempt.

NOTE

The decks, videos, and slides are drafted by an AI agent from this repository's documentation and checked automatically, not reviewed by a person before publication. Review a deck before presenting it to an external audience. An unavailable level exposes no media links until its first successful render.

🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.