Gate B8: transcript entity-name accuracy has never been measured, yet names are being published #48
Open
opened 2026-08-23 17:33:10 -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#48
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.
Board minutes #42 (2026-08-23) - Ratify BUSINESS_MODEL.md. - Gate B condition B8. Blocks charging any customer.
BUSINESS_MODEL.md§8 item 6, and the document own note on it: "this is the one people skip. You are about to sell machine-generated assertions about real incidents."No measurement of transcript accuracy exists in source; the CISO (#39) confirmed it cannot be checked from a static read. We are currently publishing machine-extracted person and place names with an unknown error rate.
To close: sample 200 calls and hand-score (a) word error rate and (b) entity-name accuracy, separately. The second number is the one that matters.
Pre-committed now, so the result cannot be argued with after the fact (minutes #42 Gate B, B8): if entity-name accuracy is below 80%, names are suppressed by default. Committing to the threshold before seeing the number is the entire point.
Costs an afternoon and one spreadsheet, per the document. Requires human judgement - not agent-automatable.
Owner: the owner (human). Date: not set until the owner schedules it - see minutes #42 "Open".
Related:
BUSINESS_MODEL.md§8 item 6, §9 Q3; the Gate B3 redaction issue.Remit changed (not removed) by owner ruling 3, board minutes #42, "Owner rulings, 2026-08-23" comment.
The owner declined E&O spend pre-revenue ("assume it will happen but get to product mvp, feedback, then go for company things"). Gate B7's pre-agreed consequence is that person names are suppressed by default on every surface, paid included, until a policy is bound - see #43.
Therefore the pre-commitment in this issue - "if entity-name accuracy is below 80%, names are suppressed by default" - is now moot as a decision rule: names are suppressed either way. This issue is not dropped from Gate B. Its purpose changes to three things that still have to be true before we charge anyone:
Method unchanged: sample 200 calls, hand-score word error rate and entity-name accuracy separately. Still requires human judgement; still owner-scheduled.