Start Here - Collins Content Engine Onboarding 2026-06-30
Internal onboarding home for Akash and Collins. Candidate-facing copy is separate and held until approval.
⚠ SUPERSEDED — 2026-07-13
Role refocused to the daily production machine + automated sales; see builder-vision-handoff-2026-07-13.html (with collins-start-plan-2026-07-13.html, daily-operating-rhythm-2026-07-13.html, and akash-onboarding-runbook-2026-07-13.html). The content-operator framing below is retired. Kept for historical reference only — do not send or plan from it.
Objective
Make Collins useful on the current St. Pierre content engine within one week.
Why it matters
The engine has to turn Akash recordings into publish packs without Akash managing every step.
You need to
Approve the held access list before any invites. ~8 min.
Status
Prep-only. No external action taken.
The operating rule needs you
- Collins gets full context immediately: docs, source maps, example publish pack, and a clear mission ticket.
- Collins gets live control only after proof: no live account permissions until he ships the week-1 publish pack and documents the repeatable process.
- The current system wins: Remotion, the canonical VSL publish pack, the content registry, the B2B/B2C engine map, and the current source files are the roadmap.
- The conveyor belt matters: the proof should show recording packet, raw drop/folder contract, manifest, transcript, rough cut, Reel, and checks - not just a finished MP4.
- His Vercel portfolio is proof, not the plan: do not let onboarding drift into a new website, new database, new app shell, or new content system.
★ Default: stage him on the B2B talking-head engine first, then expand to shared primitives, then B2C footage, then Big Mike skits later.
Role and terms to use no action
| Item | Use this |
|---|---|
| Candidate | Collins Adam Durado, GoHighLevel Specialist and Automation Engineer, Philippines. |
collensadamdurado@gmail.com | |
| Comp frame | $1,000/month, part-time, around 20 hours/week, 30-day trial. |
| Proof checkpoint | End of week 1: one raw Akash talking-head clip becomes an approved publish pack. |
| Role frame | Content engine builder/operator. Strong on GHL, n8n, webhooks, automation, funnel plumbing, documentation, and QA. |
| Watch-for | Can he think beyond workflows into content quality, creative refresh, and the two demand metrics? |
| Do not use | The separate $2,800 fixed 7-day sprint quote unless Akash explicitly changes the deal. |
Week-1 outcome must happen
- Input: one raw Akash talking-head clip. If no new clip is ready, use the existing canonical VSL raw clip.
- Output: an approved publish pack with transcript, props, 9:16 reel, caption notes, 3-5 static candidates, QA screenshots, and a Loom walkthrough.
- Intake proof: a manifest and contact sheet/check frame showing the raw-footage path can be repeated.
- Proof: another session can repeat the process from his notes without asking him what he did.
- Gate: nothing gets posted, scheduled, boosted, sent, or connected to live accounts during this proof.
★ First ticket: week-1-mission-ticket.html.
Required reading before he builds reference only
| Read | Why it matters |
|---|---|
| Two Content Engines - B2C + B2B | Canonical engine model: B2B and B2C are separate production functions with shared tooling underneath. |
| Raw to Distribution | Step-by-step view of the raw clip to distributed asset path. Use the pipeline, but defer to the two-engine map on architecture. |
| AI Builder video handoff | Adds the intake workflow: recording packet, raw footage drop, manifest, rough cut, MVP Reel, checks, and fanout. |
| IG visual standard | House look for Reels: close face, black hook chip, white captions, simple proof overlays, no avatars. |
| Local Pack Machine guide | Existing local pack runner that already outputs manifest, QA sheet, contact sheet, copy, statics, and carousel files. |
| Content Engine Full Automation SOW | Shows the open automation gaps: batch ingestor, static expander, caption writer, publisher, scheduler. |
| Remotion README | How the current render project works, what props it expects, and how renders are produced. |
| Canonical VSL publish pack | The best local example of source files, renders, QA screenshots, and caption tests. |
| Content registry | The existing queue of content pieces, props paths, input files, status, and notes. |
| P-1244 project record | Business definition of done for the St. Pierre content engine. |
| Operator scorecard | The bar Collins is being evaluated against. |
What Collins should not touch yet guardrails
- Slack IS our team chat (reinstated 2026-07-13) — Collins joins on day 1. He just does not post client- or prospect-facing messages as Akash.
- No sending emails, SMS, DMs, calendar invites, or offer messages as Akash.
- No granting himself or anyone else access to tools.
- No raw credentials in docs, chats, Looms, screenshots, or repositories.
- No live GoHighLevel or n8n workflow edits.
- No live database writes, schema changes, token work, or credential rotation.
- No homepage, funnel, dashboard, or Cloudflare deploys.
- No Instagram, YouTube, Meta, ManyChat, Blotato, Buffer, or Later publishing.
- No ad spend, boosting, or social account permission changes.
- No rebuild of the content engine from a new app, Vercel site, or external plan.
If an external write is later approved, log it in the Activity Ledger before or at the change and verify the rollback path.
Daily operating loop no action
- Every day ends with the daily update template.
- Any blocker lasting more than 30 minutes gets a Loom with the exact decision or missing input.
- Every build handoff includes: output link, what changed, how to rerun it, what failed, and what is still held.
- Every live-system ask is separated from the work product and put into the approval checklist.
★ Template: daily-update-template.txt.
Path:
Projects/St_Pierre_Digital/Recruiting/Collins-Onboarding/start-here.html