// verdict #5 · 14 May 2026 · 21:56 UTC

notion.so/

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.

**NOTION EVALUATION** **VENDOR LOCK-IN CONCERNS** Notion is a proprietary platform with notoriously poor data export capabilities. While they offer CSV/HTML exports, the structured databases, linked relations, and embedded content don't translate cleanly. You can get your text out, but the organizational logic dies in translation. This creates exactly the kind of dangerous dependency that calcifies over time. **GUARDRAIL VIOLATIONS** This doesn't directly violate any Year One guardrails, but it sits uncomfortably close to the "Schema ownership" principle. While Notion wouldn't touch the CRM's `001_crm_complete_schema.sql`, it would create a parallel information architecture that could fragment where BLKOUT's authoritative data lives. **OPERATIONAL OVERHEAD** Notion's learning curve is deceptive — it appears simple but becomes complex fast. For a small team, the maintenance cost of keeping databases organized, permissions managed, and templates updated can become significant. The risk is that it becomes another system to maintain rather than a tool that reduces cognitive load. **WISHLIST MAPPING** I don't see clear mapping to any specific wishlist items. The closest might be "Partner tool and project management dashboard" (Tier 2), but Notion's strength is internal organization, not transparent external partnerships. For compliance infrastructure, Notion's audit trails are weak compared to purpose-built tools. **SEQUENCING CONCERNS** This feels premature. The wishlist prioritizes "Tech stability and system resilience" in Tier 1 — adding another platform to manage before the core infrastructure is solid violates the "infrastructure before application" ordering principle. **ALTERNATIVE CONSIDERATION** If the need is project organization, the existing Coolify environment could host open-source alternatives like Outline, BookStack, or even a simple Git-based wiki that integrates with the existing infrastructure stack. The fundamental question: what specific organizational problem would Notion solve that can't be addressed with tools that maintain data sovereignty and integrate with the existing infrastructure? **RECOMMENDATION: PASS**

// 02 · ethicist

Murray

pass

values, sovereignty, community benefit.

I need to evaluate Notion against BLKOUT's values and the specific wishlist and guardrails. **Data Sovereignty Concerns**: Notion is a proprietary cloud service where BLKOUT would not own or control member data. All content lives on Notion's servers under their terms of service. This directly conflicts with the principle that "members own their data" and the organisation "holds it in trust, not as an asset." **Schema Ownership Guardrail Violation**: The guardrails explicitly state "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." Notion would create its own data structure completely separate from the authoritative CRM schema. **Surveillance and Transparency Issues**: Notion's collaborative features include extensive tracking of who viewed what and when. While marketed as productivity features, these create surveillance mechanics that could erode trust. Members would have no visibility into what analytics Notion collects about their engagement. **Open-Source Alignment**: Notion is entirely proprietary and opaque. There's no way to audit how it handles data, no export guarantees, and complete vendor lock-in. **Wishlist Mapping**: Looking at the specific wishlist items, Notion doesn't clearly map to any of them. It's not the "AI policy" (Tier 1), not the member-controlled "unique member pages" (Tier 3), not the "CRM values-embedded member system" (Tier 1) which already exists. It's a generic productivity tool that doesn't address BLKOUT's specific community-focused needs. **Community Benefit vs Extraction**: Notion extracts value (data, engagement patterns, subscription fees) while providing generic productivity features that don't specifically serve Black queer communities. The benefit flows to Notion's shareholders, not to BLKOUT's community. **Alternative Path**: BLKOUT already has infrastructure (Coolify, Supabase) that could support collaborative documentation through open-source alternatives that respect data sovereignty. This is a clear case where commercial convenience would undermine foundational principles. The data sovereignty violation alone disqualifies it, but the schema guardrail makes it doubly problematic. RECOMMENDATION: PASS

// 03 · builder

Rustin

pass

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

Looking at Notion for BLKOUT's context and needs. ## Technical Assessment **VIBE-CODEABILITY**: Notion has excellent UX but limited technical integration options. The API exists but is notoriously slow and has strict rate limits. Building custom integrations requires patience with their webhook system and relatively clunky database operations. **STACK COMPATIBILITY**: Notion is purely SaaS — no self-hosting, no Coolify deployment. This creates an external dependency that can't be managed within BLKOUT's VPS infrastructure. API integrations would need to run from the existing stack. **SPEED OF DEPLOYMENT**: Immediate for basic use cases (wiki, project tracking, documentation). Custom integrations take longer due to API limitations and the need to work around Notion's database model quirks. ## Wishlist Mapping This could potentially serve: - **Partner tool and project management dashboard** (Tier 2) — Notion excels at project management and could handle partner relationship tracking - **Compliance infrastructure — demonstration not monitoring** (Tier 2) — Good for creating governance documentation and evidence trails However, there's a significant gap: Notion doesn't naturally integrate with the **CRM — values-embedded member system** that's already in active use. The guardrail states "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." Notion would create a parallel information system rather than extending the existing CRM foundation. ## Capacity Reality Check **LIFT ASSESSMENT**: Moderate for basic use, significant for meaningful CRM integration. The API work required to keep Notion in sync with Supabase tables would be ongoing maintenance overhead. **MAINTAINABILITY**: Notion itself is maintained by Notion. Custom integrations become technical debt that needs developer attention when APIs change or rate limits shift. **INTEGRATION POTENTIAL**: Limited. Notion works best as a standalone tool, which conflicts with BLKOUT's integrated approach centered on the CRM schema. ## The Real Question Notion solves project management and documentation well, but BLKOUT already has infrastructure for the data that matters most (member relationships, events, directory). Adding Notion creates information silos rather than strengthening the integrated system that's being built. For partner management specifically, building lightweight partner tracking into the existing CRM would be more aligned with the "schema ownership" guardrail and create better long-term integration potential. RECOMMENDATION: PASS

// 04 · inclusion

Rivera

pass

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

Looking at Notion for BLKOUT — let me cut through the productivity hype and ask the hard questions about who this actually serves. **ACCESSIBILITY FLOOR FAILURES** Notion assumes reliable internet, modern devices, and comfort with complex interfaces. The nested page structure, database views, and endless customization options create cognitive load that excludes people with learning differences, digital literacy gaps, or older devices. A closeted person using a shared computer can't easily navigate Notion's interface quickly or privately. **PRIVACY ARCHITECTURE CONCERNS** Notion's collaboration features are a surveillance risk. Edit histories, comment threads, and "who viewed this" tracking expose patterns of engagement. For asylum seekers or people in unsafe households, Notion's default transparency could be dangerous. The platform's US hosting raises data sovereignty questions for UK community data. **PERFORMANCE DEMANDS** Notion rewards people who enjoy building systems — the wiki-builders, the database designers, the template creators. It punishes people who just need information quickly. The culture around Notion celebrates elaborate setups that become barriers for anyone who isn't already comfortable with productivity tools. **SYNC vs ASYNC MIXED BAG** Notion does respect variable capacity through asynchronous editing, but its complexity means people need significant time investment to become functional users. Quick check-ins become impossible when everything lives behind multiple navigation layers. **REGISTER AND LANGUAGE** Notion's interface language assumes familiarity with database terminology, project management concepts, and productivity culture. It doesn't work outside English effectively, and its learning curve excludes people who haven't already adopted Silicon Valley work patterns. **GEOGRAPHIC AND COST BARRIERS** Free tier has severe limitations for community use. Paid plans assume organizational budgets that grassroots groups outside London often lack. The tool's complexity requires training time that volunteer-run organizations can't provide. **WISHLIST MAPPING** This doesn't clearly map to any specific wishlist item. It's a general-purpose tool being proposed without specific BLKOUT context. The "Partner tool and project management dashboard" need could theoretically be met by Notion, but that wishlist item specifically calls for something that "sits on stable infrastructure" — Notion is external SaaS that adds operational dependency. **GUARDRAIL VIOLATIONS** Potentially violates "Infrastructure before application" — Notion adds operational complexity (user management, permissions, training) before BLKOUT has confirmed its foundational systems are stable. **WHO IS THIS NOT FOR?** - People who need information quickly without learning a new system - Community members with older devices or intermittent internet - Anyone who finds complex interfaces overwhelming - People who can't afford the time investment to become proficient - Those who need privacy from household members or immigration authorities - Grassroots groups without training budgets - People whose first language isn't English - Anyone who just wants to find an event time or contact detail without navigating a database Notion serves the over-served: the already-organized, the digitally fluent, the people who have time to build systems. It's a tool for people who are already in the room, not for getting people off the street. 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).