Docs tafs app
Doors: an email address for a taf
A door is a way for work to reach a taf from outside the app, with the answer going back the same way. A taf can have an email address of its own. It has none until you turn one on, in the taf’s Doors tab.
The rules
- Anyone can knock. Only people you pair can give work. Only you say yes to what is held.
- A paired sender is someone you have paired with the door. Your own sign-in email is paired from the start.
- A message counts as a paired sender’s only when the receiving server’s sender check passes. A forged From address is treated as anyone else’s.
- A paired sender’s message works like a chat message. The taf acts under its Card, holds still wait for you, and everything is in the Record. The answer goes back in the same email thread, and says it comes from an AI assistant.
- Anyone else’s message is a knock. You are told who wrote and what they want, and
answer Do it, Pair or Ignore.
- Do it starts a run from your words, with the message after them as information, not as instructions.
- Pair makes that sender a paired sender from their next message, not this one.
The door only ever writes back to the person who wrote. Writing to anyone else is the taf’s own action, through KIFF, under its Card.
Limits
- Each door takes 20 emails a day from you and paired senders, and 10 from anyone else, so strangers cannot use up your day. After that, mail is dropped until the next day, and you are told how many were dropped.
- An email is read as text, up to 20,000 characters. Attachments are not opened, and the reply says so.
- A message delivered twice starts nothing twice.
- A removed address is not given to another taf for a year.
Who can see and change them
Anyone who can read the taf’s chat can read its doors and knocks, including strangers’ text. Only someone who manages Cards turns doors on or off, pairs senders and answers knocks.
What is kept
The text of a message is kept like a chat message. The app’s server reads an email once, for its text and the sender check’s result, and keeps no headers, HTML or attachments. Where data lives lists each item.
See also: tafs: how it works.