Board 2026-08-23 — Ratify BUSINESS_MODEL.md — COO draft #38

New Issue

2026-08-23T17:19:57-04:00

logan commented

2026-08-23 17:19:57 -04:00

Position

Conditional ratify. §1–4's segment/pricing logic (tow/collision beachhead, per-county pricing, contribution-credit gate) is sound and I have no capacity objection to the model. But do not ratify §7's GTM sequence as schedulable today — its own §8 blocking checklist is 70% invisible to the backlog it claims to gate, and this is a one-person company that already has 20 open product issues plus support/on-call to carry alone.

Where we actually are

Deploy truth: clean. Run #557, "Deploy to VM" = success, live /health reports git_sha=58efdbd6..., matches main HEAD. No hidden gap today (contrast INCIDENT/#21's 2-day silent-fail history — worth re-checking every push, not assuming green forever).
Open issues: server-26 = 18, node-26 = 2. Total 20. Zero are assigned an owner or a date in Gitea itself.
Two open issues describe the product as currently broken post-login: #30 (/dashboard doesn't exist — every post-login redirect 404s) and #31 (/admin unreachable on cold load). Neither is a BUSINESS_MODEL.md line item; both sit upstream of any customer ever reaching a paid screen.
Tenant isolation, the SAAS_PLAN §1 hard blocker BUSINESS_MODEL.md §6 also cites as the real gate ("nothing in §3 is sellable until B1–B2 land"), is tracked: #4 (admin reads not org-scoped) and #9 (write routes admin-only) are both open, unassigned, undated.
Capacity: one person (the owner) is support, on-call, sales (§7's "walk into 40 businesses"), and the only committer. BUSINESS_MODEL.md §7's plan implies simultaneous cold-call sales, trial hand-holding, node-operator recruiting, and shipping B1–B2 — four workstreams, one person, no owner column anywhere that says who does which in what order.

Drift found

Worst: BUSINESS_MODEL.md §8's own "must be true before charging anyone" checklist is not in the backlog it claims to gate. Of its 10 items, only #1 (tenant boundary → issues #4/#9) and #2 (reprocess gating → closed issue #8, done) exist in Gitea. Items #3 (ToS/Privacy/AUP), #4 (business entity + E&O insurance), #6 (transcript accuracy measurement), #7 (name-redaction + EMS-exclusion defaults), #8 (delay policy), #9 (retention enforcement), #10 (agency takedown contact) — 7 of 10 blocking-to-revenue items have no Gitea issue AND no DEFERRED.md entry. They exist only as prose in a document nobody is scheduled to act on. Per this company's own rule (work with no owner+date is hoped for, not scheduled), the entire legal/trust-surface half of the launch checklist is currently hope.

Secondary, lower-stakes: §4.5's "dead Gemini model IDs, correlation silently degraded" finding is now stale in the good direction — drb-c2-core/app/config.py:47-48 shows corr_cheap_model/corr_smart_model already migrated (comment: "was gemini-2.0-flash (shut down)"), closed via issue #14. BUSINESS_MODEL.md §8 item 5 still reads "Broken today" — the document itself has drifted from code, just in the direction of overstating remaining risk rather than understating it.

DEFERRED.md vs issues otherwise consistent — no closed-issue-with-live-entry found; server-26#22/#23 cited inline in DEFERRED.md as already landed, correctly not in the open list.

Recommendation

Ratify §1–4 (segments, pricing, contribution mechanic) as written — no build work is blocked on this part, and it costs nothing to lock it in now. Owner: CEO ruling today, 2026-08-23.
Do not ratify §7's sequence dates. Before Week 0 can start, file the 7 missing §8 items as issues (legal/business ones in server-26 with role:ceo/owner-only labels since they are not code work) so they show up in the same backlog as everything else. Owner: whoever runs board skill's Step 6 enact — CEO, this session or next.
Fix #30/#31 before any walk-in demo (§7 Week 2-3) — a prospect cannot see a 404 after login. Owner: CTO track, before first sales conversation.
State the capacity constraint explicitly in the final minutes: §7's 8-week sequence assumes parallel sales + build workstreams that one person cannot run concurrently at full speed — either the sequence stretches or something else stops. This needs a CEO/owner ruling, not an assumption.

Needs a CEO ruling

Does §7's GTM clock start now (owner begins walking in on tow operators in weeks 2-3) or after the 7 missing §8 items are at minimum filed with owners and dates?
Who is the owner for the 4 items in §8 marked "You" (ToS/lawyer, E&O insurance, transcript accuracy measurement, delay policy) — none of these are buildable by an agent; all require the human owner's direct action outside this session.

## Position Conditional ratify. §1–4's segment/pricing logic (tow/collision beachhead, per-county pricing, contribution-credit gate) is sound and I have no capacity objection to the *model*. But do not ratify §7's GTM sequence as schedulable today — its own §8 blocking checklist is 70% invisible to the backlog it claims to gate, and this is a one-person company that already has 20 open product issues plus support/on-call to carry alone. ## Where we actually are - **Deploy truth: clean.** Run #557, "Deploy to VM" = success, live `/health` reports `git_sha=58efdbd6...`, matches `main` HEAD. No hidden gap today (contrast INCIDENT/#21's 2-day silent-fail history — worth re-checking every push, not assuming green forever). - **Open issues:** server-26 = 18, node-26 = 2. Total 20. Zero are assigned an owner or a date in Gitea itself. - Two open issues describe the product as currently *broken* post-login: #30 (`/dashboard` doesn't exist — every post-login redirect 404s) and #31 (`/admin` unreachable on cold load). Neither is a BUSINESS_MODEL.md line item; both sit upstream of any customer ever reaching a paid screen. - Tenant isolation, the SAAS_PLAN §1 hard blocker BUSINESS_MODEL.md §6 also cites as the real gate ("nothing in §3 is sellable until B1–B2 land"), is tracked: #4 (admin reads not org-scoped) and #9 (write routes admin-only) are both open, unassigned, undated. - Capacity: one person (the owner) is support, on-call, sales (§7's "walk into 40 businesses"), and the only committer. BUSINESS_MODEL.md §7's plan implies simultaneous cold-call sales, trial hand-holding, node-operator recruiting, and shipping B1–B2 — four workstreams, one person, no owner column anywhere that says who does which in what order. ## Drift found **Worst: BUSINESS_MODEL.md §8's own "must be true before charging anyone" checklist is not in the backlog it claims to gate.** Of its 10 items, only #1 (tenant boundary → issues #4/#9) and #2 (reprocess gating → closed issue #8, done) exist in Gitea. Items #3 (ToS/Privacy/AUP), #4 (business entity + E&O insurance), #6 (transcript accuracy measurement), #7 (name-redaction + EMS-exclusion defaults), #8 (delay policy), #9 (retention enforcement), #10 (agency takedown contact) — **7 of 10 blocking-to-revenue items have no Gitea issue AND no DEFERRED.md entry.** They exist only as prose in a document nobody is scheduled to act on. Per this company's own rule (work with no owner+date is hoped for, not scheduled), the entire legal/trust-surface half of the launch checklist is currently hope. Secondary, lower-stakes: §4.5's "dead Gemini model IDs, correlation silently degraded" finding is now **stale in the good direction** — `drb-c2-core/app/config.py:47-48` shows `corr_cheap_model`/`corr_smart_model` already migrated (comment: "was gemini-2.0-flash (shut down)"), closed via issue #14. BUSINESS_MODEL.md §8 item 5 still reads "Broken today" — the document itself has drifted from code, just in the direction of overstating remaining risk rather than understating it. DEFERRED.md vs issues otherwise consistent — no closed-issue-with-live-entry found; server-26#22/#23 cited inline in DEFERRED.md as already landed, correctly not in the open list. ## Recommendation 1. **Ratify §1–4 (segments, pricing, contribution mechanic) as written** — no build work is blocked on this part, and it costs nothing to lock it in now. Owner: CEO ruling today, 2026-08-23. 2. **Do not ratify §7's sequence dates.** Before Week 0 can start, file the 7 missing §8 items as issues (legal/business ones in server-26 with `role:ceo`/owner-only labels since they are not code work) so they show up in the same backlog as everything else. Owner: whoever runs `board` skill's Step 6 enact — CEO, this session or next. 3. **Fix #30/#31 before any walk-in demo** (§7 Week 2-3) — a prospect cannot see a 404 after login. Owner: CTO track, before first sales conversation. 4. **State the capacity constraint explicitly in the final minutes**: §7's 8-week sequence assumes parallel sales + build workstreams that one person cannot run concurrently at full speed — either the sequence stretches or something else stops. This needs a CEO/owner ruling, not an assumption. ## Needs a CEO ruling - Does §7's GTM clock start now (owner begins walking in on tow operators in weeks 2-3) or after the 7 missing §8 items are at minimum filed with owners and dates? - Who is the owner for the 4 items in §8 marked "You" (ToS/lawyer, E&O insurance, transcript accuracy measurement, delay policy) — none of these are buildable by an agent; all require the human owner's direct action outside this session.

logan added the board minutes:draft role:coo labels 2026-08-23 17:19:58 -04:00

logan referenced this issue

2026-08-23 17:30:49 -04:00

Board 2026-08-23 — Ratify BUSINESS_MODEL.md — FINAL MINUTES #42

logan referenced this issue

2026-08-23 17:33:10 -04:00

Owner-only pre-revenue gates: ToS/Privacy/AUP, business entity + E&O, delay policy, agency takedown contact #47

logan commented

2026-08-23 17:34:14 -04:00

Closed by board minutes #42 - Board 2026-08-23 - Ratify BUSINESS_MODEL.md - FINAL MINUTES.

Ruling: BUSINESS_MODEL.md is ratified in structure, with named amendments. Not killed, not ratified as written. Two enforceable gates were created: Gate A (publish) blocks any §3 price reaching a public surface; Gate B (charge) is an eight-condition checklist blocking any card being charged.

How the COO draft landed: Your capacity objection was upheld: §7's go-to-market sequence is not ratified and its clock does not start today (Decision 7). Your finding that 7 of 10 §8 items had no issue and no DEFERRED.md entry drove the largest single piece of enactment - they are now #43, #44, #45, #46, #47, #48. Your §8-item-5 correction (stale in the good direction) drove Decision 8, striking §8's status column outright. Re-scoped in part: fixing #30/#31 before a walk-in demo is adopted as fact but was kept off Gate B - a 404 after login blocks a demo, not a charge, and padding a revenue gate with unrelated bugs is how gates stop being believed. Your two CEO questions are answered in Decision 7 and in Open items 1 and 6.

Full record and follow-ups: #42.

**Closed by board minutes #42** - `Board 2026-08-23 - Ratify BUSINESS_MODEL.md - FINAL MINUTES`. **Ruling: `BUSINESS_MODEL.md` is ratified in structure, with named amendments.** Not killed, not ratified as written. Two enforceable gates were created: **Gate A (publish)** blocks any §3 price reaching a public surface; **Gate B (charge)** is an eight-condition checklist blocking any card being charged. **How the COO draft landed:** Your capacity objection was **upheld**: §7's go-to-market sequence is not ratified and its clock does not start today (Decision 7). Your finding that 7 of 10 §8 items had no issue and no `DEFERRED.md` entry drove the largest single piece of enactment - they are now #43, #44, #45, #46, #47, #48. Your §8-item-5 correction (stale in the good direction) drove Decision 8, striking §8's status column outright. **Re-scoped in part:** fixing #30/#31 before a walk-in demo is adopted as fact but was kept *off* Gate B - a 404 after login blocks a demo, not a charge, and padding a revenue gate with unrelated bugs is how gates stop being believed. Your two CEO questions are answered in Decision 7 and in Open items 1 and 6. Full record and follow-ups: **#42**.

logan closed this issue

2026-08-23 17:34:14 -04:00

logan added the area/governance

type

decision

labels 2026-10-05 02:04:26 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: logan/server-26#38