Team twins

Early access. Invites, citations and the reports-never-decides rule all work today. Shared administration and per-source ownership are on the roadmap.

A team twin is you, for your colleagues. It answers from the internal material you give it — project notes, decisions, how-we-do-things — in your voice, so the fourth person to ask "where are the Meridian call notes?" gets the answer without you.

One rule defines it: it reports, it never decides. Ask it what you wrote and it tells you. Ask it to approve something, commit to a date, or make a call on your behalf, and it says plainly that that's yours to decide. A colleague acting on a commitment your twin invented is the worst thing that could happen here, so it can't happen.

Who can read it#

Only people you invite. An invite is just an email address — no codes, no links: access starts the first time your colleague signs into hiy with that address and opens the twin. Everyone else, including anyone who guesses the URL, gets a 404 — for them it doesn't exist.

Removing someone removes their access, not just their invitation.

What it knows#

Only what you give it, and what you give it stays internal: sources on a team twin can be marked confidential, which makes it impossible — enforced in the database, not by a checkbox — for them to ever reach your public twin.

Creating one#

From the twin switcher in your dashboard: New team twin. It's usually named after you, because it speaks as you — and a team twin named after yourself goes live without review. Name it after somebody else and a person checks it first; that's the identity rule doing its job.