@rubytech/create-maxy-code 0.1.96 → 0.1.98

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy-code",
-  "version": "0.1.96",
+  "version": "0.1.98",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy-code": "./dist/index.js"

package/payload/platform/plugins/.claude-plugin/marketplace.json

@@ -39,6 +39,11 @@
       "source": "./email",
       "version": "0.1.0"
     },
+    {
+      "name": "founder-pack",
+      "source": "./founder-pack",
+      "version": "0.1.0"
+    },
     {
       "name": "linkedin-extension",
       "source": "./linkedin-extension",

package/payload/platform/plugins/founder-pack/.claude-plugin/plugin.json

@@ -0,0 +1,8 @@
+{
+  "name": "founder-pack",
+  "description": "founder-pack plugin",
+  "version": "0.1.0",
+  "author": {
+    "name": "Rubytech LLC"
+  }
+}

package/payload/platform/plugins/founder-pack/skills/investor-data-room/SKILL.md

@@ -0,0 +1,218 @@
+---
+name: investor-data-room
+description: Use when a UK-domiciled founder needs to produce a full seed-raise pack from idea to deliverables: graph-structured data room, 15-section business plan, 12-slide deck blueprint, print-ready HTML+PDF for both. Trigger phrases include "build me a data room", "draft a business plan", "deck from the business plan", "print-ready PDF for the prospectus", "from office hours to investor pack", "set up the fundraise repo". The skill never speculates on financial figures or cap-table values: every number traces to a Companies House filing, a financial model worksheet, or a source citation. Public-facing artefacts contain zero internal workings (no "reconciliation pending", no "open Q" markers, no comparison-to-baseline commentary). Design tokens are harmonised across business plan, deck, and prospectus per `realagent-site/.docs/design-tokens.md`.
+allowed-tools:
+  - Bash
+  - Read
+  - Write
+  - Edit
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+---
+
+# investor-data-room
+
+Build a UK seed-raise pack in five stages. Each stage has an outcome contract; do not advance until the contract is met.
+
+## Outcome contract (whole skill)
+
+Complete when the data room contains:
+
+```
+<project-site>/.docs/data-room/
+  README.md                                 # data-room index, status snapshot, doctrine
+  01-narrative/
+    office-hours-design.md                  # ideation working scratchpad
+    business-plan.md                        # 15-section business plan
+    deck-blueprint.md                       # 12-slide blueprint
+  02-corporate-legal/
+    README.md                               # incorporation filings, articles, board minutes
+    incorporation-<co-house-no>-<date>.pdf  # IN01 + statement of capital + cap table
+  03-cap-table/
+    README.md                               # pre/post-investment cap table with PSC notes
+  04-financials/
+    README.md
+    model_worksheet.md                      # opening cash, capex, burn, MRR ramp, two-round
+  05-commercial/
+    README.md
+    <gtm-partner-1>.md                      # one file per named partner
+    <gtm-partner-1>-proposal.pdf
+  06-product-ip/
+    README.md
+    encrypted-document-sharing.md           # if applicable
+  07-team/
+    README.md
+    <founder-1>.pdf                         # CV per foregrounded founder
+  08-market/
+    README.md
+    sources.md                              # every market figure with citation
+    competitor-value-claims-rebuttal.md
+  09-operations/
+    README.md
+  10-supporting/
+    README.md
+  html/
+    business-plan/
+      index.html                            # A4 portrait, design tokens, premium register
+      render-pdf.mjs                        # Playwright + img2pdf + qpdf pipeline
+      business-plan.pdf                     # rendered output
+      logo-light.png logo-dark.png
+    prospectus/
+      index.html
+      render-pdf.mjs
+      prospectus.pdf
+    deck/                                   # NOT YET BUILT in the reference project
+      index.html
+      render-pdf.mjs
+      deck.pdf
+```
+
+Skip stages that are already complete; do not regenerate stale artefacts blindly.
+
+## Stage 1 — Office-hours ideation
+
+Drive a conversational discovery session using the `/office-hours` skill (or equivalent YC-style forcing questions: demand reality, status quo, desperate specificity, narrowest wedge, observation, future-fit). Output a single `office-hours-design.md` capturing:
+
+- Problem statement
+- Demand evidence (with numbers and dates)
+- Status quo
+- Target user and narrowest wedge
+- Constraints
+- Six to eight numbered premises (founder-confirmed)
+- Two to four narrative-shape alternatives with a recommendation
+- Financials / use-of-funds placeholders flagged as open questions
+- Founder Signal Reflection
+
+This file is the working substrate. It stays internal-only. Every later artefact derives from it.
+
+**Doctrine.** Never speculate on numbers; flag them as open questions until the founder confirms.
+
+## Stage 2 — Data room scaffold
+
+Build the directory tree above. Each section gets a `README.md` that doubles as a content checklist (purpose, expected contents, current state, gaps). The graph structure is fixed: ten numbered sections (`01-narrative` through `10-supporting`) plus a top-level README and an `html/` subdirectory for rendered deliverables.
+
+**File-naming conventions:**
+
+- `<co-house-no>` for Companies House filings (e.g. `incorporation-17237239-2026-05-22.pdf`).
+- `<founder-firstname>-<lastname>.pdf` for CVs.
+- `<gtm-partner>.md` + `<gtm-partner>-proposal.pdf` for each commercial partner.
+- All `README.md` files are markdown only.
+
+**Where the published URL lives.** If the project hosts a public prospectus or marketing microsite, keep the published artefacts at a stable path (e.g. `realagent.chat/sites/<slug>/`); the rendered HTML inside `html/<artefact>/index.html` is the source of truth and republishes from there.
+
+References: `references/data-room-structure.md` for the section-by-section purpose statements.
+
+## Stage 3 — Business plan synthesis
+
+Generate `01-narrative/business-plan.md` with **15 sections** following the canonical structure:
+
+1. Executive Summary
+2. Vision and Mission (Vision / Mission / Doctrine triad)
+3. The Company (legal entity table + pre-investment cap table)
+4. The Market (TAM/SAM/SOM + structural tailwind + self-employed wedge + domestic adjacency + international upside + pricing)
+5. The Product (what it is + wedge product + upsell path + substrate moat + conversation ingestion + network + Anthropic asymmetric capture + human-services layer)
+6. The Business Model (revenue streams + unit economics)
+7. Go-to-Market (Wedge → Beachhead → Blitzscale framework + demand evidence + GTM partners + horse-before-cart logic + geography)
+8. Competition (three failing categories + RANL differentiation + most-direct-competitor counter)
+9. Operations (technology stack + data sovereignty + IP ownership chain + compliance posture summary)
+10. Compliance and regulatory positioning (UK consumer protection + UK data/AI regime + EU AI Act + adjacent UK obligations + moat-not-tax close)
+11. Team (founders + strategic shareholders + hiring plan)
+12. Financial Plan (12.1 opening balance sheet through 12.7 use of funds)
+13. Risks and Mitigations
+14. Milestones (the N-month thesis)
+15. The bottom line (summary table + close)
++ Appendices (titled documents only; no internal-only file pointers)
+
+**Critical rules** (all enforced; recurrence is a P0 violation):
+
+- **No internal workings** in body text. No "reconciliation pending", no "open Q", no comparison-to-baseline ("loss has grown from X to Y because…"), no cross-references to `office-hours-design.md` or any working file.
+- **Cap table is authoritative from the IN01.** Reconcile the share-capital line (`500,000 ordinary @ £0.001 nominal` vs `@ £0.01`) before writing the opening balance sheet. Inception premium (e.g. one founder paying £4,500 above nominal) reconciles £5k inception cash against £500 nominal.
+- **Every market figure cites a source.** Maintain `08-market/sources.md` with every figure used in the business plan; the body references "Appendix B" by title, never an internal file path.
+- **Financial figures derive from the model worksheet.** Cite "Appendix A" by title.
+- **No em-dashes between alphabetic words** in user-facing prose (recurring style violation in this project's history; see `references/internal-workings-scrub.md`).
+
+Compliance research is mandatory before drafting Section 10. WebSearch (or equivalent) for: DMCC Act (UK consumer protection for estate-agency), ICO ADM framework (Articles 22A–22D under UK GDPR + ICO 2025 strategy), EU AI Act (force date, high-risk classification for property-financing decisions). Cite each.
+
+References: `references/business-plan-template.md` for the section-by-section template; `references/compliance-research-checklist.md` for the UK + EU regulatory regimes to verify.
+
+## Stage 4 — Deck blueprint synthesis
+
+Generate `01-narrative/deck-blueprint.md` as a **12-slide brief** the deck designer can execute. Each slide has Purpose, Headline (one-line message), Body (bullets + figures pulled from the business plan), Visual suggestion, and Source reference. The 12 slides:
+
+1. Cover (raise headline + founders)
+2. Vision (Vision / Mission / Doctrine)
+3. The Market (TAM + tailwind + wedge)
+4. Business Model (subscription + service layer + unit economics)
+5. Go-to-Market (Wedge → Beachhead → Blitzscale + named partners)
+6. The Product (substrate + wedge + network + asymmetric capture + services layer)
+7. Competition (three failing categories + most-direct counter)
+8. The Team (founders + strategic shareholders)
+9. Economics (P&L summary + cash flow + break-even)
+10. The Raise (size, valuation, dilution, instrument, use of funds, IP transfer, follow-on round)
+11. Milestones (M0 to M-final timeline)
+12. Other Information (compliance + platform dependency + contact)
+
+Production notes attached: format (16:9 landscape, PDF + source deck), design tokens reference (`realagent-site/.docs/design-tokens.md` or project equivalent), chart-source consistency with the financial model, speaker-note attribution.
+
+References: `references/deck-blueprint-template.md`.
+
+## Stage 5 — HTML + PDF render pipeline
+
+For each artefact that ships as a print-ready PDF (business plan, prospectus, deck), produce three files under `html/<artefact>/`:
+
+```
+index.html        # A4 portrait single HTML file, premium design tokens, sectioned by <section class="page">
+render-pdf.mjs    # Playwright + img2pdf + qpdf pipeline (image-only PDF, linearized)
+<artefact>.pdf    # rendered output (regenerate after every HTML edit)
+```
+
+**Hard constraints** (from the `property-brochure:a4-print-documents` skill):
+
+- A4 portrait: `@page { size: A4 portrait; margin: 18mm 16mm 20mm; }`
+- One `<section class="page">` per A4 page; renderer aborts if `scrollHeight` exceeds 1123px + 2px slack.
+- Page numbers via CSS counter in `.page::after { content: counter(pagenum); }`. The renderer screenshots each section, so `@page @bottom-center` rules do NOT propagate.
+- Image-only PDF: Playwright captures one PNG per section at deviceScaleFactor 3.125 (300 dpi); `img2pdf --pagesize 210mmx297mm` binds them; `qpdf --linearize --object-streams=disable` linearises.
+- Even page count for booklet binding (multiple of 4 ideal). Add or remove a supporting page if parity breaks.
+- Cover and backpage are full-bleed `--surface-deep` with `@page :first { margin: 0 }` and named `@page backpage-full`.
+- Screen-only chrome (e.g. a Download PDF pill button) uses `@media print { display: none !important; }` per the skill.
+- `execFileSync` for img2pdf and qpdf (never `execSync` with template strings: shell-injection class).
+- Verify: `qpdf --check`, `pdfinfo | grep -E "Pages|Optimized"`, **and read every page visually**. `pdfinfo` reporting "25 pages, A4" is not verification.
+
+**Design tokens.** Reference the project's `design-tokens.md` Tier 1 (raw) + Tier 2 (semantic aliases) + Tier 3 (component) layers. Premium register defaults: `--paper-25` near-white page surface, `--teal-900` ink, `--gold-500` accent, `--paper-100` cool mist (`#ECF1F2`) tinted-band surface. Update token values in one place; CSS `:root` mirrors the spec.
+
+**Logo placement.** Copy the light and dark icon variants from the project's public assets (`logo-light.png` for dark cover/backpage, `logo-dark.png` reserved for light content pages if needed) into the artefact directory. Cover top-left pairs the icon with the wordmark; backpage top-left does the same.
+
+References: `references/html-pdf-pipeline.md` for the canonical `render-pdf.mjs` source and CSS scaffold.
+
+## Doctrine (enforced across all stages)
+
+- **No internal workings in public artefacts.** Comparison-to-baseline, reconciliation-pending, open-Q markers, internal cross-references all stay in working files (`01-narrative/office-hours-design.md`, section READMEs). Public artefacts (business plan, deck, prospectus, PDFs) state the current position as a fact.
+- **Every claim cites a source.** Companies House for the cap table. The model worksheet for every financial figure. A named publication for every market figure. A specific vendor page for every competitor claim.
+- **Design tokens are the visual contract.** Update once in the tokens spec; the business plan CSS, the prospectus CSS, and the deck CSS all consume the same tokens. Never hardcode hex values inside component CSS.
+- **Even page count for booklet binding.** Multiple of 4 ideally; minimum even. Add or remove a supporting page to maintain parity if a section change breaks it.
+- **Verify by reading every rendered page.** `pdfinfo` page count is not verification. The bottom 30% of every page must reach the content margin without significant whitespace.
+
+## Pitfalls to avoid (collected from the reference project)
+
+- **Renaming a directory after the URL is published.** Keep `<project-site>/.docs/data-room/html/<artefact>/index.html` stable; if the URL changes, downstream investor links break.
+- **Letting Round-2 hires inflate the Year-1 P&L.** Only Round-1 hires belong in the Year-1 income statement. Customer-success and product-engineer hires that trigger in Round 1 are in; senior platform engineer, head of growth, and CS team scale that Round 2 funds are not.
+- **Mixing "Year 1" (12-month) and "Round 1 runway" (9-month).** If the £350k buys 9 months, present a 9-month forecast; do not present a 12-month forecast that implicitly assumes Round 2 closes mid-period without modelling the Round-2 cash injection.
+- **Generic AI-bolted-onto-cloud-CRM competitors.** Treat the competitive set as three failing categories: incumbents (cloud CRM + bolted AI), Anthropic horizontal AI (inaccessible to non-tech-wizard users), and new-build cloud-SaaS AI-OS replacements (migration-required, same lock-in pattern as incumbents). Name each vendor, cite each claim from the vendor's own page, rebut with the substrate-AI inversion.
+- **Forgetting Priestley / equivalent founder-thesis anchor.** Any founder who built the same thesis years before AI made it structurally apparent should reference it: book title, first-publication date, founder's costly-signal action (e.g. "bought 200 copies and distributed them to operators in his network"). This dates the conviction and lifts the deck's signal weight.
+- **Letting the page background go light brown.** Premium register page surface (`--paper-25`) is near-white (`#FBFAF6`), not ivory. The screen-preview body background stays plain white (`#FFFFFF`).
+
+## References
+
+- `references/data-room-structure.md` — section-by-section README templates
+- `references/business-plan-template.md` — 15-section business plan template
+- `references/deck-blueprint-template.md` — 12-slide deck brief template
+- `references/html-pdf-pipeline.md` — render-pdf.mjs canonical source + CSS scaffold
+- `references/compliance-research-checklist.md` — UK + EU regulatory regimes to verify
+- `references/internal-workings-scrub.md` — the public-vs-internal doctrine, patterns to scrub, recurrence list
+- `references/design-tokens-application.md` — how to consume `realagent-site/.docs/design-tokens.md` from an artefact's `:root` block
+
+## Reference project
+
+The first execution of this skill produced `realagent-site/.docs/data-room/` for Real Agent Network Limited (Companies House 17237239). Read that directory as the canonical example; the skill's job is to reproduce its structure and doctrine for any subsequent UK seed raise.

package/payload/platform/plugins/founder-pack/skills/investor-data-room/references/business-plan-template.md

@@ -0,0 +1,61 @@
+# Business plan template — 15-section structure
+
+The canonical structure used by `01-narrative/business-plan.md`. Every public-facing artefact (deck, prospectus, term sheet) derives from this file. Apply the internal-workings scrub (see `internal-workings-scrub.md`) on every revision.
+
+## Section-by-section skeleton
+
+### 1. Executive Summary
+One paragraph each: what the company is (legal entity + Companies House identifier + substrate description), what is being raised (size, pre-money, post-money, runway, Round 2 follow-on), demand evidence (numbers with dates), market size + structural tailwind, competitive set in three failing categories + the architectural inversion, bottom-line P&L summary.
+
+### 2. Vision and Mission
+Three blocks. **Vision.** Where the company ends up at full execution. **Mission.** What the company gives to its customer day one. **Doctrine.** The structural belief that everything else derives from.
+
+### 3. The Company
+Legal entity table (legal name, Companies House number, incorporation date, registered office, SIC, PSC status, sole proposed director on IN01) + pre-investment cap table (sourced from the IN01 verbatim) + post-investment dilution pointer.
+
+### 4. The Market
+Subsections: Size of the addressable market (TAM with citation per figure); Structural tailwind (margin squeeze, regulatory tailwind, or equivalent); Self-employed wedge or analogous high-growth segment; Domestic adjacency (next-vertical expansion); International upside (channel partner enabling it); Pricing and TAM (per-customer ACV × addressable count = TAM number).
+
+### 5. The Product
+Subsections: What it is (substrate description, CRM-agnostic / data-sovereign positioning); The wedge product (narrowest unit of value, public-by-default if applicable); The upsell path (wedge → high-value output → full substrate); The substrate moat (operator-data + ontological graph + flywheel); Conversation ingestion (or equivalent lock-in mechanic); The network (federation thesis); Asymmetric-capture position (the LLM-binary wrap argument, with commercial-practice insurance); Human-services layer (training, support, white-glove, anti-fragile-against-frontier-AI).
+
+### 6. The Business Model
+Revenue streams (subscription tiers + future network-effect revenue), unit economics (ACV, CAC, gross margin, churn placeholder), compute-mark-up doctrine ("never mark up the LLM compute; customer pays the LLM provider directly").
+
+### 7. Go-to-Market
+Wedge → Beachhead → Blitzscale framework (with months and funding source per phase), demand evidence (40+ EOIs, paid intents, founder dogfood, partnership status — every number cited), GTM partners (one row per named partner with role and source), horse-before-cart logic (public-first wedge that earns trust for the private high-value upsell), geography.
+
+### 8. Competition
+Three failing categories: (a) cloud-CRM-bolted-AI incumbents, (b) horizontal-AI providers inaccessible to ICP, (c) new-build cloud-SaaS replacements requiring full migration. RANL differentiation paragraph. Most-direct-competitor counter (CRM-agnostic vs migration-required is the headline rebuttal).
+
+### 9. Operations
+Technology stack (foundation model, graph store, hardware tiered by workload, network, hosting), data sovereignty paragraph, IP ownership chain (deed-of-assignment commitment), compliance posture operational summary (pointer to Section 10 for full treatment).
+
+### 10. Compliance and regulatory positioning
+Three regulatory regimes: UK consumer protection (DMCC Act for estate agency / equivalent for the vertical), UK data and AI regime (UK GDPR + ICO ADM Articles 22A–22D), EU AI Act (relevant only to international expansion). Adjacent UK obligations (Estate Agents Act / equivalent + AML + sector membership bodies). Closing: "Why compliance is the moat, not the tax".
+
+### 11. Team
+Founders (foregrounded) with role + concise career summary + key credentials + pre-investment shareholding. Strategic shareholders from incorporation (advisors, family, JV partners on the cap table from day one). Hiring plan table with month-triggered roles + salary + trigger condition.
+
+### 12. Financial Plan
+12.1 Opening balance sheet (M0 after capex). 12.2 Year-1 Income Statement (revenue + COGS + every opex line + depreciation + EBIT + corp tax + net loss). 12.3 Year-1 cash flow summary table (period-by-period opening, net flow, closing cash). 12.4 Closing balance sheet (M12). 12.5 Two-round funding strategy (timing, size, pre-money, purpose, gating evidence per round). 12.6 Contingency levers. 12.7 Use of funds (this round) by bucket.
+
+### 13. Risks and Mitigations
+Two-column table: risk + mitigation. Cover Loop / Anthropic / competitor-ships-earlier / wedge-fails-to-convert / founder-transition / counsel-delays / Round-2-market / investor-structure.
+
+### 14. Milestones (the N-month thesis)
+Month-by-month table: M0 close + closing conditions; M1 first paying customer; M3 product-engineer hire + ~10 customers; M6 wedge phase complete; M7 Round 2 raise opens; M9 Round 2 closes; M12 break-even.
+
+### 15. The bottom line
+Summary table of headline numbers (raise size, pre-money, post-money, dilution, runway, Y1 revenue/loss/cash-burn/closing-cash/ARR, break-even month, Round 2 timing/size). Closing paragraph.
+
+### Appendices
+Cited documents listed by title only. Each available to a serious investor on request; internal-only working documents are not listed.
+
+## Writing rules
+
+- **Numbers cite their source.** Every figure in the body links to an Appendix entry that is itself a publicly-shareable document.
+- **No internal commentary.** See `internal-workings-scrub.md`.
+- **No em-dashes between alphabetic words** in user-facing prose. Use colons, parentheses, semicolons, or rewrites.
+- **Even-page-count parity** if the document is printed; add a supporting page if a section change breaks parity.
+- **One pre-investment cap table source: the IN01.** Reconcile the nominal-value discrepancy (e.g. £0.001 vs £0.01) before writing the balance sheet.

package/payload/platform/plugins/founder-pack/skills/investor-data-room/references/compliance-research-checklist.md

@@ -0,0 +1,53 @@
+# Compliance research checklist
+
+Required before drafting business plan Section 10 (Compliance and regulatory positioning) for a UK-domiciled raise. Every claim must cite a primary source (ICO guidance, gov.uk, regulator strategy document) verified by WebSearch.
+
+## UK consumer-protection regime
+
+**For estate-agency / property:** Digital Markets, Competition and Consumers Act 2024 (DMCC Act). In force from 6 April 2025. Supersedes the Consumer Protection from Unfair Trading Regulations 2008 for estate-agency consumer protection. Under the DMCC Act, **omitting material information is automatically an unfair commercial practice regardless of whether the omission affected the consumer's decision**. CMA holds direct enforcement powers including fines without court process. Property brochures must include Part B material information.
+
+**For other verticals:** Identify the equivalent UK consumer-protection regime (financial services → FCA Consumer Duty; healthcare → CQC; legal services → SRA; etc.). Same pattern: cite the binding statute, name the regulator, identify the enforcement mechanism.
+
+## UK data-protection and AI regime
+
+- **UK GDPR** sits over UK data processing. Articles 22A to 22D (added by the Data Use and Access Act) govern solely automated decision-making.
+- **No UK AI-specific statute in the 2026 parliamentary session.** Labour's 2024 King's Speech committed to "appropriate legislation on the most powerful AI models" but the Bill has not been introduced. A dedicated 2026 AI Bill is not expected.
+- **ICO strategy.** June 2025 strategy "Preventing Harm, Promoting Trust" frames the regulator's approach. ICO consulting on updated Automated Decision-Making and Profiling guidance during 2025–2026, with a statutory code of practice on AI and ADM in the pipeline. First substantive enforcement guidance expected later in 2026.
+- **UK is not adopting the EU AI Act.** Sector-led approach via existing regulators. Starmer's stated position: *"instead of over-regulating these new technologies, we're seizing the opportunities they offer"*.
+
+## EU AI Act (relevant only to international expansion)
+
+- Entered into force 1 August 2024.
+- Fully applicable 2 August 2026.
+- Classifies AI systems used in credit and insurance (which overlap with mortgage and property-financing decisions) as **high-risk**. Most marketing and operational AI applications sit at lower risk tiers.
+- High-risk obligations: risk-management systems, data-quality controls, human oversight, transparency to affected individuals, conformity assessment, post-market monitoring.
+- For UK-domiciled companies, the EU AI Act binds only when serving EU customers. Document the international expansion path and confirm whether any planned product crosses into high-risk territory.
+
+## Adjacent UK obligations to verify per vertical
+
+- **Estate Agents Act 1979** for property: distinguish software vendor (out of scope) from estate agent (in scope).
+- **Money Laundering Regulations 2017 + Economic Crime and Corporate Transparency Act 2023** for AML obligations.
+- **PECR (Privacy and Electronic Communications Regulations 2003)** for electronic marketing, cookies, and tracking. Sits alongside UK GDPR. Enforced by ICO with fines up to £500,000.
+- **Sector membership bodies** (NAEA / ARLA Propertymark for property; equivalents per vertical).
+- **Client Money Protection schemes** where the business handles client money.
+
+## WebSearch protocol
+
+For each regime, search for:
+
+1. The primary statute / regulation page on gov.uk or the regulator's site.
+2. A recent (within last 12 months) legal-firm briefing summarising current state.
+3. The regulator's strategy document.
+
+Examples that worked in the reference project:
+
+- DMCC Act + Propertymark guidance withdrawal: `https://www.propertymark.co.uk/resource/material-information-guidance-withdrawn-as-the-digital-markets-competition-and-consumers-act-takes-over.html`
+- ICO AI strategy: `https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/artificial-intelligence/guidance-on-ai-and-data-protection/`
+- UK AI Bill status: `https://iapp.org/news/a/king-s-speech-signals-diffuse-uk-digital-policy-agenda-but-no-ai-bill`
+- EU AI Act compliance for UK businesses: `https://www.rmoklegal.com/guides/eu-ai-act-compliance-uk`
+
+Cite the actual source URLs in the business plan's reply / Sources block (per the WebSearch tool's mandatory citation rule).
+
+## The closing argument
+
+The business plan's Section 10 ends with "Why compliance is the moat, not the tax": cloud-CRM-bolted-AI competitors inherit the vendor's data-protection posture; the product owns the agent's data sovereignty by design, so compliance is a competitive moat (especially into EU markets where the EU AI Act amplifies the cost differential).

package/payload/platform/plugins/founder-pack/skills/investor-data-room/references/data-room-structure.md

@@ -0,0 +1,77 @@
+# Data room structure — graph-structured ten-section layout
+
+Standard ten numbered sections plus root README, internal-narrative subdirectory, and an `html/` directory for rendered deliverables. Each section's `README.md` is both an investor-diligence index and a content-recording checklist.
+
+## Section purposes (README skeletons)
+
+### 01-narrative
+**Purpose.** Strategic substance the prospectus, business plan, term sheet, and any future investor-facing material derive from. Internal scratchpad lives here too.
+
+**Currently present.**
+- `office-hours-design.md` — APPROVED office-hours output (internal).
+- `business-plan.md` — 15-section public business plan.
+- `deck-blueprint.md` — 12-slide brief.
+
+### 02-corporate-legal
+**Purpose.** Statutory documentation. First section any investor's lawyer asks for.
+
+**Standard contents.** Certificate of incorporation, IN01 application, articles of association, shareholder agreement, board resolutions, register of members, register of directors and PSCs.
+
+### 03-cap-table
+**Purpose.** Who owns what, before and after the round. Most-scrutinised number in seed-stage diligence.
+
+**Standard contents.** Pre-investment cap table (per IN01), post-investment cap table (with dilution math), fully-diluted including option pool, founder vesting schedule (if any), share register, subscription letters.
+
+### 04-financials
+**Purpose.** The investability of the raise: runway, burn, revenue ramp, break-even, contingency.
+
+**Standard contents.** `model_worksheet.md` (opening cash, capex, monthly burn, MRR ramp, two-round funding strategy, contingency levers), historical accounts (if any), bank statements, unit economics, VAT status.
+
+### 05-commercial
+**Purpose.** Customer pipeline, demand evidence, GTM partners, route-to-revenue.
+
+**Standard contents.** `demand-evidence.md`, named-partner files (one per partner — e.g. `kerfuffle.md`, `magnetic-bd.md` with companion proposal PDF), `pipeline.md`, pricing schedule, sales playbook, customer references.
+
+### 06-product-ip
+**Purpose.** What investors are buying — architecture, code, brand, data, IP ownership chain.
+
+**Standard contents.** Deed of assignment (IP transfer to the raising entity), trademark filings, domain inventory, OSS manifest, security posture, privacy policy, terms of service, third-party dependency disclosures, disaster-recovery plan, optional architecture notes (e.g. `encrypted-document-sharing.md`).
+
+### 07-team
+**Purpose.** Who is executing, in what capacity, with what compensation.
+
+**Standard contents.** Founder CVs (one PDF per foregrounded founder, named `<firstname>-<lastname>.pdf`), employment agreements, director service agreements, advisor agreements, org chart, hiring plan, compensation philosophy, references.
+
+### 08-market
+**Purpose.** Size of the prize, shape of demand, competitive landscape. Every market figure in the business plan must trace to a row in this section.
+
+**Standard contents.** `sources.md` (every figure with citation), `competitor-value-claims-rebuttal.md` (vendor-by-vendor rebuttal framework), TAM/SAM/SOM file, customer-segmentation analysis, regulatory landscape, international-expansion potential.
+
+### 09-operations
+**Purpose.** Day-to-day regulatory, compliance, and operational infrastructure.
+
+**Standard contents.** ICO registration, DPIA, data processing agreements, privacy notice, insurance pack (PI, public liability, cyber, D&O, employer's), HMRC registrations (corporation tax, PAYE, VAT, R&D), AML policy, code of conduct, business bank account, accountant retainer, registered office services.
+
+### 10-supporting
+**Purpose.** Everything that adds weight to the pitch but does not belong in a structured section. Press, references, brand assets, advisor letters, demo recordings, pitch decks.
+
+**Standard contents.** Press kit, pitch deck (live presentation version), demo recording, reference contacts, advisor letters, awards, published thought leadership.
+
+## Top-level README.md doubles as data-room index
+
+Three things at the root:
+
+1. **Company identity table** — legal name, Companies House number, incorporation date, registered office, SIC code.
+2. **Top-level files** (any published artefacts that need a stable URL — e.g. `index.html` and `prospectus.pdf` if the directory itself is served).
+3. **Section index** with status snapshot (substantively populated / has key item missing / empty placeholder).
+
+## Naming conventions
+
+- Companies House filings: `incorporation-<co-house-no>-<YYYY-MM-DD>.pdf`.
+- Founder CVs: `<firstname>-<lastname>.pdf`.
+- Commercial partners: `<partner-name>.md` + `<partner-name>-proposal-<id>-<date>.pdf`.
+- All section READMEs are lowercase markdown.
+
+## Published-URL stability
+
+If the data room hosts a public prospectus (e.g. `realagent.chat/sites/<slug>/`), keep the published path stable across renames. The published HTML lives at `html/<artefact>/index.html` inside the data room and republishes from there to the stable URL.

package/payload/platform/plugins/founder-pack/skills/investor-data-room/references/deck-blueprint-template.md

@@ -0,0 +1,38 @@
+# Deck blueprint template — 12 slides
+
+Each slide is specified by Purpose, Headline (one-line message), Body (bullets + figures pulled from the business plan), Visual suggestion, and Source reference. The deck is the presentation surface; the business plan is the source of truth.
+
+## 12-slide layout
+
+| # | Slide | What it lands |
+|---|---|---|
+| 1 | Cover | Company name, raise headline, three foregrounded founders, Companies House identifier. |
+| 2 | Vision | Vision / Mission / Doctrine triad. |
+| 3 | The Market | TAM with citation, structural tailwind (margin-squeeze / regulatory / equivalent), self-employed or analogous wedge, domestic adjacency, international upside, pricing band. |
+| 4 | Business Model | Subscription tiers + hardware + service layer + future network-effect revenue + unit economics + compute-no-markup doctrine. |
+| 5 | Go-to-Market | Wedge → Beachhead → Blitzscale framework, demand evidence numbers, named GTM partners, horse-before-cart logic. |
+| 6 | The Product | Substrate description, wedge, upsell path, substrate moat, conversation ingestion, network, asymmetric capture, services layer. |
+| 7 | Competition | Three failing categories + most-direct-competitor counter (CRM-agnostic vs migration-required). |
+| 8 | The Team | Founders + strategic shareholders, with one-line credential per person and shareholding %. |
+| 9 | Economics | Y1 revenue, P&L loss, cash burn, M11 cash low, M12 closing cash, closing ARR, break-even month. Two-panel chart: MRR ramp with burn overlay + monthly cash balance. |
+| 10 | The Raise | Size, pre-money, post-money, dilution, instrument, use of funds, IP transfer at close, Round 2 size + timing, pre-emption. Pie chart of post-investment cap table. |
+| 11 | Milestones | M0 to M-final timeline with MRR curve and Round-1 / Round-2 close markers. |
+| 12 | Other Information | Compliance (DMCC + UK ICO + EU AI Act), platform-dependency disclosure with the commercial-practice-insurance answer, contact card (founders + email + web). |
+
+## Production notes attached to the blueprint
+
+- **Format.** 16:9 landscape, A4-or-equivalent print-safe. PDF deliverable + source deck file (PowerPoint or Keynote, founder preference).
+- **Font and colour.** Apply the project's design tokens (`<project-site>/.docs/design-tokens.md`) — teal-ink + gold-accent + paper-surface + slate-text + champagne rule. Tier 1 raw tokens; reference Tier 2 aliases in component CSS, never raw hex.
+- **Charts.** Build in the same renderer the prospectus uses so figures match the financial model. Source all numbers from `04-financials/model_worksheet.md`.
+- **Logo and hero.** Reuse white-mono icon for dark slides, dark icon for light slides.
+- **Internal commentary.** Zero. Every slide carries the current position as a fact. No "open items", no "pending rebuild", no "reconciliation paths". See `internal-workings-scrub.md`.
+- **Speaker notes.** One paragraph per slide. The founder of the relevant function writes their own (technical founder writes the vision and product notes; commercial founder writes the GTM note; operator founder writes the team note).
+
+## Deliverables
+
+Once the deck is designed, archive at:
+
+- `<data-room>/10-supporting/investor-deck.pptx` (or `.key`)
+- `<data-room>/10-supporting/investor-deck.pdf`
+
+The blueprint file (`01-narrative/deck-blueprint.md`) stays as the brief for any future redesign.

package/payload/platform/plugins/founder-pack/skills/investor-data-room/references/design-tokens-application.md

@@ -0,0 +1,79 @@
+# Design tokens application
+
+How a print-ready HTML artefact consumes the project's design-tokens spec.
+
+## Source of truth
+
+Project keeps `<project-site>/.docs/design-tokens.md` as the canonical tokens spec. Three tiers:
+
+- **Tier 1 — Global tokens.** Raw hex values (e.g. `--teal-900: #0E1418`). Never reference directly from a component.
+- **Tier 2 — Semantic aliases.** Maps Tier 1 to roles (e.g. `--text-primary: var(--teal-900)`).
+- **Tier 3 — Component tokens.** Per-component variables that reference Tier 2 aliases.
+
+Components consume Tier 2 or Tier 3, never Tier 1 directly. This isolation lets a token-value update propagate without touching component CSS.
+
+## Premium register defaults (the reference project)
+
+| Token | Value | Role |
+|---|---|---|
+| `--teal-900` | `#0E1418` | Primary ink |
+| `--teal-950` | `#06080A` | Deepest dark surface |
+| `--teal-700` | `#2A3036` | Secondary ink |
+| `--gold-300` | `#C9B07A` | Champagne flourish |
+| `--gold-500` | `#A4884C` | Antique gold rule |
+| `--gold-700` | `#7A6235` | Bronze accent |
+| `--paper-0` | `#FFFFFF` | Pure white (elevated cards) |
+| `--paper-25` | `#FBFAF6` | Near-white page surface (default) |
+| `--paper-50` | `#F4EFE5` | One step warmer |
+| `--paper-100` | `#ECF1F2` | Cool mist (callout / tinted-band surface) |
+| `--slate-400` | `#8A8E96` | Tertiary text |
+| `--slate-600` | `#5C6470` | Secondary text |
+| `--rule-fine` | `#E2D5BD` | Champagne sand divider |
+
+## Tier 2 aliases
+
+```css
+--surface-page:     var(--paper-25);    /* default page background */
+--surface-elevated: var(--paper-0);     /* cards, panels */
+--surface-warm:     var(--paper-100);   /* tinted band; in premium register this is cool mist */
+--surface-deep:     var(--teal-950);    /* full-bleed dark sections */
+--text-primary:     var(--teal-900);
+--text-secondary:   var(--slate-600);
+--text-tertiary:    var(--slate-400);
+--text-on-deep:     var(--paper-25);
+--text-accent:      var(--gold-700);
+--text-accent-on-deep: var(--gold-300);
+--border-fine:      var(--rule-fine);
+--border-accent:    var(--gold-500);
+--font-display:     var(--serif);       /* Cormorant Garamond */
+--font-editorial:   var(--body-serif);  /* Lora */
+--font-ui:          var(--sans);        /* Inter */
+```
+
+## Hard rules
+
+- **Never hard-code a hex value inside component CSS.** Audit by `grep -E '#[0-9A-Fa-f]{3,6}' <artefact>/index.html` — every match must be inside the `:root` block.
+- **Page background is `--paper-25`, never pure `#FFFFFF`.** Pure white is reserved for elevated cards (`--surface-elevated`).
+- **Gold is reserved for accent, never primary CTA.** Primary action buttons sit on `--teal-900` with `--gold-700` hover.
+- **All-caps eyebrows always use `--font-ui` + letter-spacing ≥ 0.24em.**
+- **Cool mist (`--paper-100 #ECF1F2`) replaced warm cream (`#EFE7D8`) in the premium register.** Tinted bands / callouts read as pale steely blue, not light brown.
+
+## When the user says "I don't like this colour"
+
+The pattern from the reference project: the user identifies a token whose value is off. The fix is:
+
+1. Update the value in `<project-site>/.docs/design-tokens.md` Tier 1 table.
+2. Mirror the value in every consuming artefact's `:root` block (business plan HTML, prospectus HTML, deck HTML).
+3. Re-render PDFs.
+
+Keep the token NAMES stable. Updating values is non-breaking; renaming is.
+
+## Logo assets
+
+Project ships icon variants in `<project-site>/public/<brand>/`:
+
+- White-mono variant for dark backgrounds (cover, backpage).
+- Dark variant for light content pages.
+- Colour variant for general use.
+
+Copy the needed variants into the artefact directory (e.g. `html/business-plan/logo-light.png`) for relative-path reference inside the HTML.