Why I built it
Creative capture breaks down when planning, recording, review, and automation live in disconnected tools with unclear authority.
What exists
The system and Mac control plane are running. Publishing has not been released, and no posting results are claimed.
- Focalane Recorder
- Signed, installed, attended-accepted
- Focalane Capture
- iPhone production candidate accepted
How it works
A Mac control plane coordinates planning and evidence. Recorder handles macOS takes and review; Capture handles iPhone camera acquisition.
- Running Mac control plane
- Signed and installed macOS Recorder
- Production-candidate iPhone Capture delivery
- Take review and evidence-oriented workflow
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.
What I checked
- runtimeSystem and Mac control plane running
- attendedRecorder signed, installed, and attended-accepted
- candidateCapture production-candidate delivery accepted
What stays bounded
- Publishing is unreleased
- No publishing outcomes are claimed
- No merged writing-plus-camera application exists
What is missing
- Public screenshots remain deferred until the product landing surface uses the Focalane family name.
Next
Publish a sanitized family landing page and evidence summary.
Later ideas, not current features
- Finish the public family naming transition
- Recruit a bounded attended beta
- Release publishing only after its own acceptance work