VCL  /  Built in Public

Built in public.
Controlled at the gate.

VCL documents the process openly because the process is part of the product. But public does not mean reckless. Anything that affects the real world goes through an approval gate.

01 / The principle

Public learning. Private control.

Two halves of the same operating model.

The lab writes about what it builds. Wins, rebuilds, failed shots, decisions. The build log is the public record. Anyone reading it can see how VCL actually works.

Operations stay inside the lab. Foreman, the gate system, the cost caps, the canon files, the keys. They do not get exposed because they happen to also be interesting. The brand earns trust by being honest, not by being naked.


02 / Build log

What the lab shipped.

Newest first. Each entry maps to a real change in a real project.

2026-06-29

VCL Website v2 build (in progress)

Rebuilt the site from the v1 portfolio into the full creative-infrastructure brand. Eight pages, expanded design system, integrated build log, design variant system. v1 archived to archive/v1/. Pending publish gate.

Building Gated publish
Web
2026-06-29

LinkedIn Publisher worker shipped (gated)

A five-gate auto-publish workflow with operator approval before the live post. Built test-first across phases A, B, and C. Operator approval flip pending tasks 14-17 before the first live post.

Live Gated
Systems
2026-06-29

FlightPlan changelog + affiliate expansion deployed

Shipped the on-site ship log (six visible entries) and integrated a second round of affiliate products. Bundle regenerated, Netlify deploy verified, source Excel archived to _processed.

Live Public
FlightPlan
2026-06-28

RECON subsystem complete

All eight phases of RECON shipped. Watches a curated feed of external AI sources, runs overnight on a cooldown, stages recommendations for the morning review. Zero recurring cost.

Live Internal
Systems
2026-06-22

FOREMAN Morning Report v0 shipped

The first daily aggregation report. Runs locally, writes to the vault, reads in the morning. Aggregation only. v0 is intentionally simple.

Live Internal
Foreman
2026-06-22

Decision Gates formalized

Five explicit approval gates added to AGENTS.md: major architecture change, spending, external publishing, irreversible actions, identity changes. Gate violations are serious operating incidents.

Public canon Doctrine
Doctrine
2026-06-21

FOREMAN v1.3 milestone

Session Budget Guard, task-load tagging, and the build-pass orchestrator shipped. The first version that genuinely keeps a long session inside its useful ceiling.

Live Internal
Foreman
2026-06-14

Media-gen tool build sequence complete

Twelve steps shipped or intentionally deferred. Vendor choice locked to Google Nano Banana and fal.ai. typography wired to Ideogram v3. upscale deferred behind a clear unwired error.

Live Internal
Tools
2026-06-06

VCL Website v1 portfolio build

First VCL web system build. Hand-coded multi-page studio portfolio. Five pages, industrial design system, gunmetal/teal/gold. Now archived to archive/v1/.

Archived
Web

03 / Gates in practice

Where work actually stops.

If the brand makes a promise about gates, the brand should also be willing to point at them.

This page itself is a working example. The redesign you are reading was built locally. The deploy step is gated. The canon file updates that come with this repositioning are gated. The new vault brief replacing the locked 2026-06-06 brief is gated.

None of those gates are theater. Each one is a checkpoint where a human reviews and either approves the change or sends it back. If the system loses the gates, the system loses the only part of it that protects the brand from itself.

See the five gates

04 / Engage

Want this approach on your project?

Transparent process. Tight scope. Real files. Gated publish.

Start a project