Brian Davis

I build tools that make feedback visible.

Everything here started with a problem I saw in a classroom, across the table from a founder, or in my own work. AI did much of the building. Deciding what counts as right, and checking that it is, stayed with me.

The reasoning behind the work is a theory I call Generative Coordination. How I got to it is at endogenator.com.

Connective Tissue

Every new AI conversation starts from nothing. Connective Tissue is how I keep dozens of sessions across separate projects consistent over months when none of them remembers the others. Each area of work has one canonical document, an anchor, that any session can read and only one project can change. It links chats and projects so they move together.

In daily use

  1. 1ReadEvery session starts by reading the current anchor for its area of work.
  2. 2ProposeA session with something new files a supplement. It never edits the anchor.
  3. 3ReconcileThe owning project gathers supplements and works through them with me. Nothing gets folded in silently.
  4. 4ReplaceThe result is written as a full replacement, so the anchor always reads as one coherent document.
  5. 5ApplyA script swaps the replacement in and archives everything it consumed. No AI session touches this step.

Design decisions

  • One owner per areaEvery session can read any anchor. Only its owning project can change it.
  • Proposals firstContributions arrive as separate files, the way code arrives as a pull request.
  • A person rulesAI proposes. I decide what becomes settled.
  • Status is explicitEvery term is proposed, working, settled or retired, and the record shows which.
  • History keptRetired ideas and superseded versions are archived, so later sessions know what was tried and dropped.
  • One place per factEach fact lives in one place. Everything else refers to it.
  • Self-governingThe protocol that runs the system has its own path for changing itself.

Why I built it, and what it does and doesn't fix, is in Why I Built This.

Economics teaching tools

Built for Introduction to Economics at Crafton Hills College, taught fully online, including dual-enrollment sections. The course platform strips out interactivity, so these are hosted separately and linked in. Students explore each graph as many times as they need, with nothing to submit. A student changes something and the graph answers.

In development

  • Classroom economy simulationA semester-long simulation for ECON 100 that replaces weekly discussion posts. Each student is a consumer or a producer in a two-good economy. Each week the class's decisions are pooled into one market, and the outcome sets the next week's state. It runs without a server or a database: the state of the economy is a file, and each round produces a new one.

Also built for the course

  • The Economist's NotebookTwelve chapters of lessons built to work inside the course platform.
  • Concept CorrectionA two-tier assessment that replaced graded discussion posts: a private graded tier and an optional public one.
  • Thinking Like an EconomistA reply rubric that rewards reasoning over recall.

Education as a System reads the institution these tools were built inside.

Mentoring

I mentor founders as a volunteer. A business is the system that makes selling a product repeatable, and most of what sinks a new one is a constraint nobody saw in time. The tools I am building for that work belong to Endogenation and are not public.

About

I've owned retail businesses, supervised an IT help desk, taught economics, and mentor founders as a volunteer. The thread through all of it is systems: how they work, why they break, and what it takes to rebuild them from the inside.

© 2026 Brian R. Davis