Skip to content

Content Creation Recording Workflow, design + build, 2026-06-11

URL: https://mkdocs.justinsforge.com/memory/handoffs/content-recording-workflow-2026-06-11/

You are a Fable 5 worker. Justin wants his end-to-end content recording-to-edit workflow designed and, where ready, built. This is a research + architecture + implement job. Think hard about the full pipeline before writing code. Produce a design doc first, get the shape right, then build the pieces that are clearly correct (the folder-scaffold script especially). Flag anything that needs Justin's hardware/account access before you can finish it.

Who Justin is + the fleet (context you must use)

  • Content creator, multiple brands (JustinWieb-VR, Nova Design, Gus Outdoor Co, Sip-N-Serve). Austin TX. Not a SWE; commission tweaks in plain language, never hand him code to edit (feedback_no_code_edits_for_justin.md).
  • Endpoints: Sol (Mac), Vector (Windows PC, RTX 5070 / 9950X), Venus/Astra (iPhone), Finn (Proxmox host serving NFS), Console (this dev VM). See fleet.
  • Storage tiers (reference_storage_policy.md): Google Drive (cloud/mobile docs), 8TB NVMe (active video + brand work), 24TB HDD (Plex + cold archive). All Finn-served NFS to Console. Active video editing lands on the 8TB NVMe.
  • Adobe Creative Cloud active (Premiere, Photoshop, After Effects) — user_adobe_creative_cloud.md. Premiere MCP lives on Sol: Adobe_Premiere_Pro_MCP at /Users/sol/Adobe_Premiere_Pro_MCP/, 97 tools via Claude Desktop (reference_premiere_mcp_sol.md). That is a real lever for programmatic project creation.
  • Vector has its own Claude Code + memory at C:\Users\Justi\forge-vector-local\, pairs with Console via shared scratchpad (reference_vector_claude_code.md). Use /sshrequest if you need to act on Vector or Sol from Console.

The three problems to solve

1. Folder-scaffold macro to AI-driven script

Today there is a macro on Windows AND Mac that builds a dated folder structure: <date>/<project-name>/ with exports/, assets/, etc. Justin wants this to be an AI-callable script instead of a manual macro, so the agent can scaffold a project on request. - Find the existing macro/structure (ask via scratchpad or inspect; on Mac it may be a Keyboard Maestro / Automator macro, on Windows an AutoHotkey or PowerToys macro). Reverse-engineer the exact folder template Justin already uses; do not invent a new one. - Build a canonical, cross-platform forge_project_scaffold.py (Forge naming, snake_case, flat dir, verbose name) that takes a project name + optional date and creates the structure on the 8TB NVMe active-video path (confirm the real path via Finn NFS mount). Make it idempotent (re-running = same end state). - Register it: SKILL.md if user-invocable (/scaffold-project <name>), topic file memory/general/reference_project_scaffold.md, MEMORY.md index line, smoke test. This is the seen-twice/wrapper signal for /learnskill.

2. Blackmagic Cam (iPhone) footage straight to the network drive

The pain: recording on Blackmagic Camera app on iPhone 16 Pro Max + 17 Pro Max. Footage lands in Apple Photos, iCloud uploads it fast, and it is a fight to get the originals onto the network drive at full quality. Justin wants: record → footage lands on the server file share automatically (or near-automatically), no iCloud-recompression detour. - Research the Blackmagic Camera app's actual export/sync options (cite official Blackmagic docs/forums): does it support saving to Files / a SMB or NAS location, FTP, or a direct network export rather than only the Photos library? Newer versions and Blackmagic Cloud / Dropbox sync may be relevant. - Evaluate paths to a Finn SMB/NFS share or a Files.app-mounted server folder, an iOS Shortcuts automation that moves new Blackmagic clips off the Photos library to the share, and whether Blackmagic Cloud + a watch-folder ingest on Finn is cleaner. - The hard constraint: preserve the original-quality file (ProRes/H.265 as recorded), do NOT let iCloud optimize-storage hand back a recompressed proxy. Call out the iCloud "Optimize iPhone Storage" trap explicitly. - Recommend ONE primary workflow + a fallback, with exact setup steps. If a watch-folder ingest on Finn is the answer, sketch the script (forge_ingest_watchfolder.py style) but don't fully build until Justin confirms the share path.

3. Auto-build the edit project (Premiere, open to DaVinci) with transcript + rough cut

Once footage is on the server in the scaffolded project, Justin wants the edit project auto-created with the media linked, ideally already transcribed and roughly edited down. - Premiere route: use the Premiere MCP on Sol (97 tools) to create a project, import the assets folder, and build a sequence. Assess what the MCP can and cannot do (project create, import, bins, sequence, markers). Cite the tool list if reachable. - Transcription: Forge already has a transcription path (yt-dlp/ffmpeg + whisper-style in /watchyoutube). Check forge/scripts for an existing transcription helper before building one. Transcript drives a text-based rough cut (remove silences/filler, mark keepers). - DaVinci Resolve alternative: Resolve has a documented Python scripting API (free, powerful, scriptable end-to-end). Justin is open to it. Compare Premiere-MCP vs Resolve-API for THIS automation goal honestly: which gets him to "auto-imported, transcribed, rough-cut project" with less fighting. Make a recommendation, do not hedge.

Deliverable

Write forge/memory/handoffs/content-recording-workflow-findings-2026-06-11.md (mkdocs URL line at top) with: 1. The full pipeline as one diagram-in-words: record → ingest → scaffold → project → transcript → rough cut → edit. 2. Problem 2 (iPhone→server) recommended workflow + fallback, exact steps. 3. Problem 3 Premiere-MCP vs DaVinci-API recommendation with reasoning. 4. What you BUILT this pass (the scaffold script if you nailed the template) vs what is blocked on Justin's input/access. 5. Prioritized next actions.

Build forge_project_scaffold.py + its registration IF you can confirm the existing folder template and the NVMe path. Otherwise specify exactly what you need from Justin. Notify with the findings path when done.

Start

Read fleet + storage + Premiere-MCP memory, find the existing folder macro, research Blackmagic Cam export options and the DaVinci scripting API, then write the design. Robust over quick (feedback_robust_over_quick.md): no band-aids on the iCloud-quality problem, solve the originals-preservation properly.