Week 1 Mission Ticket - Raw Clip to Approved Publish Pack 2026-06-30

First proof checkpoint for Collins. This is a sandbox production task, not a live publishing task.
⚠ SUPERSEDED — 2026-07-13 Role refocused to the daily production machine + automated sales; see builder-vision-handoff-2026-07-13.html. The week-1 proof is now five straight days of the full daily slate (see collins-start-plan-2026-07-13.html; day-to-day cadence in daily-operating-rhythm-2026-07-13.html), not the single-clip publish pack below. The content-operator framing here is retired — kept for historical reference only; do not send or plan from it.

Objective

Prove Collins can run the current B2B talking-head engine.

Why it matters

One approved pack proves the operator can ship without Akash rescuing each step.

You need to

Provide or approve the raw clip source, then review the finished pack. ~20 min total.

Status

Ready to assign after candidate handoff and scoped file access are approved.

The ticket needs you
★ Default: use the canonical VSL pack as the fallback input if Akash has not provided a fresh clip before kickoff.
Definition of done no action
DeliverableDone means
Working pack folderClear folder structure with source, video, statics, copy, checks, and notes. Original canonical files are not overwritten.
Recording packetHooks, angles, bullets, CTA options, proof/must-say notes, and avoid-saying notes for the clip. It can be short, but it must exist.
ManifestLists source clip, transcript path, rough-cut status, render path, statics/copy/check paths, and any skipped step.
TranscriptTranscript is usable, segmented, and named. If word-level timing is not available, the gap is documented.
Rough cutDead air is removed or the pack clearly says no cut was needed. Silence cutting is enough for week 1; meaning-aware bad-take removal is phase 2.
Props/briefProps or production brief explains hook, overlay moments, CTA, and source assumptions.
9:16 reelRendered or assembled reel is watchable, on-brand, and checked for text overflow, missing assets, and dead space.
Static candidates3-5 static/carousel candidates from the transcript or message, with notes on which are ready vs needs polish.
Copy packageCaption draft, title/hook, CTA, and publish notes are ready for Akash review.
QA proofContact sheet plus screenshots or frame checks show the beginning, middle overlay, end card, and any caption treatment.
Loom walkthrough5 minutes or less: what he did, where files are, what failed, how to rerun, and what is still held.
Repeatability noteAnother session can repeat the process from his notes without needing Collins live.
Target inputs and outputs with status tracker
TypeItemStatusOwnerNext action
InputOnboarding packetReady localAkashApprove before sharing externally.
InputExisting content-engine docsReady localAkashShare scoped read access if onboarding starts.
InputAI Builder video handoffReady localAkashInclude in reading list.
InputIG visual standardReady localAkashInclude in reading list.
InputLocal Pack Machine guideReady localAkashInclude in reading list.
InputCanonical VSL publish packReady local; external share heldAkashShare only a scoped copy if using fallback clip.
InputFresh raw talking-head clipOptional; pending AkashAkashProvide only if a new clip is ready before kickoff.
InputRaw clip accessHeld pending approvalAkashApprove scoped file share.
InputTranscript file or transcript processPartly readyCollinsUse existing transcript first; document any gap.
InputRemotion projectReady local; Collins access heldAkashGrant scoped build access only if approved.
InputContent registryReady localCollinsRead first; update only assigned row/status.
InputCaption test filesReady localCollinsUse for caption decision note.
InputStatic/style examplesReady localCollinsUse existing style before making new templates.
InputAkash CTA / offer contextReady localCollinsUse approved St. Pierre positioning only.
InputDaily update templateReady localCollinsUse daily during week 1.
InputLoom accessCandidate can use own account; St. Pierre workspace heldCollinsUse own Loom unless Akash approves workspace invite.
Output24-hour planPending CollinsCollinsSend before building.
OutputCurrent-engine summaryPending CollinsCollinsWrite before build or inside first Loom.
OutputWorking pack folderPending CollinsCollinsCreate working copy.
OutputRecording packetPending CollinsCollinsDraft hooks, angles, bullets, CTA, proof notes, avoid-saying notes.
OutputManifestPending CollinsCollinsList source and output paths.
OutputTranscript or transcript gap notePending CollinsCollinsUse existing transcript or generate/document gap.
OutputRough cut or no-cut notePending CollinsCollinsRemove dead air or document no cut needed.
Output9:16 Reel candidatePending CollinsCollinsRender or assemble review candidate.
Output3-5 static/carousel candidatesPending CollinsCollinsCreate candidates from transcript/message.
OutputCaption, title/hook, CTAPending CollinsCollinsDraft publish copy.
OutputQA screenshots/contact sheet/check framesPending CollinsCollinsCreate visual checks.
OutputContent registry updatePending CollinsCollinsUpdate only assigned row/status if access approved.
OutputLoom walkthroughPending CollinsCollinsRecord final handoff.
OutputApproval listPending CollinsCollinsList remaining access/live-system asks.
Step-by-step run no action
  1. Read the source docs: start-here, tech-stack map, video intake addendum, two-engine map, visual standard, Local Pack Machine guide, Remotion README, canonical publish pack.
  2. Send a 24-hour plan: list the exact clip, files, output folder, and expected finish time before building.
  3. Make a working copy: never overwrite the canonical VSL pack or Remotion source files unless explicitly assigned.
  4. Inspect the existing pack: source clip, transcript, render variants, checks, caption tests, and known open caption decision.
  5. Reproduce the intake path: use Local Pack Machine or an equivalent working copy where possible; document any environment issue.
  6. Write the manifest: every source and output path should be listed so the pack is repeatable.
  7. Build the review pack: final video candidate, statics, copy, checks, and manifest notes.
  8. Self-QA: watch the full reel, check text fit, check CTA, confirm no fake proof, confirm no live publishing.
  9. Handoff: send Loom plus daily update format, with the exact ask from Akash.
What not to turn this into guardrails
If Collins believes a live account is required, he must stop and write the exact ask. Do not grant access in the middle of the ticket.
Scorecard reference only
DimensionPass signalFail signal
Instruction-followingUses current files, makes a working copy, honors held-access rules.Rebuilds from scratch or asks for live access before proof.
Technical executionCan run, debug, or clearly document the current render/pack process.Only proposes tools without producing a usable pack.
Content tasteOutput is readable, on-brand, and does not require Akash to rewrite every decision.AI-looking copy, cluttered graphics, text overflow, or fake proof.
DocumentationRepeatable notes and Loom are clear enough for another session.Output exists but the process is invisible.
Operating behaviorBlocks are surfaced quickly with a concrete ask.Goes quiet or waits until deadline with vague blockers.
Path: Projects/St_Pierre_Digital/Recruiting/Collins-Onboarding/week-1-mission-ticket.html