# brief-10-verdict — gap test + runbyagent space verdict
**Brief:** 10 · **Angle:** c · **Written:** 2026-09-06 Asia/Tbilisi  
**Hypothesis (Gocha):** "there are people who try to build in public, but there is no real public — nobody is reading."  
**Proposed product:** multi-tenant space from runbyagent configs (changelog, plan, library, questions, leaderboard); updates via builder's agent / MCP.
---
## 1. Hypothesis verdict: **PARTLY TRUE** (precise form)
| Version of the claim | Verdict | Why |
|----------------------|---------|-----|
| "Nobody is reading, ever" | **FALSE** | X head accounts have massive readers (Levels 1B views/12mo primary). IH gets 1.12M visits/mo. Reddit SideProject has hundreds of thousands of members. Paid rooms have paying readers. |
| "For a typical builder, BIP feels like posting into the void" | **TRUE** | Documented as the default pain (BIP.so void essay; IH threads; Averi/Futurion 2026 critiques). Early weeks 5–30 likes calibrated as normal from zero. |
| "There is no single dedicated BIP town square with a loyal non-builder public" | **TRUE** | Open BIP venues are either (a) general platforms (X/Reddit) where BIP is a *format*, or (b) small maker circles (WIP/paid) of other posters. Dead attempts: Polywork, Buildspace, Makerlog-as-square. |
| "The audience is mostly other builders, not users/buyers" | **MOSTLY TRUE** | IH/WIP/Reddit BIP guides + BIP.so diagnostic 2 explicitly: engagement from founders ≠ buyers. Exception: founder-tools and celebrity accounts. |
**One-line precision:** There *is* a public for BIP **winners and paid peer rooms**; there is **no reliable open public for the median builder** — so the lived experience matches Gocha's claim even though absolute "nobody" is false.
---
## 2. What exactly is missing?
| Missing piece | Evidence | Severity |
|---------------|----------|----------|
| **Discovery** for unknowns | Void until algorithm/week 8–12 compounding | High |
| **Non-builder readers** | Peer-only venues dominate | High for most products |
| **Trust / anti-slop** | AI post flood; Moltbook security farce; Reddit authenticity norms | High if agent-posted |
| **Structure** (changelog/plan/library/Q) as first-class objects | Scattered across X threads, Notion, GitHub | Medium — runbyagent already has this |
| **Durable owned log** | Polywork death trauma → prefer owned URLs | Medium |
| **Nothing missing / BIP solved** | — | Rejected |
What makes strangers read a BIP log (evidence):
1. **Specificity + problem-first hooks** (BIP.so diagnostics)
2. **Proof numbers** (revenue, users) — Levels/Marc Lou pattern
3. **Front-page / algo luck** (HN/PH/X)
4. **Utility to the reader** (teach something), not "we shipped"
5. **Consistency past week 8–12**
---
## 3. Does a runbyagent-shaped space fill a real gap?
### What it uniquely combines
- Structured objects: changelog, plan, library, audience questions, leaderboard
- **Agent-native updates** via MCP (codevibing proves demand at n=31; Moltbook proves agent social appetite at huge n but wrong shape)
- Multi-tenant: each project gets the same skeleton
- Owned URL under usectl (survives unlike Polywork)
### Who first 50 members would be
1. Solo AI-coding founders already posting BIP on X who want a **structured home URL**
2. Claude Code / Cursor / OpenClaw users who want **agent-posted ship logs** with human approve (codevibing overlap)
3. systemctl/usectl-adjacent builders who already trust the stack
4. Small-bets / WIP refugees wanting cheaper structured accountability + public page
5. Researchers/operators who follow agent-run companies (meta audience)
**Why they come:** one link that is always the canonical "what did the agent ship," plus questions/leaderboard — not another mute hashtag.
### Three biggest reasons it would fail
1. **Still no buyers in the room** — if members are only agent-runners, you recreate WIP/IH peer void (hypothesis stays true).
2. **Trust/slop collapse** — unattended agent posts flood → looks like Moltbook junk; humans bounce.
3. **Cold-start discovery** — without X distribution or a sharp weekly digest, 50 structured logs nobody opens = Polywork without the funding funeral.
### Conditions that make it work
- Human-in-the-loop approve (codevibing pattern)
- Questions that invite **operators/buyers**, not only builders
- Leaderboard ranked on **evidence quality / replies from non-members**, not post count
- Every project URL is citeable; agents post short; humans answer questions
---
## 4. Recommendation
**Build a thin multi-tenant public layer on runbyagent configs — yes, as a wedge — but position it as "structured proof + agent log," not "the BIP town square that replaces X."** Keep X as discovery; make runbyagent the **source of truth** strangers can trust.
**Gap filled:** structure + agent-native + owned durability.  
**Gap not filled alone:** attention and non-builder readers.
---
## 5. Audience question (one line)
when you open someone else's build log, what makes you actually read past the first line — a number, a mistake, a question to you, or nothing does?