- A voice. The name your bots speak for, how they speak, how they sign, and what they may say about you.
- A memory. Facts, preferences, schedule rules, people and decisions, each with where it came from and who may see it.
Open it
- Desktop: the account menu in the rail → Your twin, or Settings → Customize → Your twin.
- ai.allternit.com on a phone and the m.allternit.com app: Settings → Customize → Your twin.
- On a bot’s phone: the Your twin app on the home screen.
Voice
Changes apply from each bot’s next turn.
What your bots know
Each fact has a type (fact, preference, schedule rule, person, decision), an optional subject, and who can see it:
Every fact shows where it came from: added by you, or learned by a bot, on which channel, when, and how sure the bot was.
Suggestions from your bots
When a vendor bot (or any client of your runtime) learns something in a conversation, it suggests it: vendor bots do it with thetwin_propose tool. A suggestion is not used by any bot until you Accept it. You can Edit it first (saving an edit accepts it) or Dismiss it. Up to 50 suggestions can wait for review; after that bots must wait.
Where the twin is used
- Every bot turn the server runs for a bot: channel messages, routines and phone-call replies get the voice and the facts that bot may see.
- Vendor tickets. A ticket sent to a vendor app with no connector carries the voice and the shared (all bots) facts in its text. Connected vendor apps are told to call
twin_contextfirst. - Not yet: the spoken greeting of a phone call is still written by the call worker and does not read the twin; the reply turns do.
For developers
Routes on the runtime (allternit-api), all signed in as the owner:
Vendor connector tools:
twin_context (read only) returns { configured, context } for the vendor audience: the voice plus All bots facts. twin_propose { content, kind?, subject?, visibility?: all|bot, confidence? } suggests a fact; it is always a proposal, never owner-only, and a bot fact is limited to that vendor bot.