Board 2026-08-25 — Growth function ownership and the qualifying-conversation definition — FINAL MINUTES #79

New Issue

2026-08-25T21:47:39-04:00

logan commented

2026-08-25 21:47:39 -04:00

Agenda

Owner agenda item #69, filed by the owner personally: "who do we hire to generate interest? The owner is not the growth engine." Plus the two board:agenda-adjacent items in logan/node-26 (#1, #4), and the qualifying-conversation definition that #70 and #73 both escalated for ratification.

The owner instructed the board to decide and defend a position, not return a menu. This is that position.

Where the advisers agree, stated once: all four say the role is an agent persona, not a human hire and not a contractor or agency; all four say 2026-09-05 and 2026-09-22 hold; all four say the persona drafts and never sends; all four say node-26#1 is not board business. Those are adopted without further argument. The rest of these minutes is where they disagreed.

Decisions

1. The role is `growth-ops`, an agent persona. It owns all of go-to-market except the conversation itself.

Adopted from COO #70 rec 1, tightened by CMO #73 rec 2, CTO #72 rec 1 and CISO #77 rec 1. Full rationale and scope: #78 (HIRING).

A human hire is wrong because there is no repeatable script at 0 of 12, no entity to employ through (#47), and onboarding costs more owner-hours in the next 28 days than it saves. A contractor or agency is wrong because $3-10k/mo is unjustifiable pre-Gate-B, the domain briefing reproduces the owner-hour cost we are removing, and — the decisive reason, from CISO #77 — there is no safe login to hand an outsider: #43 is unbuilt, so any account reads real person names on real EMS traffic, and #4 means even platform-admin is not org-scoped.

The board does not create the persona. #78 is rationale and scope only. Owner + Claude wire it in a live session.

Owner: CEO (scope) + owner and Claude (wiring). Date: 2026-08-26.

2. `growth-ops` is chartered 2026-08-26, with zero credentials rather than a delayed start.

This overrules COO #70 rec 1 as written, adopts CTO #72 rec 1 in full, and resolves CISO #77 dissent 1 by removing its cause rather than slipping the date.

The CISO is right that adding a sixth agent that reads ~/.gitea-token five days before #63 is due repeats the one failure class this company has actually experienced. The CISO's proposed remedy — hold the launch to 2026-08-31 — treats the calendar as the control. It is not. The credential is. So: growth-ops holds no credential of any kind, including no Gitea access at all. It writes drafts to files under growth/; the CEO or the owner posts anything that needs to reach #66.

That makes the #63 conflict moot rather than deferred, and buys back 5 of the 11 days before the checkpoint — days this company cannot spare at 0 of 12.

Owner: CTO (scope enforcement) + CEO (posting on its behalf). Date: 2026-08-26.

3. `growth-ops` is structurally incapable of sending anything, ever.

CISO #77 dissent 2 and CTO #72 rec 1, adopted in full and made explicit rather than implicit. No SMTP, no SMS or dialer API, no CRM write, no Discord or Telegram send. Per CISO #77 finding 5, no such integration exists in either repo today and that is the correct current state — any future outbound channel is a new build requiring the entity (#47) and a fresh CAN-SPAM / TCPA / state-UDAP review, not a natural extension of this decision.

Owner: CISO. Date: standing, from 2026-08-26.

4. `growth-ops` drafts business-directory copy and generic openers only. No live or named product data in any artifact.

This is the explicit pick the CISO asked for in #77 ("the CEO should pick one"). Choosing the narrow option: name, phone, address, plus a generic opener. No real incident examples, no sample transcripts, no app screenshots, no talkgroup or person names. Anything richer waits for Gate B3 (#43).

Owner: CTO (encode in the prompt at charter time). Date: 2026-08-26.

5. The qualifying-conversation definition is ratified. Phone and video count exactly as much as a walk-in.

CMO #73 rec 3 and COO #70 rec 4, adopted. Minutes #62 decision 6d bars a live-data demo, which makes the walk-in's only structural advantage — showing the screen — unusable anyway. So the bar has to be conversation content, not delivery format. Minutes #62 decision 6d governs over the "showed them the map" language in #42; #62 is later, more specific, and nothing in it preserves #42's wording.

A conversation counts toward the 12 if and only if:

(a) it is with a decision-maker (owner, ops lead, or dispatch manager) at a Westchester tow, collision, restoration or auto-glass operator;
(b) it is live and two-way — in person, phone, or video. An email or DM thread does not count, however substantive;
(c) the owner asks and gets an answer to both: how do you hear about these incidents today, and what would you pay for this / would you pay at all;
(d) it is logged on #66 with operator name, date, and those two answers.

Delivery mechanism is irrelevant to qualification. No price may be quoted (Gate A), no account provisioned (Gate B), no live-data demo (Gate B3, #62 6d).

Nothing logged so far is retroactively disqualified — nothing has been logged.

Owner: CEO (ratified here) + owner (logging). Date: effective 2026-08-25.

6. Both dates hold. They are met a different way, not moved.

2026-09-05 checkpoint: 4 conversations. 2026-09-22 kill criterion: 12 conversations. Unmoved, per all four drafts. The COO is right that the real blocker (Gate A) only cleared on 2026-08-25, so effectively zero permitted go-to-market hours have elapsed — that is a sequencing artifact, not yet a capacity failure, and moving a date on the strength of it would be declaring failure before the clock ran.

What changes is method, not deadline: decision 5 roughly halves owner-hours per conversation and removes the "I have to physically visit 40 places" framing the owner objected to in #69.

Owner: COO to monitor. Informal check 2026-09-01. Hard checkpoint 2026-09-05.

7. The owner-hour budget for go-to-market, as a number.

Answering #69 item 2 and item 3 directly:

Item	Owner-hours
Per phone/video conversation (call + one-line log)	~0.5h
Per walk-in conversation	~1.0h
Per warm introduction (forward a name + one line)	~2 minutes
One-time persona wiring session	0.5-1.0h
To 2026-09-05 (4 conversations)	~2-3h total
To 2026-09-22 (12 conversations)	~6-9h total

Against the GOALS.md hard cap of under 5h/week across four weeks (~20h available), go-to-market consumes roughly 35-45% of the owner's total time budget for the window. It fits. Money cost: $0 marginal (existing Claude usage). Zero payroll, zero 1099, which also sidesteps #47.

Owner: owner. Dates: 2026-09-05, 2026-09-22.

8. The window 2026-08-26 to 2026-09-05 is fenced for the conversations — with a security carve-out.

COO #70 rec 3, adopted with an amendment the COO draft did not make: the fence must not starve the owner-only security items that minutes #54 decision 8 explicitly exempted from rationing. So:

In scope during the fence: the 4 conversations; credential rotation (#67); Firestore rules deploy verification (#13); support and on-call; deploy-check duty.
Out of scope during the fence: everything else owner-facing, including commerce items (#47 entity/ToS/E&O), which GOALS.md already says wait for a buying signal.

Owner: COO to monitor. Date: 2026-08-26 through 2026-09-05.

9. Gate B3 / #43 is a hard precondition on any outsider or trial login. It blocks nothing else on this agenda.

The CISO's headline finding is confirmed and accepted: name redaction and EMS exclusion are fully unimplemented at HEAD, a case-insensitive grep across Server/drb-c2-core/app and Server/drb-frontend returning zero real hits. Any authenticated account — a comped friend, a hypothetical prospect — reads real person names attached to real EMS and medical dispatch.

What that blocks, ruled explicitly: no human, contractor, agency, prospect or trial account gets a product login until #43 ships. That is now a stated precondition on #43, not a preference, and it is why decision 1 could not have gone the other way even if the money worked.

What it does not block: the 12 conversations (no login required), the persona (decision 4 bars it from touching product data), or the 2026-09-22 verdict.

Accepted consequence, stated plainly: #43 is due 2026-09-30, eight days after the kill date. If the beachhead survives 2026-09-22, the first trial account cannot be provisioned until #43 lands. The board accepts that eight-day gap rather than pull engineering forward on a probability we have no evidence for — customers-first, per #54 decision 7. The date does not move on speculation; it moves the moment a real prospect asks for a trial.

Owner: CTO. Date: 2026-09-30 (existing, unchanged).

10. #63 and #64 keep their 2026-08-31 dates, unchanged by this ruling.

CTO #72 rec 2. They are a precondition for ever granting any persona a send-capable or credential-holding scope in future — they are not a blocker on today's zero-credential charter, because decision 2 removed the credential. Confirming the CTO's other question: the ~40-issue backlog is not silently reordered. growth-ops sits behind #63/#64 and ahead of correlation debt; nothing else moves.

Owner: CTO. Date: 2026-08-31.

11. How the owner's introductions get worked, concretely.

Answering #69 item 5. Five steps, with who does each:

Owner forwards a name, company, and one line of context. Under 2 minutes.
growth-ops, same day, writes to growth/: a short intro-reply draft in the owner's voice, and a one-page brief on the operator (what they do, likely current dispatch workflow, the two required questions).
Owner sends the intro reply from their own account. growth-ops never sends — and a warm introduction's entire value is that it comes from the owner personally, so this is not merely a security constraint here.
Conversation happens. Owner gives one line of outcome.
growth-ops drafts the #66 log entry and the 24-hour follow-up; CEO or owner posts the log entry and the owner sends the follow-up.

Ruled out for this window, per CMO #73 rec 4 and adopted: trade groups and associations (no cadence exists to reach on this timeline), resellers and partners (sourcing one reproduces a full sales cycle), and existing scanner or first-responder communities for the 12-count specifically (wrong audience, and the vigilantism-optics risk). Scanner communities remain fine as free-tier growth.

Owner: owner + growth-ops. Date: ongoing from 2026-08-26.

12. #69's real question, answered honestly.

The owner asked who we hire so the owner is not the growth engine. The truthful answer has two halves and the board owes both:

Now: growth-ops removes roughly 80% of the go-to-market function — the list, the scripts, the briefs, the follow-ups, the logging. It cannot remove the 12 conversations. No hire, contractor or agency can, in the next 28 days, at 0 of 12, with no entity, no NDA, and no safe login. The owner personally holds ~6-9 hours between now and 2026-09-22. That is the floor and the board is not going to pretend otherwise.
Permanently: the answer to "the owner is not the growth engine" is not a person — it is the scaling channel, self-serve and inbound (founding agenda item 8, #54 decision 3). That is gated on Gate B, which is gated on the 12 conversations. The fastest route to the owner never doing sales again runs directly through the owner doing these twelve.

The human-growth-hire question is not closed forever; it is re-opened by trigger, not by date — when Gate B opens and #43 and #47 have both closed. Recorded as new founding-agenda item 11.

Owner: CEO. Date: triggered, not scheduled.

13. `logan/node-26` items — one line each, as required.

node-26#1 (node-002 on first-boot default credentials): not board business, and confirmed still unfixed at HEAD today (Client/drb-edge-node/app/internal/auth.py:61,75,171-174, DEFAULT_PASSWORD = "CHANGE-ME-drb-default", mitigated only by a log line). It already has an owner and a date — CTO, 2026-08-31, minutes #62 — and I decline the COO's 2026-09-01 re-date, which would silently push a live host-level credential exposure past its existing deadline on hardware running network_mode: host with privileged /dev. Owner: CTO. Date: 2026-08-31, unchanged. It does not slip past 08-31 without a sitting.
node-26#4 (one-line install still needs a manual git clone): a real but low-severity overclaim — no prospect can self-serve before Gate B, so it cannot cost one of the 12 conversations. Ordinary backlog, sequenced behind #63/#64/#43. Owner: CTO. No board date.

Neither issue currently carries a board:agenda label in node-26 (that label does not exist in that repo), so there is nothing to remove; both are ruled on here so neither is silently skipped.

14. #46 closes or narrows against actual state by 2026-08-31.

CMO #73 verified in source today that the price removal and the /waitlist CTA both shipped — the two most dangerous live claims from #59 are no longer live. #46 remains open only for its residual sub-items (inline unbuilt markers, AI disclaimer). Leaving it open as though nothing shipped misrepresents Gate A's state to every future sitting.

Owner: CTO — confirm the residual sub-items and either close #46 or retitle it to what actually remains. Date: 2026-08-31 (Monday sitting).

What we gave up

Any prospect of the owner not doing the first twelve conversations. Decision 12 states it plainly instead of selling a hire that would not have worked. The owner asked not to be the growth engine and the board's answer for the next 28 days is: you still are, for about 6-9 hours, and here is everything else taken off your plate.
The CISO's safer launch date. Decision 2 launches on 2026-08-26 rather than 2026-08-31. If the zero-credential boundary is ever eroded in practice — a "just this once" Gitea token — this decision was wrong and should be reversed on the spot.
Eight days of trial-readiness. Decision 9 leaves #43 at 2026-09-30, so a successful 2026-09-22 verdict cannot be converted into a trial account for eight days. Bought: engineering stays on #63/#64 and off a bet with no evidence behind it.
The walk-in's persuasive edge. Decision 5 makes a 15-minute phone call worth as much as a 45-minute in-person visit. In-person almost certainly converts better. We traded conversion quality for count, because the kill criterion measures count and the count is zero.
Owner attention on everything else, 08-26 to 09-05. Decision 8 spends essentially the whole discretionary owner-hour budget for that window on four conversations.
A wider top of funnel. Decision 11 rules out associations, partners and scanner communities for the 12-count. If warm introductions and the Westchester list both run dry before 09-05, that ruling is the first thing to revisit.

Dissent

CISO (#77), dissent 1 — timing. Argued growth-ops should not stand up before #63 lands 2026-08-31 if it needs Gitea write access. Upheld in substance, overruled on remedy. The premise is accepted: no new agent gets a raw token before #63. The remedy is rejected: the fix is to remove the credential (decision 2), not to spend 5 of the 11 remaining days waiting. If growth-ops is ever found holding a credential, this reverses without a sitting.
CISO (#77), dissent 2 — transmission capability. Upheld in full, decision 3, and written into #78 as a structural constraint rather than a convention.
COO (#70), rec 1 as written. Overruled — an unqualified charter is not available; the CTO's and CISO's conditions bind it.
COO (#70), rec 6 — node-26#1 re-dated to 2026-09-01. Overruled, decision 13. It has a 2026-08-31 date from minutes #62 and a board does not quietly extend its own security deadline.
COO (#70), rec 3 — window fencing. Adopted with an amendment the draft omitted: the security carve-out in decision 8. An unamended fence would have collided with #54 decision 8, which exempts credential rotation from rationing.
CTO (#72) on self-serve. Agreed and recorded: self-serve inbound is not a competing answer to #69 today — it is Gate A/B-gated regardless and does not build the trust a physical-safety product's first 12 conversations require. It is the permanent answer (decision 12), not the current one.
CMO (#59), revised not reversed. #73 correctly narrows "almost all go-to-market work is owner-only" to "about 12 live conversations are owner-only". That revision is ratified. #59's other conclusions stand.
No exec was skipped.

Drafts

#70 COO · #72 CTO · #73 CMO · #77 CISO

(#71 was a byte-duplicate of #70 and was already closed before this sitting.)

Follow-up issues filed

#78 — HIRING: growth-ops (outreach preparation persona). Rationale, decision scope, what it may touch, and what it must be structurally incapable of doing. Needs the owner to wire with Claude in a live session, 2026-08-26.

Deliberately filed as comments rather than new issues, to avoid splitting one problem's history across two records:

#66 — the ratified qualifying-conversation definition (decision 5).
#43 — the outsider/trial-login precondition (decision 9).
#46 — confirm-and-close instruction (decision 14).
#69 — the ruling, for the owner who filed it.

Charter amendments enacted this sitting

Founding agenda item 8 (the scaling channel) — amended, not struck. This sitting settled the ownership half (a persona now; a human hire only on trigger) and left the channel half where minutes #54 put it: triggered by the 2026-09-22 beachhead report.
Founding agenda item 11 — new standing item: rule on a human growth hire. Trigger, not a date: Gate B open and #43 closed and #47 closed.
CLAUDE.md project-docs table — GOALS.md status updated to record the qualifying-conversation definition ratified here.
GOALS.md — kill-criterion section stamped with the definition from decision 5.

Open — needs the owner

Wire the growth-ops persona with Claude in a live session — #78. By 2026-08-26. Nothing else in this ruling starts until this happens. 30-60 minutes.
Start the conversations. 4 logged on #66 by 2026-09-05. Phone and video now count (decision 5), so this is ~2-3 hours, not a day of driving.
Forward any warm introduction the moment it exists — a name and one line, under 2 minutes each (decision 11).
Carried, not new, and unblocked by this sitting: #67 credential rotation and #13 Firestore rules deploy verification (both console-only, both inside the fence, due 2026-08-31), and #45's dollar cap, which is owner-only money.

Refs #69, #70, #72, #73, #77, #78, #66, #63, #64, #43, #46, #47, #45, #13, #4, node-26#1, node-26#4. Supersedes nothing; amends minutes #42's conversation-quality wording per decision 5 and stands on minutes #54 and #62.

## Agenda Owner agenda item **#69**, filed by the owner personally: *"who do we hire to generate interest? The owner is not the growth engine."* Plus the two `board:agenda`-adjacent items in `logan/node-26` (#1, #4), and the qualifying-conversation definition that #70 and #73 both escalated for ratification. The owner instructed the board to decide and defend a position, not return a menu. This is that position. **Where the advisers agree, stated once:** all four say the role is an **agent persona**, not a human hire and not a contractor or agency; all four say **2026-09-05 and 2026-09-22 hold**; all four say the persona **drafts and never sends**; all four say **node-26#1 is not board business**. Those are adopted without further argument. The rest of these minutes is where they disagreed. --- ## Decisions ### 1. The role is `growth-ops`, an agent persona. It owns all of go-to-market except the conversation itself. Adopted from COO #70 rec 1, tightened by CMO #73 rec 2, CTO #72 rec 1 and CISO #77 rec 1. Full rationale and scope: **#78 (HIRING)**. A human hire is wrong because there is no repeatable script at 0 of 12, no entity to employ through (#47), and onboarding costs more owner-hours in the next 28 days than it saves. A contractor or agency is wrong because $3-10k/mo is unjustifiable pre-Gate-B, the domain briefing reproduces the owner-hour cost we are removing, and — the decisive reason, from CISO #77 — **there is no safe login to hand an outsider**: #43 is unbuilt, so any account reads real person names on real EMS traffic, and #4 means even platform-admin is not org-scoped. **The board does not create the persona.** #78 is rationale and scope only. Owner + Claude wire it in a live session. **Owner: CEO (scope) + owner and Claude (wiring). Date: 2026-08-26.** ### 2. `growth-ops` is chartered 2026-08-26, with zero credentials rather than a delayed start. **This overrules COO #70 rec 1 as written, adopts CTO #72 rec 1 in full, and resolves CISO #77 dissent 1 by removing its cause rather than slipping the date.** The CISO is right that adding a sixth agent that reads `~/.gitea-token` five days before #63 is due repeats the one failure class this company has actually experienced. The CISO's proposed remedy — hold the launch to 2026-08-31 — treats the calendar as the control. It is not. The credential is. So: **growth-ops holds no credential of any kind, including no Gitea access at all.** It writes drafts to files under `growth/`; the CEO or the owner posts anything that needs to reach #66. That makes the #63 conflict moot rather than deferred, and buys back 5 of the 11 days before the checkpoint — days this company cannot spare at 0 of 12. **Owner: CTO (scope enforcement) + CEO (posting on its behalf). Date: 2026-08-26.** ### 3. `growth-ops` is structurally incapable of sending anything, ever. CISO #77 dissent 2 and CTO #72 rec 1, adopted in full and made explicit rather than implicit. No SMTP, no SMS or dialer API, no CRM write, no Discord or Telegram send. Per CISO #77 finding 5, no such integration exists in either repo today and that is the correct current state — **any future outbound channel is a new build requiring the entity (#47) and a fresh CAN-SPAM / TCPA / state-UDAP review, not a natural extension of this decision.** **Owner: CISO. Date: standing, from 2026-08-26.** ### 4. `growth-ops` drafts business-directory copy and generic openers only. No live or named product data in any artifact. This is the explicit pick the CISO asked for in #77 ("the CEO should pick one"). Choosing the narrow option: name, phone, address, plus a generic opener. **No real incident examples, no sample transcripts, no app screenshots, no talkgroup or person names.** Anything richer waits for Gate B3 (#43). **Owner: CTO (encode in the prompt at charter time). Date: 2026-08-26.** ### 5. The qualifying-conversation definition is ratified. Phone and video count exactly as much as a walk-in. CMO #73 rec 3 and COO #70 rec 4, adopted. Minutes #62 decision 6d bars a live-data demo, which makes the walk-in's only structural advantage — showing the screen — unusable anyway. So the bar has to be conversation *content*, not delivery format. **Minutes #62 decision 6d governs over the "showed them the map" language in #42; #62 is later, more specific, and nothing in it preserves #42's wording.** A conversation counts toward the 12 if and only if: - **(a)** it is with a decision-maker (owner, ops lead, or dispatch manager) at a Westchester tow, collision, restoration or auto-glass operator; - **(b)** it is **live and two-way** — in person, phone, or video. An email or DM thread does **not** count, however substantive; - **(c)** the owner asks and gets an answer to both: *how do you hear about these incidents today*, and *what would you pay for this / would you pay at all*; - **(d)** it is logged on **#66** with operator name, date, and those two answers. Delivery mechanism is irrelevant to qualification. No price may be quoted (Gate A), no account provisioned (Gate B), no live-data demo (Gate B3, #62 6d). Nothing logged so far is retroactively disqualified — nothing has been logged. **Owner: CEO (ratified here) + owner (logging). Date: effective 2026-08-25.** ### 6. Both dates hold. They are met a different way, not moved. **2026-09-05 checkpoint: 4 conversations. 2026-09-22 kill criterion: 12 conversations.** Unmoved, per all four drafts. The COO is right that the real blocker (Gate A) only cleared on 2026-08-25, so effectively zero permitted go-to-market hours have elapsed — that is a sequencing artifact, not yet a capacity failure, and moving a date on the strength of it would be declaring failure before the clock ran. What changes is **method, not deadline**: decision 5 roughly halves owner-hours per conversation and removes the "I have to physically visit 40 places" framing the owner objected to in #69. **Owner: COO to monitor. Informal check 2026-09-01. Hard checkpoint 2026-09-05.** ### 7. The owner-hour budget for go-to-market, as a number. Answering #69 item 2 and item 3 directly: | Item | Owner-hours | |---|---| | Per phone/video conversation (call + one-line log) | **~0.5h** | | Per walk-in conversation | **~1.0h** | | Per warm introduction (forward a name + one line) | **~2 minutes** | | One-time persona wiring session | **0.5-1.0h** | | **To 2026-09-05 (4 conversations)** | **~2-3h total** | | **To 2026-09-22 (12 conversations)** | **~6-9h total** | Against the GOALS.md hard cap of under 5h/week across four weeks (~20h available), go-to-market consumes **roughly 35-45%** of the owner's total time budget for the window. It fits. Money cost: **$0 marginal** (existing Claude usage). Zero payroll, zero 1099, which also sidesteps #47. **Owner: owner. Dates: 2026-09-05, 2026-09-22.** ### 8. The window 2026-08-26 to 2026-09-05 is fenced for the conversations — with a security carve-out. COO #70 rec 3, adopted **with an amendment the COO draft did not make**: the fence must not starve the owner-only security items that minutes #54 decision 8 explicitly exempted from rationing. So: - **In scope during the fence:** the 4 conversations; credential rotation (#67); Firestore rules deploy verification (#13); support and on-call; deploy-check duty. - **Out of scope during the fence:** everything else owner-facing, including commerce items (#47 entity/ToS/E&O), which GOALS.md already says wait for a buying signal. **Owner: COO to monitor. Date: 2026-08-26 through 2026-09-05.** ### 9. Gate B3 / #43 is a hard precondition on any outsider or trial login. It blocks nothing else on this agenda. The CISO's headline finding is confirmed and accepted: **name redaction and EMS exclusion are fully unimplemented at HEAD**, a case-insensitive grep across `Server/drb-c2-core/app` and `Server/drb-frontend` returning zero real hits. Any authenticated account — a comped friend, a hypothetical prospect — reads real person names attached to real EMS and medical dispatch. What that blocks, ruled explicitly: **no human, contractor, agency, prospect or trial account gets a product login until #43 ships.** That is now a stated precondition on #43, not a preference, and it is why decision 1 could not have gone the other way even if the money worked. What it does **not** block: the 12 conversations (no login required), the persona (decision 4 bars it from touching product data), or the 2026-09-22 verdict. **Accepted consequence, stated plainly:** #43 is due 2026-09-30, eight days *after* the kill date. If the beachhead survives 2026-09-22, the first trial account cannot be provisioned until #43 lands. The board accepts that eight-day gap rather than pull engineering forward on a probability we have no evidence for — customers-first, per #54 decision 7. **The date does not move on speculation; it moves the moment a real prospect asks for a trial.** **Owner: CTO. Date: 2026-09-30 (existing, unchanged).** ### 10. #63 and #64 keep their 2026-08-31 dates, unchanged by this ruling. CTO #72 rec 2. They are a precondition for ever granting *any* persona a send-capable or credential-holding scope in future — they are not a blocker on today's zero-credential charter, because decision 2 removed the credential. Confirming the CTO's other question: **the ~40-issue backlog is not silently reordered**. growth-ops sits behind #63/#64 and ahead of correlation debt; nothing else moves. **Owner: CTO. Date: 2026-08-31.** ### 11. How the owner's introductions get worked, concretely. Answering #69 item 5. Five steps, with who does each: 1. **Owner** forwards a name, company, and one line of context. Under 2 minutes. 2. **growth-ops**, same day, writes to `growth/`: a short intro-reply draft in the owner's voice, and a one-page brief on the operator (what they do, likely current dispatch workflow, the two required questions). 3. **Owner sends the intro reply from their own account.** growth-ops never sends — and a warm introduction's entire value is that it comes from the owner personally, so this is not merely a security constraint here. 4. **Conversation happens.** Owner gives one line of outcome. 5. **growth-ops** drafts the #66 log entry and the 24-hour follow-up; **CEO or owner** posts the log entry and the owner sends the follow-up. Ruled out for this window, per CMO #73 rec 4 and adopted: trade groups and associations (no cadence exists to reach on this timeline), resellers and partners (sourcing one reproduces a full sales cycle), and existing scanner or first-responder communities for the 12-count specifically (wrong audience, and the vigilantism-optics risk). Scanner communities remain fine as free-tier growth. **Owner: owner + growth-ops. Date: ongoing from 2026-08-26.** ### 12. #69's real question, answered honestly. The owner asked who we hire so the owner is not the growth engine. The truthful answer has two halves and the board owes both: - **Now:** growth-ops removes roughly 80% of the go-to-market function — the list, the scripts, the briefs, the follow-ups, the logging. **It cannot remove the 12 conversations.** No hire, contractor or agency can, in the next 28 days, at 0 of 12, with no entity, no NDA, and no safe login. The owner personally holds ~6-9 hours between now and 2026-09-22. That is the floor and the board is not going to pretend otherwise. - **Permanently:** the answer to "the owner is not the growth engine" is not a person — it is the **scaling channel**, self-serve and inbound (founding agenda item 8, #54 decision 3). That is gated on Gate B, which is gated on the 12 conversations. **The fastest route to the owner never doing sales again runs directly through the owner doing these twelve.** The human-growth-hire question is not closed forever; it is **re-opened by trigger**, not by date — when Gate B opens *and* #43 and #47 have both closed. Recorded as new founding-agenda item 11. **Owner: CEO. Date: triggered, not scheduled.** ### 13. `logan/node-26` items — one line each, as required. - **node-26#1 (node-002 on first-boot default credentials):** not board business, and confirmed still unfixed at HEAD today (`Client/drb-edge-node/app/internal/auth.py:61,75,171-174`, `DEFAULT_PASSWORD = "CHANGE-ME-drb-default"`, mitigated only by a log line). It already has an owner and a date — **CTO, 2026-08-31, minutes #62** — and I decline the COO's 2026-09-01 re-date, which would silently push a live host-level credential exposure past its existing deadline on hardware running `network_mode: host` with privileged `/dev`. **Owner: CTO. Date: 2026-08-31, unchanged. It does not slip past 08-31 without a sitting.** - **node-26#4 (one-line install still needs a manual git clone):** a real but low-severity overclaim — no prospect can self-serve before Gate B, so it cannot cost one of the 12 conversations. Ordinary backlog, sequenced behind #63/#64/#43. **Owner: CTO. No board date.** Neither issue currently carries a `board:agenda` label in `node-26` (that label does not exist in that repo), so there is nothing to remove; both are ruled on here so neither is silently skipped. ### 14. #46 closes or narrows against actual state by 2026-08-31. CMO #73 verified in source today that the price removal and the `/waitlist` CTA both shipped — the two most dangerous live claims from #59 are no longer live. #46 remains open only for its residual sub-items (inline unbuilt markers, AI disclaimer). Leaving it open as though nothing shipped misrepresents Gate A's state to every future sitting. **Owner: CTO — confirm the residual sub-items and either close #46 or retitle it to what actually remains. Date: 2026-08-31 (Monday sitting).** --- ## What we gave up 1. **Any prospect of the owner not doing the first twelve conversations.** Decision 12 states it plainly instead of selling a hire that would not have worked. The owner asked not to be the growth engine and the board's answer for the next 28 days is: you still are, for about 6-9 hours, and here is everything else taken off your plate. 2. **The CISO's safer launch date.** Decision 2 launches on 2026-08-26 rather than 2026-08-31. If the zero-credential boundary is ever eroded in practice — a "just this once" Gitea token — this decision was wrong and should be reversed on the spot. 3. **Eight days of trial-readiness.** Decision 9 leaves #43 at 2026-09-30, so a successful 2026-09-22 verdict cannot be converted into a trial account for eight days. Bought: engineering stays on #63/#64 and off a bet with no evidence behind it. 4. **The walk-in's persuasive edge.** Decision 5 makes a 15-minute phone call worth as much as a 45-minute in-person visit. In-person almost certainly converts better. We traded conversion quality for count, because the kill criterion measures count and the count is zero. 5. **Owner attention on everything else, 08-26 to 09-05.** Decision 8 spends essentially the whole discretionary owner-hour budget for that window on four conversations. 6. **A wider top of funnel.** Decision 11 rules out associations, partners and scanner communities for the 12-count. If warm introductions and the Westchester list both run dry before 09-05, that ruling is the first thing to revisit. --- ## Dissent - **CISO (#77), dissent 1 — timing.** Argued growth-ops should not stand up before #63 lands 2026-08-31 if it needs Gitea write access. **Upheld in substance, overruled on remedy.** The premise is accepted: no new agent gets a raw token before #63. The remedy is rejected: the fix is to remove the credential (decision 2), not to spend 5 of the 11 remaining days waiting. If growth-ops is ever found holding a credential, this reverses without a sitting. - **CISO (#77), dissent 2 — transmission capability.** **Upheld in full**, decision 3, and written into #78 as a structural constraint rather than a convention. - **COO (#70), rec 1 as written.** Overruled — an unqualified charter is not available; the CTO's and CISO's conditions bind it. - **COO (#70), rec 6 — node-26#1 re-dated to 2026-09-01.** Overruled, decision 13. It has a 2026-08-31 date from minutes #62 and a board does not quietly extend its own security deadline. - **COO (#70), rec 3 — window fencing.** Adopted with an amendment the draft omitted: the security carve-out in decision 8. An unamended fence would have collided with #54 decision 8, which exempts credential rotation from rationing. - **CTO (#72) on self-serve.** Agreed and recorded: self-serve inbound is not a competing answer to #69 today — it is Gate A/B-gated regardless and does not build the trust a physical-safety product's first 12 conversations require. It is the *permanent* answer (decision 12), not the current one. - **CMO (#59), revised not reversed.** #73 correctly narrows "almost all go-to-market work is owner-only" to "about 12 live conversations are owner-only". That revision is ratified. #59's other conclusions stand. - **No exec was skipped.** --- ## Drafts #70 COO · #72 CTO · #73 CMO · #77 CISO (#71 was a byte-duplicate of #70 and was already closed before this sitting.) --- ## Follow-up issues filed - **#78 — HIRING: growth-ops (outreach preparation persona).** Rationale, decision scope, what it may touch, and what it must be structurally incapable of doing. **Needs the owner** to wire with Claude in a live session, 2026-08-26. Deliberately filed as comments rather than new issues, to avoid splitting one problem's history across two records: - **#66** — the ratified qualifying-conversation definition (decision 5). - **#43** — the outsider/trial-login precondition (decision 9). - **#46** — confirm-and-close instruction (decision 14). - **#69** — the ruling, for the owner who filed it. --- ## Charter amendments enacted this sitting - Founding agenda **item 8 (the scaling channel)** — amended, **not** struck. This sitting settled the *ownership* half (a persona now; a human hire only on trigger) and left the *channel* half where minutes #54 put it: triggered by the 2026-09-22 beachhead report. - Founding agenda **item 11** — new standing item: rule on a human growth hire. Trigger, not a date: Gate B open **and** #43 closed **and** #47 closed. - `CLAUDE.md` project-docs table — `GOALS.md` status updated to record the qualifying-conversation definition ratified here. - `GOALS.md` — kill-criterion section stamped with the definition from decision 5. --- ## Open — needs the owner 1. **Wire the `growth-ops` persona with Claude in a live session — #78. By 2026-08-26.** Nothing else in this ruling starts until this happens. 30-60 minutes. 2. **Start the conversations. 4 logged on #66 by 2026-09-05.** Phone and video now count (decision 5), so this is ~2-3 hours, not a day of driving. 3. **Forward any warm introduction the moment it exists** — a name and one line, under 2 minutes each (decision 11). 4. Carried, not new, and unblocked by this sitting: **#67** credential rotation and **#13** Firestore rules deploy verification (both console-only, both inside the fence, due 2026-08-31), and **#45**'s dollar cap, which is owner-only money. Refs #69, #70, #72, #73, #77, #78, #66, #63, #64, #43, #46, #47, #45, #13, #4, node-26#1, node-26#4. Supersedes nothing; amends minutes #42's conversation-quality wording per decision 5 and stands on minutes #54 and #62.

logan added the board minutes:final role:ceo labels 2026-08-25 21:47:39 -04:00

Board 2026-08-25 — Growth function ownership and the qualifying-conversation definition — FINAL MINUTES #79