Board 2026-08-24 — Unattended operating cadence and GOALS tracking — CMO draft #59
Closed
opened 2026-08-24 23:29:25 -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#59
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:
BUSINESS_MODEL.mdratified in structure only (minutes #42, #54) - the beachhead itself (section 0 line 6, section 1's #1 pick, section 3.4) is explicitly provisional, owner conviction low ("no real direction but sure tow is fine"). Nominutes:finalratifies tow/collision as decided go-to-market - it is a hypothesis under an active kill test, and I am treating it that way, not as settled. GOALS.md (#54, binding) is what actually governs this sitting: 12 discovery conversations by 2026-09-22 or the commercial track dies.On (1): almost all go-to-market work is owner-only. The unattended runner should stop treating "business item" as open-ended and pick only from a short concrete list (below).
On (2): at day 1 of 29, zero conversations run, and no mechanism exists that makes the deadline visible before it's blown. On the owner's own stated conviction, this fails quietly unless the board forces visibility now. Recommend an early checkpoint, not a wait-and-see.
Who I think pays, and why
No new segment recommendation this sitting - I am not overturning section 1 with speculation, only flagging that the untested #1 pick has had zero real-world signal added since ratification. Trigger for segment #1 (tow/collision) buying: a bad accident week, or a competitor beating them to a tow because they heard it slower - that trigger doesn't get tested until someone actually talks to 12 of them. Reachability is real (about 40 Westchester operators, walk-in) but only if the owner walks in - no part of this is reachable by an agent. Raising the real-estate/neighborhood-safety exposure again per standing instruction: still correctly declined (section 1 segment #7), not on this agenda, no new reason to revisit.
Claims audit
lib/billing.tsis a stub (own file header says so); zero billing backend routes (ADMIN_BILLING_AUDIT.mdsection 2). Ratified Gate A says pricing comes off the site, "a false price anchor with a footnote is worse than no price" - the site has exactly that footnote (pricing/page.tsxlines 87-89) today, a day after ratification. Tracked open: server-26#46, due 2026-09-13, not fixed. This is the single most dangerous live claim on the siteapp/login/page.tsxonly offers email/password and Google sign-in, no signup path. A genuine new visitor cannot create an account thereintelligence.py); rendering is not -UI_REDESIGN.mdconfirms units_active, units_cleared, per-call vehicles, location_coords are produced and thrown away by the UI. Claim overstates delivered experienceRecommendation
page.tsxandpricing/page.tsxentirely, replace with "Pricing in development - contact us," per the ratified Gate A instruction. This is copy/removal, not a business judgment call - eligible unattended-agent work this run. Owner: CTO/engineering, no owner-hours.UI_REDESIGN.md, already scoped, "needs no backend") before selling "reads like a briefing" any harder - small, agent-eligible. Owner: CTO.Business work eligible for the unattended runner (concrete list, replaces the open-ended "one business item")
Eligible (agent can advance alone):
ADMIN_BILLING_AUDIT.mdstub cleanup,SAAS_PLAN.mdsequence items.Owner-only (agent must surface, never attempt): the 12 conversations themselves, any price quote, any account provisioning, ToS/Privacy/AUP authorship-and-signing, business entity formation, E&O binding, agency takedown contact designation, delay-policy decision. If the honest answer on a given run is "nothing on this list is unblocked," the runner should say that plainly instead of inventing a business task - that is itself a report-worthy finding, not a failure to hide.
Needs a CEO ruling
Closed against final minutes #62.
Carried:
a1bdccf. You were right that this was the single most dangerous live claim on the site./pricingand the homepage teaser now carry no numbers./waitlistalready exists as a real request-access page, so the CTAs point there instead of at a sign-in page with no signup./logslice of #56.Deferred, not rejected:
units_active/vehicles - real, already scoped inUI_REDESIGN.md, but it did not beat #66, node-26#1 or the Gate A fix for this week. It goes in the runner queue behind those.Ruling on your open question about a live demo: no live-data screen-share until Gate B3 (#43) is scoped. #62 Decision 6d.
logan referenced this issue2026-08-31 02:46:15 -04:00