Entity.ID — A founding, in six chapters

Scene · The state of things

Real clients. Real revenue. No structure.

Anjali, Faisal, and Lucia had been shipping client work for months. By every practical measure Tarka Labs already existed — except the measures that matter when money, credit, or conflict shows up.

Tarka Labs — inventoryas of 2026-01-09

Structurenone

Equity"40 / 35 / 25, roughly" — said out loud, once

BankAnjali's personal account

Decisionswhoever answers the group chat first

Recordsscreenshots, mostly

A handshake holds three people together right up until it doesn't.

Two founders shaking hands to start a venture

Bengaluru · 23:47 · the agreement

Scene · The formation

Minutes, not months.

Name → purpose → partners → ownership → terms → constitution → register. Before the coffee went cold, Tarka Labs had verified members, a written constitution, and a public address anyone on earth can look up:

tarka-labs.public.entity.id

Ownership went from a vibe to a number.

Two founders forming their venture together at a laptop

Forming the venture · step 4 of 7

Evidence · captured 2026-01-14

app.entity.id/form — step 1 of 7

Formation wizard step 1 — naming the venture

Step 1 — claim the name.

app.entity.id/form — step 4 of 7

Formation wizard step 4 — ownership split 40/35/25

Step 4 — 40 / 35 / 25, written down at last.

Scene · The treasury

The venture holds its own money.

Client payments stopped routing through Anjali's personal account. The treasury belongs to Tarka Labs — spending above a threshold needs a second approval, and every movement lands in the venture's permanent record. Anjali's bank account went back to being a bank account.

Evidence · captured 2026-02-02

app.entity.id/finance

Finance module — treasury, banking, and cap table

Finance — treasury accounts, banking, and the cap table live inside the venture, not inside anyone's personal login.

"Whose account does the client pay?" stopped being a question.

Scene · Know Your Agent

TK-OPS joins — verified.

Ops was eating the founders' evenings, so they hired an AI operations agent. On Entity.ID that isn't a hack with someone's borrowed password — TK-OPS passed KYA (Know Your Agent) verification and joined the venture as a member in its own right: disclosed operator, scoped permissions, full audit trail.

ANAnjali Rao 40% FAFaisal Ahmadi 35% LULucia Romero 25% ⌁TK-OPS AI AGENT · KYA ✓

A small founding team working together in a bright studio

The studio · four members now, one non-human

KYA — Know Your AgentKYC for people. KYA for agents.

Same registry, same standing, same accountability. TK-OPS runs treasury operations inside the rules the founders set — and every action it takes is signed and recorded.

Reconciles the treasury nightly

Chases invoices and confirms receipts

Drafts payment batches — humans approve

Files the compliance calendar, on time

Evidence · captured 2026-03-18

app.entity.id/compliance

Compliance and verified standing — humans and agents on one record

Compliance & standing — humans pass KYC, agents pass KYA. Every member sits on the same verifiable record.

The first hire that came with its own audit trail.

Scene · The raise

Diligence took an afternoon, not a month.

Who owns what? Who decided what, and when? Where does the money sit? For most handshake teams that's weeks of archaeology. For Tarka Labs it was already public: formation date, members, cap table, every recorded decision. The round ran through Fundraising — post-money SAFEs issued by the venture, funds settling straight to the treasury.

The venture didn't have to prove it existed. The record did the talking.

Founders closing a funding round with an investor

May 6 · the round closes

Evidence · captured 2026-05-06

app.entity.id/fundraising

Fundraising — SAFE issuances settling to the treasury

Fundraising — SAFEs from the venture; funds settle to its treasury.

app.entity.id/overview

Venture overview — members, milestones, entity details

What the investor saw — one page, everything verifiable.

Epilogue · Behind the story

Tarka Labs is a demo venture.
The product is real.

Everything in this story is something Entity.ID does today: a 7-step formation that takes minutes, a public tamper-proof record, and a dashboard the venture runs on from day one.

STEP 1

Name your venture

STEP 2

Purpose & details

STEP 3

Add partners

STEP 4

Split ownership

STEP 5

Agree terms

STEP 6

Pick a constitution

STEP 7

Review & register

Who writes chapter one

Built for every kind of founder.

Founding teams

Operating on handshakes and needing structure before — or instead of — incorporation.

Studios & agencies

Client money, contributor splits, and project entities without the legal overhead.

Collectives & clubs

Shared treasuries and real membership rules for groups that were never going to file paperwork.

AI agents & AI-run orgs

Verifiable identity, legal standing, treasury access, and disclosure — KYA-verified from day one.

Why the record holds

Standards under the story.

Tamper-proof public record

Formation, members, ownership, and decisions live in a public registry no single party can quietly edit.

An open registry standard

Ventures are recorded on the Entity.ID protocol — an open standard anyone can verify against. No lock-in.

Verified members

KYC for people, KYA for AI agents. Every member — human or not — is verifiable, with disclosed standing.

Disputes, decided up front

Pick your resolution path during formation — arbitration options include Kleros v2 — before you ever need it.

The whole story, in three minutes

Every company is a story.
Most never get past chapter one.

The handshake.

Real clients. Real revenue. No structure.