Skip to content
Built in Public

This is what building in public
actually looks like.

No manufactured testimonials. No vanity metrics. Real systems, documented as they get built — frameworks, infrastructure, output, and evidence.

3

Core frameworks built

10

FlowOS tabs live

5

Infrastructure systems wired

6

Ops boards running

Build Log

What’s been built. What’s running.

This is an early-stage build. What exists here is real — operational infrastructure, documented frameworks, and a live intelligence layer. The log updates as the system grows.

Jun 2026

Infrastructure

Delivery pipeline wired end-to-end

Connected five independent systems into one unified purchase → delivery flow. No manual intervention required after a payment.

  • Stripe checkout session + webhook verification
  • Supabase orders table — every transaction written automatically
  • Resend transactional emails — welcome, notify, admin alert
  • Beehiiv subscriber sync on purchase
  • Shopify Storefront API + orders/paid webhook

Jun 2026

Intelligence Layer

FlowOS Command Center — 10 tabs live

Built a private operations dashboard that replaces manual status checks. Real metrics, real time.

  • Subscriber growth (Beehiiv API v2)
  • Revenue tracking (Stripe dashboard integration)
  • Website analytics — 30-day window (Plausible Stats API)
  • Content queue with approval workflow
  • Social intelligence report (Metricool)
  • Loop tab — active specs, build state, next action

May 2026

Frameworks

1-3-5-10 operating framework — documented and deployed

The core system is fully specified: one focus, three priorities, five tasks, ten zones — running across five time horizons from daily to vision.

  • 1-3-5-10 structure — daily execution layer
  • Five Horizons map — daily, weekly, monthly, yearly, vision
  • FlowState / FlowZone / FlowSpace — three-layer model
  • Time unit system — Reset, Sprint, FlowZone Block, FlowMap
  • Zone Anatomy — six elements per zone, 10 zones total

May 2026

Content Engine

FlowSeries production system — spec complete

One recording session produces 38+ content pieces across every major platform. The pipeline is documented and deployable.

  • Transcript → flagship article → social thread → short-form clips
  • Email sequence extracted from every session
  • 10 content pillars mapped across 8 output categories
  • Platform-specific creative standards locked
  • Agent-powered production from transcript to distribution
What Becomes Possible

The transformation the system produces.

Scattered executionStructured daily operating rhythm
Reactive to every inputIntentional, priority-first
Manually operatingIntelligently automated
Ambitious but fragmentedIntegrated across every dimension

Understand how it works
before you install it.

The Method page walks through the three-layer framework. The Flow Letter documents it being built in real time.