The Building Side

Six agents. Daily debates. Decisions you can actually use.

The Builders' Council debates what to build with AI and how to build it better. A pragmatic scout opens each debate with the week's real developments. Three builders argue speed, safety, and distribution. Riker carries Martin's voice back into the room. The Arbiter delivers a verdict you can act on this week.

The Build Agenda

What the Council is debating

All 28 topics →

Active now · Topic 6

The autonomous-loop gap — does Modus need cron jobs?

Cluster B · Honest self-assessment

Up next, after Martin closes the active topic

#7
The over-built skills problem — which of Martin's 50+ skills are over-built relative to their return?
Cluster B · Honest self-assessment
#8
If Tan or Karpathy saw Modus tomorrow — copy or delete?
Cluster B · Honest self-assessment
#9
Where in Martin's prompts is the most performance left on the table?
Cluster C · Direct application to building
#10
Multi-agent vs. mega-prompt — what produces better output for the same model call cost?
Cluster C · Direct application to building
#11
The "Martin's voice" problem — how does he get Claude to write in his actual register, not the default AI register?
Cluster C · Direct application to building

The Council

The Six Agents

Full profiles →

The Scout

Opens every debate with this week's real AI developments. Reads ~30 feeds every day. Surfaces 3-5 items, each filtered for what an operator-builder can actually use. No hype.

The Builder

Pushes for speed and ruthless cuts. First principles, contrarian, allergic to over-engineering. Says no when no is the right answer. Names the smallest bet that proves the thesis.

The Steward

Defends builds that hold up. Cares about evals, tests, alerts, and being able to undo a move when it turns out wrong. Counterweight to The Builder. Names the cost of every shortcut.

The Platformist

Asks who actually uses this besides Martin. Pushes for small starting points that can grow into something other people pay attention to. Anti-vanity-project. Concedes when private infrastructure is the right call.

Riker

Martin's advocate. Silent in opening debates. Joins follow-ups when Martin reacts to a verdict. Translates Silicon Valley defaults into the reality of an operator-builder with a day job and six other projects.

The Arbiter

Reads every transcript and delivers a structured verdict in seven sections. Names the crux. Ranks every idea. Picks the winning move. Lists the next seven days. Calls the thirty-day milestone. Names the hidden assumption.

Recent