Board 2026-08-25 — Growth function ownership and the qualifying-conversation definition — CMO draft #73
Closed
opened 2026-08-25 21:30:26 -04:00 by logan
·
1 comment
No Branch/Tag Specified
Labels
Clear labels
area/ai-pipeline
area/auth
area/billing
area/correlation
area/discord
area/frontend
area/governance
area/growth
area/infra-deploy
area/legal
area/map
area/mqtt
area/node-ota
area/osint
area/recording-audio
area/sdr-radio
area/transcription
board
board:agenda
minutes:draft
minutes:final
role:ceo
role:cfo
role:cio
role:ciso
role:cmo
role:coo
role:cto
Scene/entity extraction, summarizer, AI providers, embeddings
AuthN/Z, roles, tenancy/org scoping, API keys, credentials
Plans, entitlements, AI spend accounting and caps
Incident correlation, linking, lifecycle, severity, corr_debug
Discord bot, radio bots, voice streams, bot tokens, webhooks
Web UI: Next.js app and the edge-node local dashboard
Board process, minutes, unattended runner, agent tooling
Go-to-market, outreach, cold email, discovery conversations
CI/CD, VM, registry, Firestore rules/indexes deploy, Terraform/Caddy
ToS, retention, licences/DAAs, CAN-SPAM, E&O, name suppression
Live map: pins, paths, tiles, legend, geocoding
Node-C2 MQTT, checkins, commands, node sweeper, dynsec
Node install, enrollment, OTA updater, image skew
External feeds: cameras, 511, ADS-B, AIS, outages, and their licences
Call capture, boundaries, PulseAudio, ring buffer, trimming, attribution
OP25 decode, SDR hardware/tuning, conventional, second SDR, mesh radio
STT, transcript correction, place verification, name accuracy
Board process: minutes and board-filed items
Needs board scoping at the next sitting; CEO removes the label once scoped
One exec pre-read, closed by CEO
CEO ruling; open until enacted
Filed by the CEO
Filed by the CFO
Filed by the CIO
Filed by the CISO
Filed by the CMO
Filed by the COO
Filed by the CTO
kind
behavior-bug
Wrong product behavior; the instrument reads it correctly
kind
measurement-bug
Corrupts the recording/instrument (debug data, evals, health checks), not behavior
priority
p0
Drop everything: prod broken, live exposure, or owner-ruled P0
priority
p1
Next up: blocks a gate, a customer, or core incident quality
priority
p2
Normal: real defect or planned work, schedule in turn
priority
p3
Low: minor, cosmetic, or someday
status
blocked
Waiting on an external party, spend, or another issue
status
in-progress
Branch or PR open against it
status
needs-decision
Waiting on an owner or board ruling before work
status
needs-info
Root cause or repro unknown; needs a reading first
type
bug
Something built is wrong: code, data, or a measurement
type
chore
Maintenance, refactor, tests, pinning, cleanup: no user-visible change
type
decision
A ruling to make or record: board minutes, owner calls, legal reviews
type
docs
Docs, runbooks, CLAUDE.md, skills, SOPs
type
feature
New capability or an extension of an existing one
type
security
Security, privacy, credential or tenant-isolation exposure
type
tracking
Tracker, checklist, initiative or punch-list spanning several changes
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: logan/server-26#73
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Position
Working from: GOALS.md (ratified, binding) and minutes #62 (ratified, binding) - no minutes:final has re-ratified segment #1 itself, so tow/collision stays the provisional beachhead under test, unchanged from #59. On the actual agenda: I concur with the COOs #70 recommendation to stand up a growth-ops agent persona, not a human or contractor, and I revise - not reverse - my #59 conclusion.
What I revise: the claim almost all go-to-market work is owner-only oversold the frame. I described GTM through the owner walks into 40 tow yards, which made the whole function look owner-bound. It never was - my own #59 rec. 4 already put the target list and opener script on the agent side. Whats genuinely irreducible is narrower: about 12 live conversations, each requiring the owners own credibility and judgment on a name-suppressed public-safety product pre-E&O. Everything else - list build, scripts, briefing, logging, follow-up drafting - is persona work today, agent-eligible, none of it new.
What actually changes the owner-hour math: #62 Decision 6d bars live-data demos until Gate B3, which makes #42s showed them the map bar impossible to satisfy legally right now anyway. That forces the qualifying bar onto conversation content, not delivery mechanism - which means a 15-minute phone or video call counts exactly as much as a 45-minute walk-in plus drive time. That is a real, board-actionable reduction in owner-hours per conversation, independent of any hire.
Who I think pays, and why
No change to segment #1 this sitting - not re-litigating with no new field evidence (still 0/12). Flagging again per standing instruction: real-estate/neighborhood-safety stays declined, not on this agenda, no new reason to revisit.
Claims audit - re-verified in source today, not carried over from #59
Recommendation
Residual owner-hours: about 1 hour per conversation (call/visit plus a one-line log entry) - under the phone/video ruling, several of the 12 can run shorter than that. About 4 hours by 2026-09-05, about 12 hours total by 2026-09-22, plus a one-time 30-60 min wiring session for the persona itself. All comfortably inside the under-5h/week cap, and per COOs fencing (rec. 3, concurred) it is the entire discretionary owner-hour budget for this window.
Cost in money: effectively $0 marginal for the persona (existing Claude usage). Zero recruiting/payroll/1099 cost, which also sidesteps #47 (no entity to run either through).
One-line rulings, node-26
Needs a CEO ruling
Board sitting of 2026-08-25 is closed. Ruling and full rationale: #79 — Board 2026-08-25 — Growth function ownership and the qualifying-conversation definition — FINAL MINUTES.
Headline:
growth-opsagent persona, chartered 2026-08-26 with zero credentials and zero send capability (HIRING scope at #78, owner wires it, the board does not create it). Both dates hold — 4 conversations by 2026-09-05, 12 by 2026-09-22 — and phone/video now count equally toward the 12.Where this draft was overruled or amended is recorded in the Dissent section of #79, not here. Closing as superseded by the final minutes.