// verdict #17 · 6 Aug 2026 · 10:24 UTC

www.sanity.io/

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 Sanity as a "Content Operating System" for BLKOUT — this is a headless CMS with AI features, targeting enterprise content operations. **VENDOR LOCK-IN CONCERNS** This is proprietary SaaS with no self-hosting option. While they offer data export capabilities, the entire content architecture would be built around their APIs and data structures. Migration off Sanity would mean rebuilding content infrastructure from scratch. For a community benefit society focused on data sovereignty, this creates dangerous dependency. **GUARDRAIL VIOLATIONS** - **Schema ownership**: Sanity maintains its own content schema. The guardrail states "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." Sanity would create a parallel content system outside the CRM. - **Infrastructure before application**: This adds significant operational complexity before foundational infrastructure is stable. Tier 1 priority is "Tech stability and system resilience" — Sanity introduces new dependencies when the VPS and Coolify setup needs solidifying first. **OPERATIONAL OVERHEAD** Enterprise-grade CMS with substantial learning curve. The "Content Agent" and AI features suggest this is built for teams with dedicated content operations staff. BLKOUT's small team would be adopting a tool designed for organizations like Shopify and Spotify — massive operational overhead mismatch. **SEQUENCING PROBLEMS** Nothing on the wishlist suggests BLKOUT needs a headless CMS right now. The closest items are "Unique member pages" (Tier 3) and general web presence, but those don't require enterprise content operations. This tool doesn't unlock any Tier 1 or Tier 2 capabilities — it's solving problems BLKOUT doesn't have yet. **SURVEILLANCE MECHANICS** While not explicitly extractive, Sanity collects extensive usage analytics and content metadata. Their AI features would process BLKOUT's content through their systems. For an organization developing an AI policy "à la New Public," adopting AI-powered content tools before that policy exists is backwards sequencing. **CATEGORY MISMATCH** This is built for e-commerce sites, media companies, and SaaS platforms that need to manage thousands of content pieces across multiple channels. BLKOUT's current content needs (member pages, basic web presence) don't justify enterprise CMS infrastructure. The master's tools problem is clear here: Sanity would make BLKOUT dependent on a proprietary platform designed for extractive business models, before BLKOUT has determined its own content strategy or AI principles. **RECOMMENDATION: PASS**

// 02 · ethicist

Murray

pass

values, sovereignty, community benefit.

Looking at Sanity.io through BLKOUT's values and operational context, I see significant structural misalignment that makes this a clear pass. **Data Sovereignty Violation**: Sanity is a proprietary cloud platform that positions itself as "The Content Operating System" — this fundamentally contradicts BLKOUT's principle that members own their data. Content stored in Sanity's "Content Lake" becomes dependent on their infrastructure and subject to their terms. There's no indication of member data portability or the transparency mechanisms that would be required for BLKOUT's "unique member pages" wishlist item. **Guardrail Conflicts**: This directly violates the "Schema ownership" guardrail. Sanity would create its own content schema separate from the authoritative CRM schema in `001_crm_complete_schema.sql`. Any integration would require maintaining parallel data structures, exactly what the guardrails prevent. **Operational Complexity**: Sanity adds significant infrastructure complexity when BLKOUT's "Infrastructure before application" guardrail prioritizes debugging existing services (CPU, disk, Docker images) before adding new ones. The platform appears designed for enterprise content operations, not a small CBS building foundational systems. **Wishlist Mismatch**: Looking at the fifteen-item wishlist, nothing maps to a headless CMS need. The closest items are "CRM — values-embedded member system" (already built) and "unique member pages" (requires member data control, not content management). Sanity solves problems BLKOUT doesn't have while creating dependencies that conflict with what they're actually building. **Commercial Lock-in**: Despite marketing to developers, Sanity's business model depends on platform lock-in. The "Content Agent" and AI features suggest surveillance-adjacent capabilities that could conflict with BLKOUT's anti-surveillance principles. There's no indication this supports the transparency and member control that BLKOUT's values require. **Resource Misallocation**: BLKOUT needs "AI policy," "tech stability," and "compliance infrastructure" — foundational work. Sanity is a sophisticated content platform that would consume attention and resources without addressing any Tier 1 priorities. This is a category mismatch. Sanity is built for content-heavy applications with complex editorial workflows. BLKOUT needs member-controlled data systems and community infrastructure, not enterprise content management. RECOMMENDATION: PASS

// 03 · builder

Rustin

pass

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

Looking at Sanity as a "Content Operations Platform" for BLKOUT... ## VIBE-CODEABILITY Sanity has excellent DX reputation - React-based Studio, good TypeScript support, solid documentation. The `npm create sanity@latest` suggests straightforward onboarding. However, it's a headless CMS that requires frontend development to be useful, which means significant implementation work beyond just "installing Sanity." ## STACK COMPATIBILITY Sanity is cloud-hosted (not self-hostable), which creates a dependency outside the Coolify VPS setup. It integrates via APIs, so it would work alongside the existing stack, but it doesn't "live" in the infrastructure BLKOUT controls. ## GUARDRAIL CHECK **This hits a major guardrail violation**: "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." Sanity is fundamentally about maintaining its own content schema and data model. It's designed to be the source of truth for content, not a consumer of existing database schemas. You'd either duplicate member data into Sanity or create complex sync mechanisms. ## WISHLIST MAPPING Looking at the fifteen capabilities, Sanity doesn't clearly map to any specific wishlist item. It's a general-purpose CMS, but BLKOUT's needs are more specific: - The **CRM** is already built and in use - **Member pages** need to read from the existing CRM schema - **Directory** and **AIvor** would benefit from structured content, but they need to integrate with the CRM, not replace it - **Events calendar** could use content management, but again needs CRM integration ## LIFT ASSESSMENT Significant. Sanity isn't just a tool you deploy - it's a platform you build on top of. Creating the Studio interface, defining schemas, building frontend components to consume the API, and integrating with existing systems would be a major undertaking. ## MAINTAINABILITY Once set up, Sanity is quite maintainable. But the integration complexity with the existing CRM-centric architecture would create ongoing maintenance overhead. ## INTEGRATION POTENTIAL Poor fit for BLKOUT's current architecture. Sanity wants to be the content hub, but BLKOUT already has a CRM as the member data hub. Creating clean integration between them without violating the schema ownership guardrail would be very difficult. Sanity is a powerful platform, but it's solving a different problem than what BLKOUT has. BLKOUT needs tools that enhance and integrate with the existing CRM-centric architecture, not a separate content platform that would fragment the data model. **RECOMMENDATION: PASS**

// 04 · inclusion

Rivera

pass

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

Looking at Sanity as a content management platform for BLKOUT, I need to cut through the enterprise marketing speak and ask: **WHO IS THIS TOOL NOT FOR?** ## ACCESSIBILITY FLOOR — FAIL Sanity assumes technical literacy that excludes most community members. The homepage leads with `npm create sanity@latest` — that's a developer command line instruction. The "Content Studio" requires understanding of schemas, APIs, and structured content. A community member who wants to share their story, update an event, or contribute to the directory would need either coding knowledge or a developer intermediary. This creates a bottleneck where content creation becomes gatekept by technical capacity. ## PRIVACY ARCHITECTURE — MIXED The platform offers granular permissions and can be self-hosted, which is good for protecting member data. But the complexity means privacy settings require technical expertise to configure properly. A closeted member or asylum seeker needs simple, obvious privacy controls — not enterprise-grade permission matrices they can't navigate. ## PERFORMANCE DEMANDS — FAIL This is built for professional content teams, not community voices. The interface assumes you're comfortable with content modeling, API endpoints, and structured data. It demands articulacy in technical language, not human language. Someone wanting to share their experience of loneliness or contribute to the Black queer directory shouldn't need to understand "document schemas" first. ## COST TO USER — CONCERNING While there's a free tier, the moment BLKOUT scales beyond basic usage, this becomes expensive fast. The pricing jumps to $99/month for teams, then enterprise rates. For a community benefit society operating on CBS tiers of £3-£10/month, this cost structure is completely misaligned. ## REGISTER — FAIL Everything about Sanity speaks in tech industry language. "Content Operations Platform," "Content Lake," "Agent API" — this vocabulary excludes anyone who isn't already in the room with developers. Community members need tools that speak their language, not corporate buzzwords. ## MEMORY vs RE-EXPLANATION Sanity does remember content and user permissions, which is good. But accessing that memory requires navigating complex interfaces that force constant re-learning for non-technical users. ## ISOLATION vs NETWORK — MAKES WORSE This tool deepens isolation by requiring technical mediation for community participation. Instead of helping someone who is alone reach others, it puts a developer between them and their ability to contribute to community resources. ## AGAINST BLKOUT'S GUARDRAILS This violates the **"Schema ownership"** guardrail. Sanity wants to be the authoritative schema — it's literally called a "Content Lake" where everything flows through their data model. BLKOUT's CRM schema should remain authoritative, with tools reading from those tables, not replacing them. ## AGAINST BLKOUT'S WISHLIST This doesn't map to any wishlist item. The **"CRM — values-embedded member system"** already exists and should be developed with transparency principles. The **"Live directory"** needs to be "built by the community, kept live by the community" — Sanity's technical barriers make that impossible. Sanity serves the over-served — funded startups with developer teams. It abandons everyone else on the street: community members who want to contribute but can't code, organisations without technical budgets, voices that need platforms but not programming languages. 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).