# 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.
