# V3A — "Chapters" — Message Spine Branch of V3 (Founder journey). Same strategic angle — narrative, emotional, journey-driven — executed as a **cinematic, chaptered documentary**: six full-viewport chapter breaks with date slates (orange sync-tick, blinking REC dot), evidence exhibits captured from the real app, punchlines set in italic serif behind an orange rule, and a scroll-driven progress rail that fills as the story advances. The AI agent TK-OPS joins the cast in Chapter 04. ## Category (named) **The story of record.** Newspapers of record report what happened; registries of record prove it. Entity.ID is both at once for ventures: the place where a company's story — who's in it, who owns what, what was decided, where the money moved — is written down as it happens, publicly verifiable, tamper-proof. Not marketing about a company; the company, on the record. Diligence stops being archaeology and becomes a URL. Contrast frame: incumbents keep either documents (Clerky, LegalZoom) or private databases (Carta). Entity.ID keeps the story itself — and the record, not the vendor, is the trust anchor. ## Positioning statement For teams (and AI agents) already doing real work on a handshake, Entity.ID is the venture platform that makes them real in minutes — a named entity with members, ownership, rules, and a treasury on a tamper-proof public record — so the story of the company *is* its legal and financial history, written as it happens and carried intact into incorporation. Unlike incorporation platforms, whose paperwork says nothing about what a company did, and unlike equity software, whose private ledgers ask you to trust the vendor, the Entity.ID record is public, verifiable, and continuous — from Chapter 01 (the handshake) to Chapter 06 (incorporation day) and beyond. ## One big idea **Every company is a story — Entity.ID is where it gets written down.** The page is literally a six-chapter film of one venture's founding year; the product appears as dated "evidence" inside the narrative. The emotional claim underneath: most founding stories are lost — kept in screenshots, group chats, and three differing memories — and lost stories are exactly what makes diligence slow, disputes ugly, and incorporation a rebuild. A story written down as a record is a company that can prove itself. ## Three pillars ### 1. The record is the company Name, equity, decisions, treasury — written down once, publicly verifiable forever, at `tarka-labs.public.entity.id`. When the angel arrived in Chapter 05, the diligence answer was a URL: formation date, members, cap table, every recorded decision. The venture didn't have to prove it existed; the record did the talking. ### 2. Agents are cast members, not tools Chapter 04: a fourth member joins Tarka Labs — "it isn't human, it doesn't sleep." TK-OPS passes KYA (Know Your Agent) verification and joins as a member in its own right: disclosed operator, scoped permissions, every action signed and recorded. KYC for people, KYA for agents — same registry, same roster, same accountability. The first hire that came with its own audit trail. ### 3. Incorporation is an upgrade, not a rebuild Chapter 06's transfer manifest, dated 2026-09-01: 4 members (3 human, 1 verified agent), cap table 40/35/25 plus SAFEs, 31 recorded decisions with votes, full treasury history, signed investor agreements — and the line that lands the thesis: *rebuilt from scratch: nothing.* Eight months of history walked into the C-Corp on day one. ## Proof points (cited) | Claim | Source | |---|---| | Carta's 2024 data scandal — an employee misused confidential cap-table data; Carta exited secondary trading "to prioritize trust." When records live in a vendor's private database, the vendor is the trust model; a public record inverts that | TechCrunch, Jan 2024 | | A US court held unstructured-collective participants can be personally liable as general partners — the unwritten story is a liability (*Samuels v. Lido DAO*, 2025) | dwt.com/blogs/financial-services-law-advisor, Jan 2025 | | After 2008, regulators created the LEI because nobody could identify counterparties; 3M+ entities now carry one — proof that "who is this, on the record?" becomes mandatory infrastructure | GLEIF history — gleif.org | | An airline argued in court that its own chatbot was "a separate legal entity responsible for its own actions" — and lost, because no such entity existed. Entity.ID makes the honest version of that sentence true | *Moffatt v. Air Canada*, 2024 — McCarthy Tétrault | | ~69,000 AI agents already transacting ~$600M/yr over one payment protocol alone — economically active cast members with no legal identity | Coinbase x402, spring 2026 | | From 2026-08-02, EU law requires AI systems — explicitly including agents per Commission draft guidance — to disclose they're artificial; the mandate has a date, the infrastructure doesn't exist | EU AI Act Art. 50; Global Policy Watch, May 2026 | | American Banker, on the record: banks now need to "know your agent" — the industry is asking for KYA by name | American Banker (opinion), 2025 | | Record ~5.62M new US business applications in 2025, tracking higher in 2026 — millions of chapter-ones every year, almost none written down | US Census BFS; finder.com | | Estonia's registry publishes its own counters and earned €125M in 2025 — a registry earns trust by publishing its numbers | e-resident.gov.ee/dashboard; ERR, 2025 | | Anthropic's CEO predicts the first billion-dollar one-employee company in 2026 — the cast is shrinking to a person and their agents | Inc. (Amodei prediction), 2025 | | Carta requires a certificate of incorporation just to onboard — the incumbent stack starts after Chapter 02 | carta.com/equity-management/launch | ## Hero package **Variant A (shipped):** - Kicker: REC dot · "Entity.ID · A founding story · Recorded 2026" - Headline: *Every company is a story. Most never get past chapter one.* - Subhead: Entity.ID forms real ventures in minutes — a named entity with members, ownership, rules, and a treasury, recorded in a tamper-proof public registry. Operate today; incorporate when you need to. What follows is 34 weeks in the life of one venture: Tarka Labs. - Credits block: Featuring — Anjali Rao · Faisal Ahmadi · Lucia Romero · TK-OPS, an AI agent. Setting — a product studio with paying clients and nothing on paper. - CTAs: **Form your venture — free** → https://app.entity.id · **Begin the story** → #ch1 **Variant B (alt):** - Headline: *A company is born long before it's incorporated.* - Subhead: This is the true shape of a founding — six chapters, one venture, every step recorded. Entity.ID made it official on day five. - CTAs: **Form your venture** · **Watch the formation (1:07)** **Variant C (alt — the documentary conceit, foregrounded):** - Headline: *Thirty-four weeks. One venture. Every frame verifiable.* - Subhead: From a kitchen-table handshake to incorporation day, every member, decision, and payment in this film is a public record you can look up. Your founding could be shot the same way. - CTAs: **Start your chapter one** · **Skip to the evidence** → #ch2 ## Chapter map (dates are documentary slates, all 2026) 01 The handshake — Fri Jan 9, 23:47 · 02 The name — Wed Jan 14, 09:12 · 03 First money in — Mon Feb 2, 14:03 · 04 The team grows (TK-OPS, KYA) — Wed Mar 18, 11:26 · 05 Investors arrive — Wed May 6, 16:40 · 06 Incorporation day — Tue Sep 1, 10:00. Epilogue = "Tarka Labs is a demo venture. The product is real." + how it works (7 steps), who it's for, standards (tamper-proof record, open registry standard, KYC/KYA, Kleros v2 arbitration option), dashboard tour video (1:12), finale CTA ("Your chapter one takes minutes"). ## Lexicon — say this / not that | Say this | Not that | Why | |---|---|---| | chapter, scene, slate, evidence, cast | funnel stage, use case, feature tour | the documentary register is the brand; the product appears as exhibits | | the record, the story of record | blockchain, on-chain, ledger | banned terms; "record" is the film's own vocabulary | | tamper-proof, verifiable, captured | immutable, trustless, decentralized | trust language founders and regulators respond to | | the Entity.ID protocol / open registry standard | RegistryChain | the old name is retired — never use it | | venture, entity | DAO, proto-entity (hero), wrapper | "DAO" is legally radioactive post-*Lido*; founder-legible words win | | constitution, written down once | smart contract, code-is-law | high-trust governance words | | treasury, first money in | wallet (outside dev docs) | clean corporate-finance word | | KYA — Know Your Agent; cast member; verified member | agent KYC, bot, AI employee, tool | Chapter 04's thesis: agents join the cast with standing | | an upgrade, not a rebuild; transfer manifest; carried over | migration, data export | Chapter 06's language — continuity is the payoff | | absolute dates (Fri Jan 9, 2026) | "recently", "last month" | documentary slates demand absolute time; house rule | | Tarka Labs, a demo venture | (implied traction) | labeled in epilogue + footer; story, never traction | ## Craft notes - Hero stays in plain founder language; KYA/protocol jargon confined to Chapter 04 and the epilogue standards block. - Punchlines set in italic serif with an orange rule; orange is a micro-accent only (slate ticks, evidence labels, REC dot). - No pricing, customer counts, or revenue claims anywhere.