// verdict #9 · 14 May 2026 · 22:25 UTC

heypocket.com/

PASS

three or more voices said no. release without guilt.

submitted by Rob · BLKOUT · model anthropic/claude-sonnet-4 · against wishlist of 2026-04-27T11:18:37z · visit the tool → · back to history

// the four voices, in parallel

What the Council said

// 01 · critic

Baldwin

pass

technical risk, lock-in, sequencing — the master's tools.

Looking at Pocket, this is a physical AI device that magnetically attaches to your phone to record and transcribe conversations and voice notes. Let me stress-test this against BLKOUT's context. ## GUARDRAIL VIOLATIONS **Pre-order model mismatch**: This is a $169+ hardware device with subscription tiers, not software that fits BLKOUT's pre-order/waiting-list model. Category mismatch. **Infrastructure before application**: BLKOUT is in Year One, focused on "debug infrastructure (CPU, disk, running services, Docker images) before application code." Adding a physical AI device creates new operational complexity when the foundational digital infrastructure isn't stable yet. ## CRITICAL CONCERNS **Vendor lock-in**: This is proprietary hardware with cloud-dependent AI processing. No self-hosting option, no data export guarantees, complete dependency on the vendor's servers and business model. **Surveillance mechanics**: Records conversations continuously, processes audio through third-party AI services, stores transcripts in vendor cloud. This directly contradicts BLKOUT's data sovereignty principles and member control over their data. **Technical debt**: Introduces a physical device dependency that doesn't integrate with BLKOUT's existing Coolify/Supabase stack. Creates a separate data silo that can't feed into the CRM or other systems. **Operational overhead**: Hardware requires charging, maintenance, replacement cycles. Subscription costs ongoing. Small team burden for managing physical devices across community activities. ## WISHLIST MAPPING This doesn't map to any item on the fifteen-capability wishlist. The closest might be supporting member consultation or co-production work, but those explicitly require "co-designed" approaches, not surveillance-adjacent recording tools. The device assumes always-on recording in community spaces, which would undermine the trust-building that several wishlist items depend on. ## SEQUENCING PROBLEMS BLKOUT needs "tech stability and system resilience" (Tier 1) before adding new operational complexity. The AI policy (also Tier 1) should be established before adopting AI tools that record community conversations. This tool jumps ahead to application layer before the foundational infrastructure questions are resolved. **RECOMMENDATION: PASS**

// 02 · ethicist

Murray

pass

values, sovereignty, community benefit.

Looking at Pocket, this is a hardware AI device that clips to your phone and records conversations/thoughts for transcription and analysis. Let me evaluate it against BLKOUT's principles and needs. **Values Assessment:** **DATA SOVEREIGNTY - Critical Concern**: This device is fundamentally about capturing and processing personal conversations and thoughts through proprietary AI systems. The website provides no information about data ownership, storage location, or member control over their recordings. This directly conflicts with BLKOUT's principle that "members own their data" and the organisation holds it "in trust, not as an asset." **ANTI-SURVEILLANCE - Red Flag**: Pocket is literally a surveillance device - it records conversations, potentially without all parties' knowledge or consent. The marketing even promotes "phone call transcription (with consent)" as a feature, suggesting it can record calls. This crosses the line between care and surveillance that BLKOUT explicitly rejects. **TRANSPARENCY - Opaque**: No information about how the AI processing works, where data is stored, or what happens to recordings. Members couldn't "see what the organisation holds about them" if BLKOUT adopted this tool. **OPEN-SOURCE ALIGNMENT - Proprietary**: This is a closed, commercial hardware product with opaque AI processing. **Wishlist Mapping:** This doesn't map to any item on BLKOUT's wishlist. The closest might be "AI policy" development, but Pocket would violate the very principles that policy should establish. It's not infrastructure, member experience tooling, or co-production - it's a personal productivity device that would introduce surveillance mechanics into community spaces. **Guardrail Violations:** While not explicitly listed in the guardrails, this violates the foundational principle that tools must serve the community, not extract from it. A recording device that processes community conversations through proprietary AI systems is extractive by design. **Community Context:** For a Black queer community benefit society, introducing recording devices into social and support spaces would fundamentally alter the nature of those spaces. Trust and safety require knowing when conversations are being captured and processed. This tool would make authentic community connection harder, not easier. The device might have legitimate uses for individual productivity, but it's incompatible with BLKOUT's mission and values. The surveillance implications alone make this a clear values mismatch. RECOMMENDATION: PASS

// 03 · builder

Rustin

pass

vibe-codeability, stack fit, lift — what'll actually ship.

Looking at Pocket, this is a hardware AI device that clips to your phone and records conversations/thoughts for transcription and analysis. Let me break this down against BLKOUT's context: ## GUARDRAIL CHECK **PASS** - This doesn't violate any guardrails directly, but it's completely orthogonal to BLKOUT's digital infrastructure needs. It's a consumer hardware product, not a software tool that integrates with the existing stack. ## WISHLIST MAPPING This doesn't map to any item on the wishlist. The closest might be infrastructure tools for capturing community insights, but Pocket is designed for individual productivity, not community organizing or member experience. ## TECHNICAL ASSESSMENT **VIBE-CODEABILITY**: Not applicable - this is a physical device with a companion app, not something BLKOUT would build or deploy. **STACK COMPATIBILITY**: Zero compatibility. This is consumer hardware that would sit entirely outside BLKOUT's VPS/Coolify infrastructure. **SPEED OF DEPLOYMENT**: Fast for individual users (buy device, download app), but irrelevant to BLKOUT's organizational needs. **LIFT ASSESSMENT**: Minimal technical lift for individuals, but no organizational value for BLKOUT. **MAINTAINABILITY**: BLKOUT wouldn't maintain this - it's a third-party consumer product. **INTEGRATION POTENTIAL**: None. This doesn't connect to CRM, member pages, AIvor, events, or any other BLKOUT systems. ## CORE PROBLEM Pocket is solving individual productivity and note-taking, not community organizing, member experience, or co-production. It's a personal AI assistant for capturing your own thoughts, not a tool for building Black queer community infrastructure. The pricing model (one-time hardware purchase + optional subscription) and the use case (personal voice memos and meeting transcription) are completely misaligned with BLKOUT's needs as a community benefit society building digital capabilities for member organizing. This feels like it was suggested because it has "AI" in the description, but the actual functionality doesn't serve any of BLKOUT's strategic priorities. RECOMMENDATION: PASS

// 04 · inclusion

Rivera

pass

reach, the under-served, who's on the street.

This is a $200+ AI-powered wearable device that records conversations and thoughts, then processes them through AI to generate summaries, insights, and action items. Let me interrogate this against reach questions for BLKOUT. **ACCESSIBILITY FLOOR**: This tool assumes you own a recent iPhone (MagSafe compatibility), can afford a $200+ device, have stable internet for AI processing, and are comfortable with English-dominant AI interfaces despite claiming "120+ languages." The device literally attaches to your phone — if you don't have the right phone, you can't use it. That's a hard exclusion for anyone on older devices, Android users, or people who can't drop £200 on a gadget. **PRIVACY ARCHITECTURE**: This is surveillance dressed up as productivity. The device records everything around you and sends it to external AI services for processing. For closeted people, asylum seekers, survivors, or anyone in unsafe households, this is a privacy nightmare. The marketing focuses on "capturing conversations" and "phone call transcription" — exactly what someone trying to stay safe cannot afford to have recorded and processed by unknown third parties. **COST TO USER**: The website shows "up to 45% off" pricing but doesn't reveal the actual cost until checkout. The testimonials from VCs and "startup founders" signal this is priced for the already-privileged. There's mention of subscription features beyond the "lifetime core features" — so ongoing costs on top of the device price. **PERFORMANCE DEMANDS**: The entire value proposition assumes you have thoughts worth capturing, conversations worth transcribing, and insights worth generating. It's built for "professionals" and "people who get things done" — the productivity-optimized class. What about people whose primary need is connection, not optimization? What about people whose best thinking happens in community, not in solo voice memos? **REGISTER**: Despite claiming multilingual support, the marketing is entirely in productivity-speak English. "Capture your mind in motion," "augmented brain," "insights at your fingertips" — this is Silicon Valley language that assumes familiarity with tech culture and self-optimization frameworks. **ISOLATION vs NETWORK**: This is fundamentally an isolation tool. It's about capturing *your* thoughts, optimizing *your* productivity, augmenting *your* brain. There's no community element, no way to share insights with others, no recognition that the best thinking often happens between people, not inside individual heads. **GEOGRAPHIC REACH**: US-focused (the country selector defaults to US), with shipping and support likely concentrated there. The testimonials are all from tech industry people, suggesting this hasn't been tested in community contexts outside Silicon Valley. Looking at BLKOUT's wishlist, this doesn't map to anything they're actually trying to build. It's not infrastructure, it's not about member experience in a community context, and it's not co-production. It's individual productivity tech that assumes the user is already well-resourced and tech-savvy. This tool deepens existing exclusion by requiring expensive hardware, creating privacy risks for vulnerable people, and centering individual optimization over community connection. It serves exactly the over-served — tech professionals who already have too many productivity tools. RECOMMENDATION: PASS

// context at time of judgement

The Wishlist, as it was then +

this is the document the council was asked to hold this tool against. click to expand.

BLKOUT Digital Strategy — Living Document

This document is the authoritative context for the Dreamcatcher Council. It combines BLKOUT's Year One guardrails with the fifteen-item wish list. The Council reads this fresh on every evaluation — edits here immediately reshape every future verdict.

Last revised April 2026. For board and community input.

Year One Guardrails

Rules that hold while foundational infrastructure is being built. Harder than tier priorities — these do not negotiate.

— No n8n. All automations use node-cron or Supabase triggers. n8n was tried and removed; the operational cost of a workflow engine outweighed the benefit for a small team.

— Schema ownership. The CRM's 001_crm_complete_schema.sql is authoritative. Any new tool that touches member data reads from CRM tables — it does not maintain a separate schema.

— Pre-order model, not always-on store. The BLKOUT shop is a waiting-list / pre-order surface with CBS tiers (free / £3 per month / £10 per month). Tools that assume always-on e-commerce are a category mismatch.

— Stripe pre-flight. Stripe routes stay disabled until credentials are confirmed in Coolify. Test mode only — no tool that requires live payment provisioning on adoption.

— CRM mock data stays until migrations verified. Nothing removes CRM mock data until the equivalent migration has been confirmed via supabase-query.mjs. Tools that auto-migrate are held until verification is possible.

— RSVP and Stripe are already built. Frontend and backend exist in the platform. Tools that duplicate these are a category mismatch — the gap is credentials and tables, not code.

— Infrastructure before application. Debug infrastructure (CPU, disk, running services, Docker images) before application code. Tools that add operational complexity must justify themselves against this order.

Wish List — fifteen capabilities

Prioritised by potential impact and capacity to instigate change. First draft March 2026, living document since.

Tiers: do now (accessible) — plan and build (moderate lift) — develop with intent (significant undertaking)

Categories: infrastructure — member experience — co-production

Tier 1 — do now

High impact, low barrier — no dependency blockers.

— AI policy, à la New Public infrastructure accessible Unlocks the integrity of everything beneath it. Determines what BLKOUT will and won't do with AI, and why. Data sovereignty and privacy follow from this document, not the other way around. Mainly a thinking and writing exercise — the hardest part is the thinking.

— CRM — values-embedded member system member experience accessible Already in active use. Develop with transparency and member control principles baked in before habits calcify around the wrong defaults. Needs connecting to member pages, AIvor, and the directory as those mature.

— Leania.ai — AI ops audit infrastructure accessible Quick diagnostic of workflows, tools and bottlenecks. Keep / kill / replace / automate recommendations. Low cost, high information value. Caveat: recommendations will skew commercial — use the diagnostic layer, not the prescription.

— Tech stability and system resilience infrastructure moderate lift Without this, everything built on the infrastructure will fail. The VPS, Coolify, and all modules need to be reliable and recoverable before more is added. Foundational before ambitious.

Tier 2 — plan and build

High impact, requires resourcing, people or sequencing.

— Bookkeeping, financial regulations and fundraising infrastructure moderate lift CBS obligation, funder pipeline active. Needs the right person as much as the right tool — the Treasurer role is load-bearing. Required before significant grant income flows through the organisation.

— Compliance infrastructure — demonstration not monitoring infrastructure moderate lift Mission risk if left too long. Evidence of governance, financial stewardship, and community benefit must be buildable in real time, not reconstructed after challenge. Systems need building before they are needed.

— Regular events calendar and Brunch 2030 member experience moderate lift Visible, reliable rhythm signals organisational health. Monthly social, film screening at The Arzner, community organisers gathering, seasonal specials, Berto Pasuka day. Key venue relationships held — Stanley Arts, The Arzner. Delegate the programming.

— Non-intrusive lead generation member experience moderate lift Community-appropriate discovery. Transparent about the win on all sides. Values-consistent methodology — games welcome if honest, surveillance mechanics excluded. The question is whether the constraint is capacity, visibility, or trust, because each has a different solution.

— Live directory of Black queer civil society co-production moderate lift Co-production and community research — built by the community, kept live by the community. Feeds CRM, AIvor, lead generation, and network mapping simultaneously. The gaps in the directory are as revealing as what is in it.

— Partner tool and project management dashboard infrastructure moderate lift Operational capacity for transparent relationships with organisations of all sizes. Sits on stable infrastructure. Enables partnerships to be held without depending on founder memory.

— Network mapping — loneliness co-production moderate lift How loneliness manifests for Black queer men — which responses are proximate, which require greater effort. Research question still needs articulating before design. Board community lead to own this. Brunch network exercise as potential methodology.

Tier 3 — develop with intent

Transformative — significant undertaking, dependencies to resolve first.

— Unique member pages — member-controlled data as feature member experience significant Members see exactly what BLKOUT holds about them, can edit or delete any of it, and are equipped to ask the same of others. Policy as education. Significant data architecture. Needs CRM foundation first. The feature that most visibly demonstrates the values.

— Next-level AIvor — orchestration on member need member experience significant From broadcaster to responder — receiving member need signals and acting on them, with care and ethical guardrails. The line between care and surveillance must be designed in from the start. Depends on knowing what members actually need. Network mapping and directory must precede.

— Co-designed member consultation with iterative learning loop co-production significant Design the consultation process in consultation. Radical transparency, shared results, member agency in decisions that follow insight. Includes autoresearch-style closed feedback cycle with co-designed metrics. Never a failure, always a lesson — at organisational scale. The most ambitious item on the list and the one that could make every other item more effective.

— Youth leadership intervention co-production significant Form and content both need co-producing — this cannot be designed for young people, only with them. Requires funding. Can begin relationship-building and scoping conversations now, against the backdrop of Black youth unemployment returning to 1981 levels.

— Enterprise and wealth — pop-up / shebeen / art model co-production significant Still forming. The relationship between enterprise, workplaces, community and intergenerational wealth remains to be discovered. An inquiry that in its form embodies potential elements of the final proposal — collaborative, cultural, accessible, profitable, sociable. Trust for London proposal as the discovery vehicle.

BLKOUT Creative Ltd — Community Benefit Society Living document — edited in situ via the Dreamcatcher editor

---Podcast hosting — added April 2026, surfaced via Commons page build

What we want: A hosted podcast platform with a brand-themeable embeddable player (we'll skin to obsidian/gold), an RSS feed for distribution to Spotify/Apple Podcasts, and basic listener analytics. Should integrate with the Commons + Critical Frequency pages without a generic Drive iframe.

Why now: We're starting to publish AI-generated audio (NotebookLM Deep Dives, future episodes from the Compass material). Drive embed is the current workaround — generic player, no podcast-app distribution, no analytics, asset lives in personal Drive.

Constraints / what we won't: Free tier or low monthly cost (BLKOUT is small); no extractive licensing on community audio; option to self-host or export RSS to migrate (no lock-in); accessible player UI; no Spotify exclusivity.

On the radar for Council review when surfaced: Castopod (open source, self-hostable on Coolify — natural fit), Transistor (paid, neutral, RSS-first), Buzzsprout, Spotify for Podcasters / Anchor (free + reach but sovereignty concerns).