@rubytech/create-sitedesk-code 0.1.386 → 0.1.388

package/payload/premium-plugins/venture-studio/skills/investor-data-room/references/compliance-research-checklist.md

@@ -1,53 +0,0 @@
-# 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/premium-plugins/venture-studio/skills/investor-data-room/references/data-room-structure.md

@@ -1,88 +0,0 @@
-# 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` — 16-section public business plan.
-- `deck-blueprint.md` — 13-slide brief.
-- `exit-thesis.md` — target exit value, 5–8-year horizon, exit routes (strategic / PE / IPO), 3–5 named acquirers with one-line rationale each.
-
-### 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, `comparables.md` (recent comparable rounds — company / pre-money / post-money / multiple / source — that the term sheet's valuation cites).
-
-### 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 (must include **LTV:CAC ratio** and **burn multiple** as named lines alongside ACV / CAC / LTV / gross margin / churn), 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 (bottoms-up; **geography-tier floor** — late pre-seed TAM is expected to clear $1B US / $500M UK / $500M EU; flag any named geography that sits below its floor), `market-growth-rate.md` (single CAGR figure with citation + one-line 3-year market-expansion thesis), `market-share-trajectory.md` (path to 3–8% SAM within 5 years, reconciled to the ARR target in the business plan), 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.
-
-### prototype/ (sibling of the ten numbered sections)
-**Purpose.** Running code: landing page source, wedge prototype source, dev-server logs. This is the only top-level under `.docs/data-room/` that ships an executable surface rather than narrative or diligence artefacts. Lives outside the numbered investor sections because investors read the rendered URL, not the source tree.
-
-**Standard contents.** One subdirectory per hosted surface (e.g. `landing/`, `prototype/`, `prototype-v2/`), each containing:
-- Framework scaffold (e.g. Vite `package.json`, `src/`, `index.html`) or a single static `index.html`.
-- `.port` — the local port the dev server / file server binds to (allocated by `prototype-host` skill from the 4100–4199 range).
-- Framework dotfiles (`.gitignore`, `vite.config.ts`, etc.).
-
-**Lifecycle.** Created by `bin/scaffold.sh` (empty directory) when the data room is first scaffolded. Populated by the `prototype-host` skill when the founder runs "host the landing" or "host the prototype". Multiple surfaces can coexist — port allocation, cloudflared ingress rules, and systemd unit names are all namespaced by surface name.
-
-## 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/premium-plugins/venture-studio/skills/investor-data-room/references/deck-blueprint-template.md

@@ -1,39 +0,0 @@
-# Deck blueprint template — 13 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.
-
-## 13-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, **CAGR with citation**. |
-| 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, **LTV:CAC and burn multiple**. 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 | Exit | Target exit value, 5–8-year horizon, exit routes (strategic / PE / IPO), 3–5 named acquirers with one-line rationale each. Sourced from `01-narrative/exit-thesis.md`. |
-| 12 | Milestones | M0 to M-final timeline with MRR curve and Round-1 / Round-2 close markers. |
-| 13 | 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/premium-plugins/venture-studio/skills/investor-data-room/references/design-tokens-application.md

@@ -1,79 +0,0 @@
-# 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.

package/payload/premium-plugins/venture-studio/skills/investor-data-room/references/html-pdf-pipeline.md

@@ -1,236 +0,0 @@
-# HTML + PDF render pipeline
-
-Image-only A4 portrait PDF, rendered from a single HTML file via Playwright + img2pdf + qpdf. Constraints inlined in the parent `SKILL.md` Stage 5.
-
-## File layout per artefact
-
-```
-html/<artefact>/
-  index.html        # source of truth
-  render-pdf.mjs    # Playwright pipeline
-  <artefact>.pdf    # rendered output
-  logo-light.png    # for dark cover/backpage
-  logo-dark.png     # for light content pages (optional)
-  README.md         # render + verify commands, page list
-```
-
-## HTML scaffold (key blocks)
-
-```html
-<!DOCTYPE html>
-<html lang="en-GB">
-<head>
-  <meta charset="UTF-8">
-  <link href="https://fonts.googleapis.com/css2?family=Cormorant+Garamond:ital,wght@0,400;0,500;0,600;0,700;1,400&family=Inter:wght@400;500;600;700&family=Lora:ital,wght@0,400;0,500;0,600;1,400&display=swap" rel="stylesheet">
-  <style>
-    /* Tier 1 + Tier 2 design tokens from project's design-tokens.md */
-    :root {
-      --teal-900: #0E1418;
-      --teal-950: #06080A;
-      --gold-500: #A4884C;
-      --gold-300: #C9B07A;
-      --gold-700: #7A6235;
-      --paper-0:  #FFFFFF;
-      --paper-25: #FBFAF6;
-      --paper-100: #ECF1F2;
-      --slate-400: #8A8E96;
-      --slate-600: #5C6470;
-      --rule-fine: #E2D5BD;
-      --serif: 'Cormorant Garamond', serif;
-      --body-serif: 'Lora', Georgia, serif;
-      --sans: 'Inter', sans-serif;
-      --surface-page: var(--paper-25);
-      --surface-deep: var(--teal-950);
-      --text-primary: var(--teal-900);
-      --text-on-deep: var(--paper-25);
-      --text-accent: var(--gold-700);
-      --text-accent-on-deep: var(--gold-300);
-    }
-
-    @page { size: A4 portrait; margin: 18mm 16mm 20mm; }
-    @page :first { margin: 0; }
-    @page backpage-full { margin: 0; }
-
-    body {
-      margin: 0;
-      background: var(--surface-page);
-      color: var(--text-primary);
-      font-family: var(--body-serif);
-      font-size: 11pt;
-      line-height: 1.55;
-      counter-reset: pagenum;
-    }
-
-    .page {
-      counter-increment: pagenum;
-      position: relative;
-    }
-    .page:not(.page--cover):not(.page--backpage)::after {
-      content: counter(pagenum);
-      position: absolute;
-      bottom: 10mm;
-      right: 16mm;
-      font-family: var(--sans);
-      font-size: 9pt;
-      letter-spacing: 0.28em;
-      color: var(--slate-400);
-    }
-    .page:not(.page--cover):not(.page--backpage)::before {
-      content: "REAL AGENT NETWORK LIMITED · BUSINESS PLAN · v1.0";
-      position: absolute;
-      bottom: 10mm;
-      left: 16mm;
-      font-family: var(--sans);
-      font-size: 7pt;
-      letter-spacing: 0.24em;
-      color: var(--slate-400);
-    }
-
-    @media screen {
-      body { background: #FFFFFF; padding: 24px; }
-      .page {
-        width: 210mm; min-height: 297mm;
-        margin: 20px auto; padding: 18mm 16mm 20mm;
-        background: var(--surface-page);
-        box-shadow: 0 4px 28px rgba(0,0,0,0.14);
-      }
-      .page--cover, .page--backpage { padding: 0; overflow: hidden; }
-    }
-
-    @media print {
-      body { background: var(--surface-page); padding: 0; }
-      .page { page-break-after: always; padding: 0; }
-      .page--cover, .page--backpage {
-        margin: 0; width: auto; box-shadow: none;
-        height: 100vh; position: relative; overflow: hidden;
-        -webkit-print-color-adjust: exact;
-        print-color-adjust: exact;
-      }
-      .page--backpage { page-break-before: always; page: backpage-full; }
-      .download-btn { display: none !important; }
-    }
-
-    .download-btn {
-      position: fixed; top: 20px; right: 20px; z-index: 100;
-      font-family: var(--sans); font-size: 9pt; letter-spacing: 0.28em;
-      text-transform: uppercase; color: var(--paper-0);
-      background: var(--teal-900); padding: 11px 18px 12px;
-      border-radius: 9999px; text-decoration: none;
-      box-shadow: 0 4px 16px rgba(14, 20, 24, 0.18);
-    }
-    .download-btn:hover { background: var(--gold-700); }
-  </style>
-</head>
-<body>
-  <a class="download-btn" href="<artefact>.pdf" download>Download PDF</a>
-
-  <section class="page page--cover" data-screen-label="cover"> ... </section>
-  <section class="page" data-screen-label="exec-summary"> ... </section>
-  <!-- ... one <section class="page"> per A4 page ... -->
-  <section class="page page--backpage" data-screen-label="backpage"> ... </section>
-</body>
-</html>
-```
-
-## render-pdf.mjs (canonical)
-
-```javascript
-#!/usr/bin/env node
-import { chromium } from 'playwright';
-import { execFileSync } from 'node:child_process';
-import { mkdirSync, rmSync, existsSync } from 'node:fs';
-import { dirname, basename, join, resolve, extname } from 'node:path';
-import { pathToFileURL } from 'node:url';
-
-const [, , htmlInput, pdfOutput] = process.argv;
-if (!htmlInput || !pdfOutput) {
-  console.error('Usage: render-pdf.mjs <input.html> <output.pdf>');
-  process.exit(64);
-}
-
-const htmlPath = resolve(htmlInput);
-const pdfPath  = resolve(pdfOutput);
-const tmpDir = resolve(dirname(pdfPath), `.tmp-${basename(pdfPath, extname(pdfPath))}`);
-rmSync(tmpDir, { recursive: true, force: true });
-mkdirSync(tmpDir, { recursive: true });
-
-const VIEWPORT_W = 794;        // A4 portrait at 96 dpi
-const VIEWPORT_H = 1123;
-const SCALE = 3.125;           // → 300 dpi PNGs
-const A4_HEIGHT_PX_SLACK = VIEWPORT_H + 2;
-
-(async () => {
-  const browser = await chromium.launch();
-  const context = await browser.newContext({
-    viewport: { width: VIEWPORT_W, height: VIEWPORT_H },
-    deviceScaleFactor: SCALE,
-  });
-  const page = await context.newPage();
-
-  await page.goto(pathToFileURL(htmlPath).toString(), { waitUntil: 'networkidle' });
-  await page.emulateMedia({ media: 'print' });
-  await page.evaluate(() => document.fonts ? document.fonts.ready : Promise.resolve());
-  await page.evaluate(() => { document.body.style.padding = '0'; });
-
-  const sections = await page.$$('section.page');
-  if (sections.length === 0) {
-    console.error('No <section class="page"> elements found.');
-    process.exit(65);
-  }
-
-  const pngFiles = [];
-  let overflow = false;
-
-  for (let i = 0; i < sections.length; i++) {
-    const section = sections[i];
-    const label = await section.getAttribute('data-screen-label') || `page${i + 1}`;
-    const scrollHeight = await section.evaluate(el => el.scrollHeight);
-    if (scrollHeight > A4_HEIGHT_PX_SLACK) {
-      console.error(`[OVERFLOW] page ${i + 1} (${label}): ${scrollHeight}px > A4 + 2px slack`);
-      overflow = true;
-    }
-    const outPath = join(tmpDir, `page-${String(i + 1).padStart(2, '0')}-${label}.png`);
-    await section.scrollIntoViewIfNeeded();
-    await section.screenshot({ path: outPath, type: 'png' });
-    pngFiles.push(outPath);
-  }
-
-  await browser.close();
-  if (overflow) {
-    console.error('Overflow detected. Aborting.');
-    process.exit(4);
-  }
-
-  const preLinearize = join(tmpDir, 'pre-linearize.pdf');
-  execFileSync('img2pdf', ['--pagesize', '210mmx297mm', '--output', preLinearize, ...pngFiles], { stdio: 'inherit' });
-  execFileSync('qpdf', ['--linearize', '--object-streams=disable', preLinearize, pdfPath], { stdio: 'inherit' });
-
-  console.log(`✓ PDF written: ${pdfPath}`);
-})();
-```
-
-## Verification
-
-After every render:
-
-```sh
-qpdf --check <artefact>.pdf                           # → "No syntax or stream encoding errors found"
-pdfinfo  <artefact>.pdf | grep -E "Pages|Optimized"   # → confirms page count + linearization
-```
-
-Then **read every page visually**. `pdfinfo` reporting "25 pages, A4" is not verification.
-
-## Dependencies
-
-```sh
-npm i -D playwright && npx playwright install chromium
-brew install img2pdf qpdf
-```
-
-## Hard rules
-
-- One `<section class="page">` per A4 page. Renderer aborts (exit 4) on overflow.
-- `execFileSync` (never `execSync` with template strings).
-- Cover and backpage are full-bleed dark teal (`--surface-deep`); skip page numbers and running footer via `:not(.page--cover):not(.page--backpage)` selectors on the page-counter pseudo-elements.
-- Even page count for booklet binding (multiple of 4 ideal).
-- Logo: copy the white-mono icon variant as `logo-light.png` for dark cover/backpage; copy the dark icon variant as `logo-dark.png` if used on light content pages.

package/payload/premium-plugins/venture-studio/skills/investor-data-room/references/internal-workings-scrub.md

@@ -1,33 +0,0 @@
-# Internal-workings scrub — public-vs-internal doctrine
-
-Public-facing documents (business plan, prospectus, deck, term sheet, anything the investor reads) state the **current position** only. The journey to that position, the reasoning behind it, comparisons against prior baselines, open items still being reconciled, and cross-references to internal sections all stay in working documents in the data-room's internal sections.
-
-## Patterns that must NOT appear in public docs
-
-- **Comparison to baseline / prior version.** *"The loss has grown from -£282.6k to -£323.1k because…"*, *"Total opex (M0 customer-success hire adds £40,500 vs the M10 model worksheet baseline)"*.
-- **Process commentary.** *"Numbers below use the model's published figures pending the reconciled rebuild"*, *"reconciliation pending"*, *"open item, not actioned here"*, *"see Section X critical note and Section Y contingency levers for the reconciliation paths"*.
-- **Internal cross-references to scaffolding.** *"see Section 12.3 critical note"*, *"see Section 12.6 contingency levers"* when the linked content itself is process-talk rather than substance.
-- **Discrepancy resolution narratives.** *"The earlier '£0.01 vs £0.001 nominal' note is resolved by treating the £4,500 as share premium"*.
-- **"Open Q" or "Open item" markers in body text.** Belongs in section READMEs and the office-hours design doc only.
-- **Date-coded internal designs.** *"2026-04-22 design"*, *"office-hours design doc"*, *"model worksheet (Appendix A) needs a rebuild"*.
-- **"Pre-contingency-lever activation" / "once X is included" hedges in summary tables.**
-- **Explanatory parentheticals that name the process.** *"(M10-trigger model did not carry)"* is process commentary and must go.
-
-## What IS acceptable in a public-facing document
-
-- The current position, stated as a fact.
-- A footnote citing a source (Companies House, IBISWorld, ICO, etc.) when the figure derives from public data.
-- A pointer to a public appendix (titled documents only; not internal-section READMEs).
-- Conditions on a forecast figure that an investor needs to know (e.g. "assuming Round 2 closes at M9-M10").
-
-## The same content, internal vs public
-
-| Internal version (working doc) | Public version (business plan) |
-|---|---|
-| Total operating expenses ~£649,100 (M0 customer-success hire adds £40,500 vs the M10 model worksheet baseline). | Total operating expenses ~£649,100. |
-| Year-1 P&L loss has grown from -£282.6k to -£323.1k because the customer-success hire is brought forward from M10 to M0. | Year-1 P&L loss is approximately £323k against revenue of £356k. |
-| Cash crosses zero at M8–M9 if Round 2 does not close; the model worksheet's M11 £34k cash low arrives roughly two months earlier under the M0 CS hire structure. | The raise is sized to deliver the Round 2 gating milestones; Round 2 closes at M9 to M10. |
-
-## Recurrence is a P0 violation
-
-In the reference project this rule was violated three times in one session (initial draft used a dated internal design reference; appendix table referenced internal-only documents alongside externally-shareable ones; M0 customer-success hire updates added "model worksheet baseline" comparisons). The pattern: every time the founder adds content or asks for an update, the temptation is to include "what changed and why" alongside the new value. The temptation must be resisted; the public document carries only the new value. The "what changed and why" goes in a sibling internal document if it needs to live somewhere.

package/payload/premium-plugins/venture-studio/skills/investor-data-room/references/monetization-strategy.md

@@ -1,35 +0,0 @@
-# Monetization Strategy
-
-The method for turning a product into a revenue model: how the business makes money, from whom, over what time, and how that compounds. Pricing (`pricing-strategy.md`) sets the number on one tier; monetization sets the **shape of revenue across the whole relationship and the whole market**. Output lands in `04-financials/` and feeds business-plan §6 "The Business Model" and the prospectus.
-
-## What this produces
-The revenue architecture: the streams, the wedge→upsell path, the expansion mechanics, and the future network/platform revenue — each tied to evidence and reconciled against the financial model. Apply `internal-workings-scrub.md` before anything reaches a public document.
-
-## Citation discipline (binding)
-Every quantitative claim — attach/expansion rates, comparable monetization multiples, market spend that a future stream taps — is a **sourced claim**. Route benchmarks (typical net revenue retention, attach rates, comparable take-rates) through the `research-assistant` specialist with `deep-research`. Mark anything unsourced `source pending — route to research-assistant`. Projected expansion rates must cite a comparable or be flagged as an assumption, never stated as fact.
-
-## Process
-
-### 1. Map the revenue streams
-List every way money comes in, now and planned: subscription, usage, services, and any future network-effect or platform-take revenue. For each, state whether it exists today or is a forward bet, and what gates it (the milestone that turns it on).
-
-### 2. Define the wedge → upsell path
-The narrowest unit of value (the wedge) earns trust and the right to sell the high-value product. State the mechanic: what the wedge delivers, what triggers the upsell, and the expected path from wedge ACV to full ACV. This is the monetization thesis — it must match the GTM "horse before cart" logic in business-plan §7.
-
-### 3. Choose the expansion engine
-How does revenue per customer grow without a new sale? Seat expansion, usage growth, tier upgrade, cross-sell. Name the one that dominates and tie it to a sourced or evidenced retention/expansion assumption. Land-and-expand only counts if the expand step has evidence.
-
-### 4. Sequence future streams to milestones
-Network-effect or platform revenue is real only when its gating milestone is named (e.g. "federation revenue turns on once N accounts are live"). Put it on the model as a forward stream with its trigger, not as day-one revenue.
-
-### 5. Reconcile to the model
-The streams and rates here must roll up to the ARR trajectory in business-plan §12 and the SOM in §4. If monetization implies a number the model doesn't show, one is wrong — reconcile explicitly (see the sibling `zero-to-prototype/references/market-sizing.md` reconciliation discipline).
-
-## Output
-`04-financials/` working notes → business-plan §6 and the prospectus. Each stream: status (live/forward), mechanic, gating milestone, and a citation for every benchmark.
-
-## Common failures
-- Counting forward network revenue as if it were live.
-- An "expand" motion with no evidence the expand step happens.
-- Attach/retention rates asserted, not sourced or evidenced.
-- Monetization that contradicts the ARR line in the financial model.

package/payload/premium-plugins/venture-studio/skills/investor-data-room/references/pricing-strategy.md

@@ -1,37 +0,0 @@
-# Pricing Strategy
-
-The method for setting a defensible price for the wedge and the full product. Output lands in `04-financials/` (unit economics) and feeds business-plan §6 "The Business Model" and the prospectus. Apply the `internal-workings-scrub.md` doctrine to anything that reaches a public document.
-
-## What this produces
-A price (or price band) per tier, with the **basis** stated: what the price is anchored to, why a buyer pays it, and what it implies for ACV, gross margin, and the LTV:CAC the financial model depends on.
-
-## Citation discipline (binding)
-Pricing is built from numbers — competitor prices, willingness-to-pay signals, cost-to-serve, comparable ACVs. Every such number is a **sourced claim**, not a guess. Route competitor pricing, comparable contract values, and willingness-to-pay benchmarks through the `research-assistant` specialist (with `deep-research` / `data-research`); quote the citation. Any figure you cannot source is written `source pending — route to research-assistant`. A price defended by invented competitor numbers is a failed price.
-
-## Process
-
-### 1. Choose the pricing basis
-Pick the anchor deliberately — they produce very different numbers:
-- **Cost-plus** — cost-to-serve plus a margin. Floor only; never the headline for software.
-- **Competitor-anchored** — relative to the sourced price of the closest alternative (including "the status quo / doing nothing", which often has a real cost).
-- **Value-based** — a share of the quantified value the buyer gets (time saved × loaded cost, revenue gained, risk avoided). The strongest basis when the value is sourced and legible to the buyer.
-
-Most seed-stage pricing is value-based with a competitor-anchored sanity check.
-
-### 2. Quantify value and willingness to pay
-State the buyer's gain in their units, sourced or evidenced from discovery (the sibling `zero-to-prototype/references/commitment-signals.md` and `mom-test.md`). Price as a fraction of that gain that still leaves the buyer clearly ahead. Cross-check against willingness-to-pay signals from real conversations, not assertion.
-
-### 3. Set the structure
-Decide the model (per-seat, usage, flat subscription, tiered) and the tiers. Keep tiers to the few a founder can explain in one breath. Name the wedge price (the narrow public-by-default entry) and the upsell price separately — the wedge→upsell path is the monetization thesis, detailed in `monetization-strategy.md`.
-
-### 4. Reconcile to unit economics
-The chosen price must produce an ACV that makes the model work: **LTV:CAC ≥ 3:1** target, **gross margin ≥ 70%** steady-state (the data-room's standing targets). If the price can't clear these with defensible CAC and churn, the price, the segment, or the cost structure is wrong — say which. Compute-cost pass-through follows the data-room doctrine: never mark up LLM compute; the customer pays the provider directly.
-
-## Output
-`04-financials/` working notes → business-plan §6 and the prospectus. Each tier: price, basis, ACV implication, and a citation for every external figure.
-
-## Common failures
-- Cost-plus pricing for value-dense software — leaves money on the table.
-- Competitor prices asserted from memory instead of sourced.
-- Tiers a buyer can't tell apart.
-- A price that quietly breaks the LTV:CAC the financial model assumes.