// verdict #2 · 13 Apr 2026 · 19:01 UTC

lumalabs.ai/

PASS

two or more voices said no. release without guilt.

submitted by Rob · model anthropic/claude-sonnet-4 · against wishlist of 2026-04-13T17:49:02z · visit the tool → · back to history

// the three voices, in parallel

What the Council said

// persona 01

The Skeptic

pass

technical risk, lock-in, sequencing.

Looking at Luma Labs AI - this is a 3D content generation platform that creates photorealistic 3D models and scenes from text prompts or images. **GUARDRAIL VIOLATIONS:** None directly, but this raises immediate sequencing concerns against the "Infrastructure before application" guardrail. The platform isn't even stable yet - you're still working on tech stability and system resilience as a Tier 1 priority. **WISHLIST MAPPING:** This doesn't map to any item on the fifteen-capability wishlist. The closest might be future enterprise/wealth activities under Tier 3, but that's "still forming" and explicitly requires co-design with community first. 3D content generation is not identified as a community need or organizational capability gap. **TECHNICAL CONCERNS:** - **VENDOR LOCK-IN**: Complete dependency on Luma's proprietary models and infrastructure. No export standards for 3D assets, no open-source alternative pathway. - **OPERATIONAL OVERHEAD**: Subscription costs, learning curve, and integration complexity for a capability that serves no identified organizational need. - **SEQUENCING**: This is a solution looking for a problem. You have Tier 1 infrastructure work (CRM development, AI policy, system resilience) and Tier 2 member experience work (events calendar, directory, lead generation) that directly serve identified community needs. 3D content generation doesn't unblock any of these. **SURVEILLANCE MECHANICS**: Luma processes uploaded images and prompts through their models. For a community benefit society focused on data sovereignty, adding another AI vendor that processes member-adjacent content without clear necessity is questionable. **CAPACITY REALITY CHECK:** Your team is small and working on foundational infrastructure. Adding 3D content generation capability when you don't have stable bookkeeping, compliance systems, or even a reliable events calendar is premature optimization. This tool might have value for creative organizations with different priorities, but it doesn't serve BLKOUT's current mission-critical needs or map to any identified community requirement. RECOMMENDATION: PASS

// persona 02

The Ethicist

pass

values, sovereignty, community benefit.

I've reviewed Luma Labs AI, which appears to be a 3D AI generation platform that creates 3D models, scenes, and videos from text prompts or images. ## Values Assessment **Data Sovereignty**: Luma's terms indicate they retain broad rights to user-generated content and training data. Users upload images/prompts, and the service processes these through proprietary AI models. This creates potential data sovereignty issues, particularly if BLKOUT members' images or content were used as inputs. **Anti-Surveillance**: The tool itself isn't surveillance-oriented, but the data collection practices around user inputs and generated content lack transparency about retention, usage, and potential training applications. **Community Benefit**: Luma is a commercial 3D generation service. While 3D content could theoretically benefit community projects, this specific tool doesn't align with community-controlled or community-beneficial technology. **Open-Source Alignment**: Luma is entirely proprietary with opaque AI models and closed infrastructure. ## Wishlist and Guardrails Analysis Looking at BLKOUT's fifteen-item wishlist, **Luma doesn't map to any specific capability BLKOUT is trying to build**. The wishlist focuses on: - Infrastructure (AI policy, tech stability, compliance) - Member experience (CRM, member pages, events, lead generation) - Co-production (directory, network mapping, consultation processes) 3D content generation doesn't appear in any tier or category. The closest potential connection might be supporting "Regular events calendar" with visual content, but this would be a significant stretch and expensive overkill for event promotion needs. **Guardrails compliance**: No direct violations, but the tool doesn't serve any identified organizational need, making it essentially irrelevant to Year One priorities. ## Missing Foundation Most critically, Luma would require BLKOUT to have an **AI policy** first (Tier 1, "do now" priority). The wishlist explicitly states this "unlocks the integrity of everything beneath it" and "determines what BLKOUT will and won't do with AI, and why." Adopting AI tools before establishing this policy violates the strategic sequencing BLKOUT has set for itself. ## Conclusion While not actively harmful, Luma represents exactly the kind of shiny commercial AI tool that can distract from foundational work. BLKOUT has clearly prioritized infrastructure, member systems, and community co-production capabilities. 3D generation doesn't serve any of these priorities and would consume resources better directed toward the actual wishlist. RECOMMENDATION: PASS

// persona 03

The Builder

pass

vibe-codeability, stack fit, lift.

## The Builder's Assessment: Luma Labs AI Looking at Luma Labs AI — this is a 3D content generation platform that creates 3D models, scenes, and videos from text prompts or images. Think of it as "Midjourney but for 3D assets." ### Wishlist Mapping I've read through BLKOUT's fifteen-item wishlist carefully, and **Luma Labs doesn't map to any of the prioritized capabilities**. The wishlist is focused on: - Infrastructure (AI policy, tech stability, compliance) - Member experience (CRM, events calendar, member pages) - Co-production (directory, network mapping, consultation processes) 3D content generation isn't mentioned anywhere. This is a creative tool, but BLKOUT's current priorities are foundational systems and community infrastructure. ### Technical Assessment **VIBE-CODEABILITY**: Actually quite good. Luma has clean APIs and decent documentation. The DX is straightforward for what it does. **STACK COMPATIBILITY**: This is where it gets tricky. Luma is a cloud service that would integrate via API calls, so no containerization issues. But it's resource-intensive on the generation side and would require handling large 3D file assets. **SPEED OF DEPLOYMENT**: Fast to get basic integration running — could have 3D generation working in a day or two. **LIFT ASSESSMENT**: Moderate lift for basic integration, but significant lift to make it meaningfully useful. You'd need: - Asset storage and management system - Frontend for displaying 3D content - Use case definition (what would BLKOUT actually do with 3D models?) **MAINTAINABILITY**: Low maintenance once set up, since it's a managed service. Main risk is API changes or pricing shifts. ### The Real Question The fundamental issue isn't technical capability — it's **purpose alignment**. What would BLKOUT actually use 3D content generation for? Event visualization? Community art projects? Member avatar creation? Without a clear use case that connects to the wishlist priorities, this becomes a "cool tech looking for a problem" situation. BLKOUT is in Year One infrastructure building mode, not experimental creative tools mode. ### Guardrail Check No direct guardrail violations, but this doesn't advance any of the Tier 1 "do now" priorities that are supposed to be the focus. This is a capable tool that doesn't solve any of BLKOUT's current problems. Come back to it when the foundational infrastructure is solid and there's a specific creative project that needs 3D assets. **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