// verdict #7 · 14 May 2026 · 22:02 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.

I've reviewed Pocket and it's a fundamental mismatch with BLKOUT's infrastructure and principles. **GUARDRAIL VIOLATIONS:** - **Schema ownership**: Pocket maintains its own content database separate from BLKOUT's CRM schema. The wishlist item "CRM — values-embedded member system" requires everything to connect through CRM tables, not fragment across proprietary silos. - **Surveillance mechanics**: Pocket is owned by Mozilla but operates as a content recommendation engine that profiles reading behavior to suggest articles. This creates exactly the "extraction dynamics at odds with BLKOUT's data sovereignty principles" that the AI policy (Tier 1) needs to address first. **SEQUENCING PROBLEMS:** This doesn't map to any wishlist item. The closest might be "AIvor — orchestration on member need" but that's Tier 3 and explicitly requires the directory and network mapping to be built first. Pocket is a consumer bookmarking tool, not community infrastructure. **OPERATIONAL OVERHEAD:** Pocket creates dependency on Mozilla's servers and recommendation algorithms. If the team wants content curation, that capability should be built into the existing platform where members control their data, not outsourced to a third party that profiles reading habits. **TECHNICAL DEBT:** Adopting Pocket now would establish a pattern of reaching for external tools instead of building member-controlled alternatives. This calcifies bad defaults before the foundational AI policy and CRM connections are solid. The real question is what problem this is meant to solve. If it's content discovery for members, that belongs in the directory or AIvor. If it's research organization for the team, that's an internal workflow question that doesn't require member data to flow through Mozilla's systems. RECOMMENDATION: PASS

// 02 · ethicist

Murray

pass

values, sovereignty, community benefit.

Looking at HeyPocket, this is a social bookmarking and content curation platform that allows users to save, organize, and share links with others. It's positioned as a way to build collections of resources and discover content through community curation. **Values Analysis:** **Data Sovereignty**: Significant concern. HeyPocket is a proprietary platform where users' curated content, bookmarks, and usage patterns become platform assets. Members would be contributing valuable intellectual labor (curation) to a commercial platform without ownership or portability guarantees. This directly conflicts with BLKOUT's data sovereignty principle. **Anti-Surveillance**: The platform's discovery and recommendation features likely involve tracking user behavior, reading patterns, and social connections to surface relevant content. While framed as helpful curation, this creates detailed profiles of member interests and networks — classic surveillance mechanics regardless of intent. **Community Benefit vs. Extraction**: HeyPocket's business model appears to rely on aggregating user-generated curation to create value for the platform. Members would be providing free labor (organizing and contextualizing resources) that generates commercial value they don't share in. **Wishlist Mapping:** This doesn't clearly map to any specific wishlist item. The closest might be supporting the **"Live directory of Black queer civil society"** through resource curation, but that directory is explicitly described as "built by the community, kept live by the community" — not hosted on a third-party commercial platform where BLKOUT wouldn't control the infrastructure or data. **Guardrails Check:** While HeyPocket doesn't violate the technical guardrails (it's not n8n, doesn't touch CRM schema, etc.), it does conflict with the foundational principle that **"Infrastructure before application"** — this adds operational dependency on an external platform without addressing any of BLKOUT's core infrastructure needs. **Alternative Consideration:** If BLKOUT needs community resource curation, this capability could be built into the existing platform using the CRM foundation, supporting both data sovereignty and the eventual "unique member pages" where members control their contributed content. RECOMMENDATION: PASS

// 03 · builder

Rustin

pass

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

Looking at Pocket (heypocket.com), this is a read-later service for saving and organizing articles, videos, and other web content. Users can save items to read later, tag them, and access them across devices. **VIBE-CODEABILITY**: Not applicable - this is a SaaS service, not something BLKOUT would deploy or maintain. The integration would be minimal (maybe embedding saved content or using their API). **STACK COMPATIBILITY**: As a third-party service, it doesn't directly interact with BLKOUT's Coolify/VPS setup. Any integration would be API-based. **SPEED OF DEPLOYMENT**: Very fast - accounts can be created immediately, and basic usage requires no technical setup. **LIFT ASSESSMENT**: Accessible - using Pocket is straightforward, and any integration work would be minimal. **MAINTAINABILITY**: Pocket handles their own infrastructure. BLKOUT would just be a user. **INTEGRATION POTENTIAL**: Limited direct integration with BLKOUT's stack. Could potentially feed into content curation for the Commons page or research workflows, but it's not a natural fit with the CRM, member pages, or other core systems. **GUARDRAIL CHECK**: No guardrail violations - this doesn't duplicate existing functionality or require n8n. **WISHLIST MAPPING**: Here's the problem - Pocket doesn't map to any specific item on BLKOUT's wishlist. It's a personal productivity tool for content consumption, but BLKOUT's priorities are around member experience, co-production, and organizational infrastructure. The closest connection might be supporting research workflows that feed into the **live directory** or **network mapping** work, but that's a stretch. The real question is: what problem would Pocket solve for BLKOUT that isn't already handled by existing bookmarking tools or note-taking systems? For a small team with focused priorities, adding another tool needs clear justification against the wishlist. RECOMMENDATION: PASS

// 04 · inclusion

Rivera

pass

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

I've reviewed Pocket (heypocket.com) against BLKOUT's context and my inclusion lens. **What Pocket is:** A "read later" service that saves articles, videos, and web content for offline reading across devices. Premium tier adds features like permanent library, full-text search, and suggested tags. **Accessibility floor analysis:** - **Device assumptions:** Requires smartphone/computer with internet for saving, though offline reading helps with intermittent connectivity - **Literacy barriers:** Assumes text-heavy consumption patterns and English-language content curation - **Cost barriers:** Free tier exists but premium features (£4.49/month) gate the most useful functionality **Privacy architecture:** - **Exposure risk:** Reading lists could reveal political interests, health searches, job hunting activity to anyone with account access - **Household safety:** Browser extensions and saved articles visible to others using shared devices - **Data sovereignty:** Mozilla-owned (better than big tech) but still centralized data storage **Reach questions for BLKOUT context:** - **Who's this NOT for?** People who consume information through audio, video, or community conversation rather than saved articles. Those without stable housing to maintain reading routines. Community members who get their information through WhatsApp forwards and social feeds rather than longform articles. - **Geographic reach:** Works globally but assumes Western article-consumption patterns - **Network vs isolation:** This is an individual consumption tool - doesn't help isolated members connect with others or discover community content **Against BLKOUT wishlist:** This doesn't map to any of the fifteen wishlist items. BLKOUT needs infrastructure for community building, member experience, and co-production. Pocket is a personal productivity tool for information workers - it's category-adjacent to what BLKOUT is building, not supportive of it. **The deeper problem:** Pocket serves people who already have information abundance and need better curation. BLKOUT members who are isolated, newly out, or struggling with basic needs aren't drowning in articles to save - they need human connection, immediate resources, and community discovery. This tool optimizes for the information-rich, not the connection-poor. **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).