Based Resilience House Applicability Report
Readiness verdict
The local design powerset is ready for immediate local use in the BRH production lane as design heuristics, page structures, prompt blocks, and proof-pack patterns.
It is not yet a canonical shared MGA14 design skill because the external Refero and Mobbin corpora were not locally mirrored and no GitHub-first filing has occurred.
Safe to apply now
1. Investor/client-room information architecture.
2. Proof-card layout for de:hub, RESIHLOG, cap table, financing, public-support, and transcript evidence.
3. Package readiness dashboard.
4. Open-gates dashboard.
5. Pitch deck section architecture.
6. Source-card and document-card visual pattern.
7. Access-tier labels: `matias-only`, `customer-view`, `investor-version`.
8. Cutoff banner: `Information cutoff: Sunday 03 May 18:00 CET`.
9. Mobbin-inspired interaction patterns for document library browsing, readiness dashboards, onboarding, and membership-tier comparisons.
Recommended BRH page sections
1. Hero: "Resilience House investor package"
2. Cutoff and access tier
3. Package status
4. New-product framing
5. Evidence-backed validation
6. Product architecture
7. Financing and cap table
8. Public-support scenario
9. Proof pack
10. Open release gates
11. Documents
12. Contact / next step
Mobbin-inspired components to use for BRH
| Component | BRH use |
|---|---|
| Onboarding / intro flow | Explain who can access the room, what the cutoff is, and what is review-gated |
| Searchable document library | Let MC or later investor-view users filter files by status, topic, source, and access tier |
| Status cards | Show `ready`, `review-gated`, `blocked`, and `needs owner` states |
| Membership tier cards | Present Resilience House Community tiers and strategic/free seats separately |
| Timeline/activity feed | Show Phase 1, Phase 2, latest source batch, and next gate actions |
| Empty/blocked states | Show why a document is unavailable instead of hiding it |
Recommended proof cards for BRH
| Proof card | Source | Status |
|---|---|---|
| BMWK de:hub admission | `241112 Bestaetigung Digital Hub Security and Defence.pdf` | supported |
| Resilience House new-product framing | transcript + financing memo | supported |
| MSB/BASED as validation/reach | transcript + prior materials | supported with caveat |
| Cap table / round terms | cap-table workbook + Einstein memo | partly supported; legal review gated |
| RESIHLOG application | RESIHLOG PDFs | supported as application; award not proven |
| Public-support amounts | RESIHLOG / Bavarian request docs | supported as request/application; not base-case revenue |
| Cloudflare documents area | Wrangler check | blocked pending auth |
Design integration for investor documents
- Executive summary: use concise proof-backed blocks, not long narrative.
- Pitch deck: use one claim per slide, one evidence note per claim, and visible gate status for financial/legal claims.
- Data room: use cards grouped by status and access tier.
- Model dashboard: separate forecast, actuals, scenario, and public-support funds.
Production signal
- Ready for local use: yes.
- Safe immediate use for BASED: yes, as design and structure guidance.
- Needs GitHub-first filing before canonical status: yes.
- External Refero/Mobbin-derived claims: gated until source corpus is properly ingested and licensed/attributed as appropriate.
MGA14 Design Powerset Index
Purpose
Create a local design-powerset seed that can be applied immediately to the Based Resilience House investor package, client-room, proof-pack, and Cloudflare documents area without claiming canonical shared-skill status.
Powerset modules
| Module | Use | BASED application |
|---|---|---|
| DESIGN.md capture | Convert visual/design references into reusable design DNA | Define a consistent investor-room visual language |
| Token normalization | Turn type/color/spacing/motion into repeatable rules | Keep deck, memo, proof-pack, and webviewer coherent |
| Skill/harness packaging | Convert design process into agent-runnable prompt blocks | Later package as canonical MGA14 design skill |
| Anti-pattern review | Detect front-end/design slop, inconsistent hierarchy, vague UI | Review Cloudflare client-room pages and pitch sections |
| Investor-room shell | Structure documents around navigation, proof, gates, and calls to action | BRH matias-only data room / investor-version later |
| Proof-pack cards | Present claims with source links, status, and access tier | de:hub proof, RESIHLOG, cap-table, public-support evidence |
| Status dashboard | Summarize readiness, blockers, and release gates | Investor package completion dashboard |
| Narrative section design | Use repeated section frames for problem, product, proof, model, ask | BRH pitch deck and executive memo |
| Mobbin reference patterns | Use app/web UI screenshots as flow and component inspiration | Client-room navigation, onboarding, status cards, search/filter, document dashboards |
Index principles
1. Use design as governance, not decoration.
2. Every investor-facing claim must have a visible proof state.
3. Every source reference shown to a reader must be clickable or explicitly marked unavailable/blocked.
4. Working outputs default to `matias-only`.
5. `customer-view` or `investor-version` requires MC approval evidence.
6. Shared powerset canonicalization requires GitHub-first filing.
7. Mobbin and Refero references may guide local design choices, but external corpus capture or reuse must be source-verified before canonical packaging.
Design Pattern Taxonomy
1. Information architecture
- Top navigation: Overview, Package, Evidence, Model, Gates, Documents, Contact.
- Secondary filters: `all`, `ready`, `review-gated`, `blocked`, `source-needed`.
- Document grouping: narrative, finance, legal/governance, public-support, proof-pack, transcript/source.
2. Visual hierarchy
- Use a calm institutional layout: high contrast, generous spacing, low-noise backgrounds.
- Prefer evidence cards and tables over long unstructured prose.
- Use status chips for release state:
- `ready-internal`
- `founder-input`
- `review-gated`
- `blocked`
- `investor-ready`
3. Proof-card pattern
Each proof card should include:
- Claim
- Evidence source
- Access tier
- Gate status
- Reader link or unavailable/blocked note
- Approved wording
- Risk note
4. Investor narrative section pattern
Use repeatable sections:
1. Problem / market dislocation
2. Product / platform
3. Why now
4. Why BASED can launch it
5. Evidence and validation
6. Business model
7. Financing and use of funds
8. Governance and caveats
9. Ask / next step
5. Dashboard pattern
For the BRH project dashboard:
- Package status
- Cutoff date
- Latest source batch
- Gates open/closed
- Documents ready
- Documents blocked
- Next owner actions
- Cloudflare upload/auth status
6. Anti-patterns to avoid
- Claim cards without source links or blocked notes.
- Mixing base-case revenue with public-support scenario funds.
- Presenting BASED/MSB history as direct Resilience House operating history.
- Overusing "exclusive", "mandated", or "official" without exact source wording.
- Hiding release gates in footnotes.
- Mixing `matias-only`, `customer-view`, and `investor-version` assets on one page without labels.
7. Mobbin-derived reference categories
Use Mobbin as an external inspiration source for:
- onboarding flows that explain access tier, information cutoff, and document status;
- dashboard cards that show readiness, blockers, owner, and next action;
- search/filter interfaces for evidence packs and document libraries;
- pricing / membership plan comparison layouts adapted for Resilience House Community tiers;
- mobile-first navigation patterns for investor/client-room access;
- empty-state and blocked-state UI for documents awaiting approval;
- compact activity timelines for new information batches and release-gate changes.
Do not copy screenshots or proprietary UI assets. Use pattern abstraction only unless a separate source-rights review approves otherwise.
Reusable Prompt Blocks
Extract design DNA
```text
Read the source page or document set and extract its design DNA: typography, color, spacing, grid, component patterns, motion, tone, hierarchy, navigation, content density, and anti-patterns. Convert the result into a DESIGN.md-style spec with tokens, component rules, and usage constraints.
```
Normalize to token system
```text
Turn this design reference into reusable tokens: colors, type scale, spacing scale, border radius, shadows, icon treatment, status chips, evidence cards, tables, and document cards. Keep the output implementation-agnostic and suitable for a Cloudflare Pages investor room.
```
Audit for investor-room anti-patterns
```text
Review this investor/client-room page for design and governance anti-patterns: unsupported claims, unclear access tier, missing source links, weak visual hierarchy, mixed release states, excessive copy density, hidden caveats, and unclear next action. Return only actionable fixes.
```
Build BRH proof-pack layout
```text
Create a proof-pack layout for Based Resilience House. Each card must show: claim, approved wording, source file, evidence status, release gate, access tier, clickable source or blocked note, and risk/caveat. Default access tier is matias-only.
```
Build BRH investor dashboard
```text
Create a Based Resilience House investor-package dashboard with sections for package readiness, information cutoff, current source batch, open release gates, documents ready, blocked documents, Cloudflare upload status, and next owner actions.
```
Abstract Mobbin patterns
```text
Use Mobbin only as a reference for interaction and layout patterns. Abstract reusable patterns for onboarding, status dashboards, document libraries, proof cards, pricing/membership tiers, mobile navigation, search/filter, and blocked states. Do not copy proprietary screenshots or visual assets. Return original BRH-specific components with access-tier labels and source-proof requirements.
```
Apply BRH narrative design
```text
Rewrite the investor narrative into a clean sectioned format: market dislocation, new platform product, validation/reach, product architecture, business model, financing readiness, public-support caveat, proof pack, and next step. Do not present BASED/MSB history as Resilience House operating history.
```
This page is a sanitized working update. Raw Phase 2 PDFs, audio, and workbook files are not published here because the pages.dev URL is public even though client-room.collanlaw.com is Cloudflare Access protected.