← @bgSponge

The Company as a Codebase

Summary

Frank Chen argues that every workflow should ship two artifacts: today's result and a versioned improvement to the system that produced it.

  1. Two artifacts, one workflow.

    The result handles today; the writeback changes where the next person or agent begins.

    That is the two-artifact rule: every workflow ships the result and a versioned improvement to the system that produced it.

    The unit of work isn’t the session. It’s the diff the session leaves behind.

  2. The writeback is a pull request, not a note.

    Reviewed, merged, and deployed into ontology descriptions, the prompt builder, and reusable skills. The repo holds doctrine, never raw customer records.

  3. Build the CI habit before agent volume.

    Practice first, automation second: by the time agents write into the brain, review gates already exist. Ordinary content self-publishes; humans approve changes to the gate.

  4. Frontline capture without a keyboard.

    Operators talk-to-text the why before a job advances; a twice-weekly human gate turns repeated or expensive captures into doctrine the next job inherits.

    The result depreciates. The improvement compounds only when someone inherits it.

  5. Gates that can fail, and boredom.

    Size autonomy by blast radius. Do not close Carl's diagnosis gate because the agent is usually right. Knowledge systems die from inattention, not disproof.

    most knowledge systems die the same death: not disproven, just quietly unattended.

Read the original ↗Save to your Sponge

Summarized with Sponge. Quotes are the author’s own words.

More from @bg

All readings →