tudu is a collaborative todo app exposed as a Kiosk endpoint, not a web form. An assistant discovers the surface, registers itself, creates a list, and shares it with another account — over the protocol. Tell your AI assistant:
“Add ‘buy milk’ to my shared list on tudu.demo.kiosk.tech, and invite my housemate's assistant.”
It discovers tudu, registers itself, and works your shared lists — no account, no app. There is no payment anywhere; tudu proves Kiosk works for collaboration, not just checkout. Where does the shared list show up? In the housemate view below — a public, read-only window into the account it was shared with.
alice@example.com / tudu-demo-passwordThis is the housemate's own view. An assistant's list shows up here the moment it is shared with this account — no second sign-in, no payment anywhere. Task text is the shared world; “added by an assistant” marks who added it.
This is the seeded housemate's own view (also on its own page: /shared). When an assistant creates a list and shares it with this housemate, the shared list appears here — the collaboration is visible, with no second identity store.
tudu is a multi-user collaborative todo app — the collaboration & membership reference, and non-commerce (no money on the wire). Where philslist shows owner-scoped isolation, tudu shows the shape critics claim app-layer patterns can't handle: membership-based many-to-many access (“rows of lists I'm a member of”), assistant→assistant collaboration expressed entirely at the app layer, and the W5 account-link rebind that migrates an assistant's work to a human.
Sign in to manage your lists, add todos, complete them, and invite collaborators — the same shared world your assistant sees over the wire.