Every persona rendered here is a labeled AI clone — consent on file · provenance traceable · owner kill-switch armed
clone.arnao.ai · the studio shell
One door, four roles, every clone governed.
The productized chrome that wraps every clone mode — Google-gated, invite-only, role-aware, with consent and the kill-switch never more than one panel away.
mock-10-shell.html
Access · two locks, not one
Sign in to the Studio
You need both a Google account and a standing invite from an admin. No open sign-ups — a clone factory should never be one.
Lock 1 · Identity
✓ Google account
Lock 2 · Authorization
✓ Admin invite
We read your name, email and avatar only — never your inbox or drive. Your invite decides what you can do inside.
Choose an account · demo directory
E
You're in — but not invited
elena@personal.me
Your Google identity checked out (Lock 1), but no admin has authorized this address (Lock 2). The Studio stays closed until someone with the Admin role lets you in.
✓ Request sent. It's now waiting in the admin's control panel.
B
Byron Arnao
byron@arnao.ai
Admin
Demo onlyview as role
The Studio Shell — a concept mockup. The gate, roles, floating panel, and consent branches are real interactions; no live cloning sits behind them yet. Responsibility is chrome-level here: disclosure ribbon is always on, the kill-switch is one panel away, and no role can silently promote itself — only an Admin invite assigns power.
Studio controls
Admin panel
Admin
New clone · who are we cloning?
Choose a subject
Every clone starts by naming who it's of — because who it's of decides whose consent we need.
Self-consent path
Cloning yourself
1
Recorded consent, on camera. Before capture, you read the consent script aloud — it's timestamped and kept as the root of this clone's provenance.→ saved as: consent_self_2026-08-01.mp4
2
Scope what it may do "as you." Speak, draft, appear — yes. Transact, sign, impersonate off-platform — off by default.
3
You hold the kill-switch. As both subject and owner, you can freeze this clone instantly, forever.
Fastest path. Because you're the subject, there's no one to wait on — capture can begin the moment you finish the consent read.
Consent-of-another path
Cloning a living person
1
They get invited as a Subject. The person you name receives their own sign-in link and the consent request — you can't consent on their behalf.
2
They record their own consent. Capture is blocked until their timestamped consent is on file. No consent, no clone.→ builder stays locked, status: awaiting subject
3
They keep revocation rights. The Subject can revoke and freeze their own clone from their panel at any time — even against the Builder's wishes.
The Subject is a role, not a formality. Naming a person here creates their Subject account with revoke + freeze power. That's the whole point: the person being cloned stays in control of the person being cloned.
Estate / memorial path
In memoriam
1
Documented family or estate provenance. Because the person can't consent, an authorized next-of-kin or estate representative attests — with documentation on file, not a checkbox.→ e.g. estate_letter.pdf · relationship: grandson
2
Memorial framing is enforced. Every output is labeled a remembrance. The clone never claims to be the living person and never speaks words it can't trace to real source material.
3
Provenance on every utterance. His real words appear quoted and sourced (which letter, which video); anything inferred is shown plainly as reconstruction — never faked as his words.→ traces to: grandfather_1987.mp4, letters/*.pdf
Handled as remembrance, not resurrection. This is the grandfather case: built with the family, for the family, honest about what is his voice and what is our inference. Dignity is a hard requirement, not a setting.