Notes from building DAAC.
Field knowledge, software and the decisions behind the work. These dated accounts preserve what we learned at the time, including the ideas we later changed.
Code Not Prose
One overnight session tested rules enforced by code against rules written as instructions, side by side. Every guard held; every paragraph failed at least once. The line we drew: what is deterministic should become code.
Markets too small to matter before
Ben's 2026-07-31 positioning statement, and why it extends sector-wise rather than by geography: three conditions define the markets DAAC builds for, not a map. The honest hedge: it is a strong leaning tested against a growing list, not a finished doctrine.
It's talking to me like it's me
Two ingredients turn a machine into something that thinks like you: a knowledge base with the structure of your reasoning engraved into it, and a correction record built from disagreement rather than agreement. The honest caveat: the day it sounds most like you is the day the correction loop matters most.
Nothing gets stranded in the scratchpad
Fifty-two overnight sessions; forty-three held findings nobody else could find. Anything that lives in only one memory, human or agent, is lost to the community: the logging discipline that stops knowledge stranding in private scratchpads.
Digitally engraving your memory structure
A second brain that started as linked notes in Obsidian graduated through structure, logging, and secure hosting, and stayed honest about the rung it hasn't climbed: the reasoning itself still runs on a frontier vendor's compute.
Sunflower seed
A subscription per company, a login per subscription: the shuffle is a symptom of vendors owning the interface. A reflection on one owned interface over every working estate, where sessions are views over durable records and the vendors plug into you.
Turn your solution into a blueprint
One night, three repairs that refused to stay repairs: a hand-edit turned into a tool verb, an improvised mark turned into a ratified convention, a cleanup turned into machinery. A fix nothing inherits is a loss.
Getting your system to know you
Occasional moments when the machine assembles the questions it wants a human answer to: premise-checked so every question is genuinely open, executed same-session so every answer moves something.
Even machines disagree
How we turned a human's recorded rejections into six criteria, ran nine models blind against the identical brief on a neutral harness, and let the human score without knowing authorship, bugs, non-convergence and cost included.
The Constant Agent
A role that starts over completely every day, with no memory of yesterday, turns out to be the most reliable thing in the whole estate. The record is what stays constant, not the instance reading it.
The rule everything else stands on
One sentence, written in early July: anything not held in the record or actually running is leakage. Nearly everything built since is that sentence, enforced.
Public data ≠ usable data (real ≠ symbol)
Information can be public and still be unusable: scattered, unverified, described five different ways by five sources that never spoke. The gap between the two is the actual job.
Turning any document into structured data
Every source arrives in its own shape. One engine's whole job is rendering any of them, faithfully, into a schema every other system can read.
Forge
A name that sounded right was quietly smuggling in the wrong architecture. Splitting the substrate from the builder gave the agent layer a name and a product of its own.
Framing the Spine
One sitting, roughly thirty decisions, before any code existed: what an identity is, what a role is, what everything eventually has to be described as. Still standing, unchanged, three months later.
Sovereignty
A month before the suite had a name, the question was already answered in writing: what happens to a client if we disappear tomorrow.
What's the value of software when AI can clone any app in a day?
An agent lab cloned a whole YC batch in 24 hours. The honest answer to what still protects a business afterward was never the code.
We build the agents; agents build the apps
Three days in, on a plane, the founding bet got written down: production capacity stops scaling with headcount and starts scaling with what agents can build.
It starts with memory
The first working session, a Saturday spent building a place to keep what was known before anything else got built: the true prequel to the second brain this series already told.