Starlight IntelligenceStarlightAcademy

Lesson 06 / 06 · Work

Record the build. Publish the proof.

Turn one actual artifact into a useful demonstration and a searchable lesson.

Your artifact: A recording brief, original assets and publication draft

Show the mechanism before the claim.

Capture the transformation: the question, the exact prompt, the visual result, one meaningful interaction and the accepted artifact. Keep a visible correction when it teaches something. A short demonstration should make one useful promise and show the evidence for it. Do not turn a mock into a live integration through editing.

For a Windows workflow, record the browser or editor with an available screen recorder such as OBS or an already-owned capture tool. Capture a clean 16:9 master and a deliberate portrait crop; review legibility at phone size. Add edited captions and a written transcript. OpenAI Record & Replay is a separate computer-use workflow feature on supported macOS setups, not a general video production recorder.

Publish an original answer-first lesson with an exact title, a useful worked example, primary references, a checked date and a link to the runnable artifact. Add chapters and a transcript when the actual video exists. Structured data must describe what is visible; add VideoObject only after publishing the real recording. Search and answer-engine visibility are experiments measured through qualified visits and useful artifacts, not guaranteed rankings.

Worked example · illustrative

See the decision.

A 60-second film opens on the finished comparison, shows the brief that created it, changes one input, then reveals the exported review note. Its single action is to open this lab and build a comparison with the viewer's own workflow. A longer edition explains the correction and production checks.

Run the prompt.

Use the supported host shown above and supply your own non-confidential context. Preview availability and tool access depend on your account.

Use this actual artifact and its accepted evidence to prepare a recording package. Produce a 60-second script with five timed shots, a six-minute walkthrough outline, caption text, transcript draft, three accurate titles and one useful call to action. Separate captured proof from shots still needed. Show the input, prompt, one interaction, a limitation and the portable result. Draft an answer-first lesson with primary references, checked date, accessible image descriptions and relevant internal links. Name providers as technologies used; describe any collaboration or partnership only with owner-approved substantiation. Keep publication and external messages pending until separately authorized.
Open the prompt library and studio

Make a first attempt.

Record the five shots from the course recording studio. Check every visible claim against the actual recording, then publish only after reviewing captions, rights and the destination.

Inspect your artifact

  • Every capability shown actually ran or is labeled a demonstration.
  • No private prompts, account details or credentials appear.
  • Captions and a written equivalent preserve the teaching.
  • The call to action opens a relevant usable artifact; affiliation language is substantiated.

Transfer / A fresh case

Carry the idea further.

Repeat with a different artifact and one unfamiliar viewer. Observe where they hesitate before revising the next edition.

Keep a note of your prediction, what happened and one revision. These are self-study checks, not a graded assessment.

Read the primary sources.

Checked 2026-10-20. Recheck availability, access and API versions before a real implementation.