Skip to content

Final Recording Checklist

Before recording

  • [ ] https://provifact.tmcoconsulting.com/api/status reports LIVE SANITIZED TENANT DATA, current freshness, openai, fixed gpt-5.6-terra, and model availability.
  • [ ] Status snapshot matches the public Mission package and the reviewed protected audit artifact.
  • [ ] A protected refresh is complete if evidence is stale or the expected fleet aggregate cannot be explained.
  • [ ] Production home, Mission Control, Baseline Plan, and Judge Guide load over HTTPS.
  • [ ] Browser console is clean; keyboard and mobile checks pass.
  • [ ] A single bounded Assistant question succeeds and retains its generated/review-required label, references, limitations, and review questions.
  • [ ] Current visible counts and finding choice are written in private recording notes only.
  • [ ] Notifications, password managers, cloud consoles, profiles, and unrelated tabs are closed.

During recording

  • [ ] Record only public-safe pages.
  • [ ] Show the live/synthetic mode and human-review boundary.
  • [ ] Say “technical alignment” or “matches desired state,” never compliant, MET, satisfied, or certified.
  • [ ] Explain 98 approved inventory rules, four exact reviewed joins, and the visible backlog.
  • [ ] Show one deterministic trace and one GPT-5.6 answer with evidence references.
  • [ ] Explain that Git revert does not revert Intune and Provifact has no write operation.
  • [ ] Keep the final timeline below 3:00.

After recording

  • [ ] Watch the exported file start to finish with headphones.
  • [ ] Verify no tenant, client/object, policy/group/device, serial, user, email, domain, token, key, notification, browser history, or cloud-console identifier is visible or audible.
  • [ ] Verify text is readable at 1080p and the narration matches the screen.
  • [ ] Verify only authorized TMCO Consulting / Provifact assets appear.
  • [ ] Upload to the TMCO Consulting YouTube channel using the publishing runbook.
  • [ ] Test the final URL signed out and insert it into Devpost.
  • [ ] Run /feedback in the primary Codex task and paste the returned identifier into Devpost only.
  • [ ] Submit and verify the green Submitted state before the deadline.