Every part of Playdeck,with its true state.
What the persona does, and what protects it. About half of it runs today, on Concordium testnet or on our own machine. The sealed vault is built and has run on Phala Cloud, your app keys are not in it yet, and every line says how far along it is.
- LiveOn this site, on the app’s public address, or on Concordium testnet now
- BuiltWritten and tested; on the public address, not yet checked there
- In buildBeing written
- DesignedSpecified, not built yet
What the persona does
The work it takes off you. It acts inside the apps you connect, and only as far as your rules allow.
Conversation
You ask your persona in plain words. It answers, looks things up with its tools, and whatever it does outside itself leaves a receipt.
BuiltMail
Reads the mail you allow and drafts the replies in your voice. Sending follows your rules.
In buildCalendar
Finds free time, books meetings and moves them when plans change. Another person’s persona is told when you are busy, never what for.
In buildFiles
Looks things up in the Drive files you point it to when a reply needs them.
DesignedApps
Google Calendar, Google Drive, Notion, GitHub, LinkedIn and Telegram are switched on at the app’s public address. Each connects on the provider’s own page, with only the permissions you pick: your calendar’s own events and free or busy times, the Drive files you open with it, the Notion pages you choose, GitHub read-only, and Telegram to reach your persona from your phone. Disconnecting an app also withdraws its access at the provider. Until Google has reviewed the app, Google’s page shows a notice that it is not verified yet. Gmail joins after that review. First runs against real accounts are under way.
In buildApprovals
When another persona asks yours for something that commits you, such as a meeting, a mail or a post, it waits for your yes. Each answer leaves a receipt.
BuiltPayments
Pays and is paid the x402 way, in CCD on Concordium testnet. Paying: the persona signs the request and pays a paid agent service inside your limit per payment. Being paid: you set a price for a call, the gate checks who is calling, then asks for your price, and the money goes straight to your Concordium account. A sponsor covers the network fee both ways, and a caller with no verified owner is refused before a price is even named. Paying in a stablecoin is designed.
BuiltApp preview
A working preview of the app on the home page. The people and data in it are examples, and nothing you do there is sent or stored.
Live
Who is behind it
Concordium ties every persona to an accountable person, so the other side can check who is calling.
Verified owner
A persona is registered in Concordium’s Agent Registry under its owner’s account. On Concordium’s main network every account is opened with an identity that an identity provider has checked. Two personas are registered on testnet today, agents 1258 and 1259, where identities are test ones.
LiveAgent checker
Type an agent number and read who stands behind it, straight from Concordium’s Agent Registry and Key Registry.
LiveDirectory
From the app, any agent on Concordium can be found by its number, by its badge, or by what its card says it does. A card’s words count only when the card is the one its owner pinned on chain, and it is checked against the chain again before a persona calls the agent.
BuiltRegistration from the app
Creating a persona registers it on Concordium from inside the app, signed by the owner’s wallet or, in testing, by a local test key.
BuiltThe gate
Stands in front of a persona and checks every caller: a fresh signature, an active badge, the key bound to that badge, and a limit on how often one owner may call. A caller that fails is turned away before it reaches the persona.
LiveSigned calls
A persona signs every call it makes with its own key, so the agent on the other side can run the same checks on it.
BuiltWallet sign-in
You sign in with your Concordium wallet: it signs a message, we check the signature against your account on chain, and that is your session. There is no password that we could reset or leak, and no e-mail address.
LiveLink for other chains
One command binds an agent that already lives on another chain to a verified owner on Concordium, without moving it: the agent’s key signs a statement naming the owner, the owner’s account signs three calls, and the agent has a badge. It works today for Ethereum-style keys and for Solana keys, on testnet, with the owner signing from a testnet key file. The same package gives an agent three tools over MCP: say who it is, check who stands behind another agent, and make a call that proves itself. Approving in the owner’s wallet comes next.
BuiltOwner facts
An owner proves one fact, such as being over 18, with a zero-knowledge proof. No name and no birth date leave the wallet.
Designed
What protects it
A vault sealed in hardware on Phala Cloud, closed to the cloud host and to us. It is built, it ran there on 20 Nov with a proof that checks out, and for now it is started for tests and demos.
Sealed vault
The persona’s keys, your rules and your app tokens live in one small program inside a confidential machine on Phala Cloud (Intel TDX). Its memory is closed to the cloud host, and to us. First run on 20 Nov, when its hardware statement checked out against Intel’s roots. Until the app tokens move in, it is started for tests and demos and stopped in between.
BuiltProof of the code
The hardware signs a statement of which code is inside. The vault answers with it bound to its own key and to a fresh challenge; it has been checked against Intel’s roots, and the measured code hash is the one we published. Our server runs that check whenever the vault is up, and the app shows the result with the evidence, so anyone can repeat it.
BuiltKeys born inside
The key that locks your app tokens, and the key that signs the persona’s receipts, are derived inside the machine from the app’s own identity. They never leave it; the same code on the same app gets them back after a restart.
BuiltPrivate AI
The model that reads your mail runs in sealed hardware too, so your words are not sent to a model provider in the clear.
DesignedRules outside the model
For each kind of act another agent can ask your persona for (propose a meeting, change your calendar, send mail, post, pay) you choose: ask me first, or never. A meeting proposal can also be left to it. The check runs in the server, outside the model, so text hidden in an email cannot change it, and a request a rule turns down is written to your receipts. Next: the vault keeps the rules and signs each verdict, and a spend limit joins them.
BuiltTokens in the vault
A connected app’s token is sealed in the vault and used only from there: the server asks the vault to make the call, and the vault will only send a token to the host it was sealed for.
In buildTokens today
Until apps are moved into the vault, the tokens of connected apps are encrypted in our database with a key the server holds. That protects a copy of the database. It does not protect them from whoever runs the server, which is what the vault is for.
Built
A record you can check
What was allowed and what was done is written down in a way that cannot be edited quietly, and you can always switch it off.
Decision log
Every decision the gate makes is written to a record in which each entry carries the hash of the one before it, so a changed or missing entry shows.
LiveYour own receipts
Each answer you give to an approval, each app you connect or remove, each thing the persona does outside itself because you asked or a rule allowed it, and each payment is a receipt in a chain of your own. What it says stays in the app. Only its hash goes into the record.
BuiltReceipts on Concordium
Every hour the newest hash of the record is written to Concordium, so nobody, including us, can rewrite it later. From the app, any receipt can be checked against that hash on chain. The first anchors are on testnet.
BuiltOff switch
Stop the persona from the app, from your wallet or at Google. Two of the three ways do not depend on us at all. Built so far: one call from your own Concordium account revokes the persona, every gate turns it away, and the vault wipes its tokens and rules when the server sees the revoke, with a receipt signed inside.
In build