← All work

Focalane

Script to post, without losing why it was made.

My creator command center: one local place that carries each piece of content from script through filming, editing, rendering, and review, coordinates my Mac and iPhone recorders at their verified boundaries, and publishes nothing without my explicit approval.

The idea

Focalane is for a solo creator who writes, films, edits, and posts, and keeps losing the thread between those steps. The idea sits in a note, the script in a document, the footage on two devices, and the reason the video existed fades somewhere in between. Christian built it because his own channel kept breaking at those seams, and because he wanted help that never takes the final decision away from him.

When the whole family works, a filming day should feel simple: show up, film, walk away. Focalane would turn an accepted script into the day's brief, send it to the Mac and the iPhone, take every verified take back as a candidate, and carry the cut through editing to review. Christian signs off where it matters: the first step, a middle checkpoint, and the final publish. The bet is one accountable record, not one giant app.

Today, Focalane runs on Christian's Mac. It holds the canonical scripts, runs the local edit pipeline with full human review, and receives FocalaneRecorder takes as candidates. A small owner-only relay went live on 24 September 2026 and FocalaneCapture has paired with it, but no accepted script has passed through it yet, and publishing has not been released. The rest is the road ahead.

How it works

  1. Plan + script
  2. FocalaneRecorder + FocalaneCapture
  3. Edit
  4. Review

Focalane is the central web product for plans, scripts, editing, and review. FocalaneRecorder owns Mac screen capture and durable desktop takes; FocalaneCapture owns iPhone notes, the teleprompter, the camera, and takes. Each product keeps its own authority: FocalaneRecorder's verified takes reach Focalane as candidates, while FocalaneCapture's takes stay on the phone for now. A small hosted relay (an owner-only console and API) pairs devices and will serve accepted scripts; it carries no media, camera control, rendering, or publishing. FocalaneSpatialLab is FocalaneCapture's research twin, and VoiceOfTheTexts, a separate project, connects through FocalaneCapture.

FocalaneRecorder
Separate macOS product; notarized, installed, attended-accepted
FocalaneCapture
Separate iPhone product; accepted as the owner-operated production app
FocalaneSpatialLab
Research twin of FocalaneCapture; proposals only

Where it stands today

Focalane's control plane runs locally on Christian's Mac, where it holds the canonical scripts, runs the edit pipeline, and receives FocalaneRecorder takes as candidates. On 24 September 2026 a small owner-only hosted relay went live and passed a synthetic device test, and on 25 September FocalaneCapture paired with it on Christian's iPhone; no accepted script has passed through it yet. Publishing has not been released, and no posting results are claimed.

Working now

  • Canonical scripts in Markdown and Git, with local planning, calendar, studio, and publishing-review workspaces
  • Exact-revision filming acceptance, kept separate from who wrote the words
  • Local edit pipeline: silence removal, transcription timing, subject-aware layout, and final render, with full human review
  • FocalaneRecorder batches that deliver every verified take as an immutable candidate
  • Owner-only hosted relay for device pairing, with FocalaneCapture paired
  • A bounded local agent interface with 41 non-publishing operations

Not there yet

  • The main console and the family landing page run only on Christian's Mac. The hosted relay is owner-only, and no accepted script has passed through it yet.

How it got here

  1. Began as the content and video pipeline for Christian's own channel
  2. Short-form video pipeline built; screen recording split into a separate native Mac app, because browser capture bakes the cursor into the pixels
  3. Accepted scripts exportable as teleprompter prompts for FocalaneCapture
  4. Family names frozen: the Focalane name moved from the Mac recorder to this central product
  5. Naming cutover accepted across the apps and their storage
  6. Owner-only hosted relay went live
  7. FocalaneCapture paired with the hosted relay on Christian's iPhone

What comes next

Next step

Deliver the first accepted script to FocalaneCapture and FocalaneRecorder through the hosted relay, used only after an explicit Use for filming step.

Later ideas, not current features

  1. Pair FocalaneRecorder with the hosted relay after its own signed-package gate
  2. Deliver the first accepted script to both apps through an explicit Use for filming step
  3. Run the first deliberate FocalaneRecorder production batch
  4. Run the first real pilot production cycle, with a human-approved publish

What I checked, and what stays bounded

Dated evidence

  1. FocalaneRecorder signed capture and review attended-acceptedattended
  2. System and Mac control plane runningruntime
  3. Production-candidate delivery from the earlier iPhone camera app accepted, before FocalaneCapture existedcandidate
  4. FocalaneCapture accepted as the owner-operated production appattended
  5. Family naming cutover acceptednaming
  6. Hosted relay live; synthetic device lifecycle acceptedruntime
  7. FocalaneCapture paired with the hosted relay on a real iPhoneattended

Boundaries it keeps

  • Publishing is unreleased, and every publish needs Christian's review
  • No publishing outcomes are claimed
  • The hosted relay carries accepted script copies only: no media, camera control, rendering, or publishing
  • Agents act only through the non-publishing interface
  • Each product keeps its own authority; FocalaneSpatialLab only proposes

My role

Designed the system boundaries, native capture surfaces, evidence contracts, and recovery paths; directed and reviewed the implementation and ran the attended acceptance workflow.