private-data-boundary
The owner's private investment data and where it may never go. Invested amounts, invest dates and years, entry rounds and follow-ons, realized/unrealized/current value, [redacted]/TVPI/DPI, per-company or per-deal [redacted] (one general portfolio [redacted] is allowed, from data/portfolio-performance.yaml), carry, fund or entity names, share class, [redacted]-or-cap, round terms, and links to his AngelList portfolio must never be in a committed file, a build, a deploy target or another repo. The one exception is angel-investments-performance, which is always kept. Use before any data, Airtable, AngelList, sync, import, deploy, cleanup or cross-repo work, and whenever a file or page might carry deal data.
- Source file
.claude/skills/private-data-boundary/SKILL.md
Private data boundary
The rule
The Airtable Manus view's columns are fixed. Only its public columns
(data/airtable-manus-sync.json publicFields: name, market, exit status,
latest market cap, one-liner, website, acquired by, category, sub-category)
may be written to any file, in any repo, or to any deploy target.
Never write, and never pull from AngelList or another Airtable view:
- invested amounts, invest dates and invest years
- the round he invested in (Airtable "Round", e.g. "Series A+") and which
companies got follow-ons (owner, 2026-10-17). A page's
stageis the company's public stage or latest public round, never his entry round. - realized, unrealized and current value
- [redacted], TVPI, DPI, RVPI
- per-company or per-deal IRR, and any second IRR figure (see below)
- carry, fund names, investment entities
- share class, valuation-or-cap, [redacted] and other terms
No AngelList links (owner, 2026-10-11): no angellistUrl key and no value,
logo included, that links to his AngelList portfolio. Airtable's "Angellist
URL" column is never read.
Source links: direct, never to a private host
Since 2026-10-16 every cited source on a page is a plain direct link to its URL
(owner rule, 2026-10-16: every link followed, no hop pages; standing-rules). A source on a private
host is never linked: AngelList (any angellist.com or angel.co page),
Wellfound, Airtable, Google Drive and Docs, Dropbox, DocSend, Notion and
app.carta.com. publicSourceHref() / sourceLinkHtml() in
server/publicInvestorResearch.ts return no link for them and the page shows
the publisher unlinked; the old /sources/{id} URL of such a source is a 404.
The host list is PRIVATE_SOURCE_HOST_PATTERN in scripts/private-deal-fields.mjs
(a literal copy in server/publicInvestorResearch.ts, parity in
server/private-deal-data.test.ts). A company value must cite a linkable
source; the build throws otherwise. Source URLs still never enter a browser
bundle (pnpm privacy:bundle): a React island gets them from server-built
props in its page's HTML, never from a client data module. The data files keep
/sources/{id} references (they 301 to the source), because URL slugs such as
"…-valuation-…" break the data-file vocabulary policy.
On 2026-10-16 all 849 cited sources were checked: three are on private hosts and render unlinked (a Wellfound profile in the angel directory, and two AngelList blog posts cited by the angel directory and the all-time rankings).
IRR: one general figure only
Owner, 2026-10-11: "IRR is ok, general IRR is ok, only one IRR is allowed,
which is general." The portfolio-wide IRR may appear on the public site as one
figure. It lives in exactly one place, data/portfolio-performance.yaml
(generalIrr), read through shared/portfolioPerformance.ts; copy in
content/ and page code uses the {irr} placeholder and the label "IRR".
Never write the number itself anywhere else, never a per-company or per-deal
IRR, and never a second IRR figure (industry benchmarks included).
server/general-irr-single-source.test.ts fails on a hard-coded percentage
next to "IRR" or the literal figure outside the source file. The llms files and
data downloads still carry no IRR at all (RESTRICTED_PERFORMANCE_TERMS in
server/publicContentPolicy.ts).
Numbers on every surface: public fields only (owner, 2026-11-05)
"never ever Private numbers." Every number on a page, its markdown version
(/page.md), a statistics or research page, an opening sentence, a list
title, llms.txt or llms-full.txt comes only from Manus-view public fields
(counts by sector, market, status; public valuations on HTML pages only) plus
the single general IRR via {irr} on HTML pages. Markdown and llms outputs
carry no company values, market caps or IRR at all. These outputs are built
from the public-field allowlist, never from a full Airtable record. Any new
surface that shows figures gets a test that fails when a private field or
restricted term reaches its output (server/markdown-pages.test.ts for the
markdown pages), and ships only after the private-data-auditor agent and
the gate pass.
The one exception
Always keep angel-investments-performance (owner, 2026-10-11). It is the
private Angel Simulator (~/Code/sahin/angel-investments-performance, private
repo sahin/angel-investments-performance) and holds this data on purpose.
Never delete or archive it, never rewrite its history, never scrub its data,
including during privacy cleanups. A user-level PreToolUse hook
(~/.claude/hooks/keep-angel-investments-performance.sh) blocks those commands.
Enforcement
server/private-deal-data.test.ts: fails on any deal field in a committed JSON file, any AngelList portfolio link in any committed file, and any of the retired private exports coming back.pnpm privacy:bundle(scripts/validate-public-bundle.mjs): the same checks on every shipped file indist/cloudflare.- Field list and patterns:
scripts/private-deal-fields.mjs. Never loosen them. scripts/validate-public-seo-build.mjsandserver/staticBuild.ts: no built page links a private host (PRIVATE_SOURCE_HOST_PATTERN).server/general-irr-single-source.test.ts: the general IRR figure exists only indata/portfolio-performance.yaml; no second IRR figure anywhere.- Agent:
private-data-auditorsweeps the repo, build, live site, sibling repos and Cloudflare Pages projects (read-only).
Before data, sync, deploy or cleanup work
Check every place the data lands, not just this repo:
(Read-only. Owner, 2026-10-13: "we only work in web-angel-investments": never
edit, commit, push or deploy a sibling repo; report what you find instead.
Hook: scripts/hooks/only-this-repo.mjs.)
- sibling repos under
~/Code/sahin/(angel-investments,web-angel-investments-*), but leaveangel-investments-performancealone - every Cloudflare Pages project in account
9ea45491…. Old projects keep serving files, and every deployment keeps its own URL. - Cloudflare caches hashed assets for a year (
immutable). A file removed from the build can stay reachable until it is purged.
When a shipped bundle carried private data
- Remove the data at its source and rebuild (the bundle gets a new hash).
- Add the old path to
REVOKED_PUBLIC_ASSETSinserver/publicRouting.ts. The worker then answers it with a 404 before Cloudflare's asset cache is consulted.server/cloudflare-worker.test.tsproves this. - Ship it. Every deploy runs
scripts/cloudflare-purge.ts, which purges each revoked bundle from both sahin.io cache layers and checks it answers 404. If one is still served, it purges the whole zone and checks again. The run fails if that doesn't work, or if theCLOUDFLARE_API_TOKENsecret lacks the Zone > Cache Purge permission on sahin.io. - Older deployments keep their own pages.dev URLs and old worker. Only deleting those deployments removes the file there.
History
On 2026-10-11 an old Manus dashboard (angel-portfolio-dashboard.pages.dev,
repo sahin/angel-investments) was found serving these fields. The
project was deleted and the files purged from that repo's history.
portfolio-data-airtable.json, scripts/airtable-raw-export.json and 285
AngelList links were removed from this repo (6e74d0e, ad0d60c).