Skip to content
bflo.sh

Prototype 4

The platform's own design set, published on the platform it describes — from the agent team that builds it to the machinery serving this page.

Story

10 steps · read in order

A site that explains itself

Everything under Prototype 4 is the real design set of this site — constitution, contracts, decisions. Follow the marks to see how Contract-First Agentic Delivery works.

This page is where the story begins — step 1 of 10.

  1. One repo, one boundary

    The repository splits into contract, backend, frontend, and infra — and the contract is the only thing two tiers may share.

    read ~/internals/prototype-4/overview.md

  2. Rules that bend for nobody

    Every agent session loads this file first. Ownership is exclusive, dependencies point one way, and nothing ships against an unpublished interface.

    read ~/internals/prototype-4/constitution.md

  3. Six agents, one lead

    Work is routed by ownership to specialized agents; the interactive session orchestrates and verifies rather than implements.

    browse ~/internals/prototype-4/agent-team/

  4. Phases open on the user's word

    A phase starts only when its task list is confirmed — then runs as a deterministic workflow with per-task model and effort.

    read ~/internals/prototype-4/agent-team/orchestration.md

  5. The spec never chases the code

    Interfaces are proposed, versioned, and published before anyone implements against them; drift is fixed in the contract, not around it.

    read ~/internals/prototype-4/agent-team/rules-of-engagement.md

  6. The application itself

    From the generic tier model to one concrete product: a blog where the filesystem is the CMS.

    browse ~/internals/prototype-4/application/

  7. Files, not forms

    Articles are Markdown files with front-matter; publishing is saving a file. The database only ever holds a derived index.

    read ~/internals/prototype-4/application/master-blueprint.md

  8. Save → live in under 90 s

    A reindex tick, a signed webhook, and cache tags carry an edit from disk to the page you are reading — no restarts, no deploys.

    read ~/internals/prototype-4/application/how-it-works.md

  9. Every why, on record

    Seventeen accepted ADRs document each consequential choice — including the ones behind the page you are reading.

    browse ~/internals/prototype-4/decisions/

Also in this directory