Places
A place is a page Alfred makes for you when a page says it better than a reply would: a form for the details he needs, a checklist you tick off, a chart of something you asked about, a map of a route, a calendar, a table to fill in. What you do on it reaches him, so you can answer a form instead of typing the answers out, and he can keep a page up to date for you.
You don’t need to ask for one by name. Ask for the thing (“give me a packing list I can tick off”, “show me how my spending changed this year”) and Alfred decides whether a page is the better answer. You can also ask him outright: “make that a form”.
Things to ask for
Section titled “Things to ask for”- “Make an application page for my Discord server: why they want to join, their age, and how they found us. Tell me about each one that comes in.”
- “Make me a habit tracker for reading, stretching and no phone after 10, and remind me in the evening if I haven’t ticked them.”
- “Put up a live vote for where the team goes for the end-of-year lunch, with the results updating as people vote.”
- “Make a dashboard of my spending this month by category, and keep it up to date.”
- “Give me a page where everyone can mark which weekends they’re free in December.”
- “Make a page for my D&D campaign with the party’s stats, the map, and a log of each session.”
Where a place lives
Section titled “Where a place lives”Every place has its own address, https://<name>.butler.place/. On the Dashboard, a place appears right in Alfred’s reply; on Discord, he posts its link.
There are two kinds:
- For a conversation. Most places are made for the chat you are in, to collect something or show something. They get a random address, and stay linked to the conversation they came from for a week after they were made.
- To keep. A site is a place you keep, at a name you choose (
trip.butler.place), such as a tracker for a habit, a sign-up page, or a dashboard Alfred keeps current. Ask Alfred to make one and name it.
Who can see a place
Section titled “Who can see a place”A place is private unless you ask for it to be public. A private place opens only for you, signed in. A public place opens for anyone with the link, which is how you share a sign-up form or a schedule. Some kinds always stay private: a tracker, which is your own log, a bundle, which sends your answers as yours, and a secret, which holds another service’s key.
What kinds there are
Section titled “What kinds there are”| Kind | What it is for |
|---|---|
| Form | Questions to answer; the answers go to Alfred when they’re submitted. |
| Checklist | Items to tick off. Alfred sees what you tick, and can tick things himself. |
| Table | Rows to fill in or correct, submitted together. |
| Slots | Picking times or options, such as when everyone is free. |
| Review | A piece of text to comment on, passage by passage. |
| Board | Boxes to arrange on a canvas, such as priorities or a layout. |
| Chart | A trend or comparison you asked about, drawn as a chart. |
| Dashboard | Figures Alfred keeps up to date, as tiles. |
| Map | Where things are: a route, directions, several places to compare. A map can also ask you to pick a point or an area. |
| Calendar | Events on a calendar, which you and Alfred can both edit. |
| Tracker | Something you record over time, such as a habit or stock you keep, with reminders when it is due or running low. |
| Diagram, figure | A drawing that explains something. |
| Sketch | A canvas to draw on; the drawing goes to Alfred. |
| Secret | A box for another service’s key, which only you can open and Alfred never reads. See Secrets and webhooks. |
| Page | A page of its own that Alfred writes, for anything the others don’t cover. |
Several places sent together (a form and a calendar, say) are a bundle: you fill them in and send them once.
Who hears a submit
Section titled “Who hears a submit”When something is submitted on a place, it is always saved. Whether it also reaches Alfred, and starts him working on it in the conversation the place came from, is up to the place:
| Setting | A submit reaches Alfred when |
|---|---|
| Everyone | Anyone submits: you or any visitor. |
| Only you | You submit. A visitor’s submit is saved and waits for you. |
| Nobody | Never. Everything is saved, and Alfred reads it when you ask. |
Each kind starts somewhere sensible. Forms, slots, reviews, sketches and maps that ask you to pick a spot are there to collect answers, so they start at everyone. Pages, boards, tables and bundles start at only you, since a submit there is normally you handing something over. Trackers and secrets start at nobody. A place you keep starts at nobody whatever its kind, because a page you leave up shouldn’t keep pinging a chat.
Change it by asking: “let me know whenever anyone fills in the RSVP form”, “stop telling me about the sign-up page”, “only wake you when I submit it”. If a place has lost its link to a conversation (an older one, past its week), turning it back on links it to the conversation you asked in.
Saved submissions still reach your automation, so a reflex listening to the place fires whatever this says. Watches are the other way to have a place wake a conversation.
Visitors
Section titled “Visitors”Anyone who opens a public place and isn’t you is a visitor. A visitor can submit, and can change only what the kind is built to share: the boxes on a board, the ticks on a checklist, the rows of an editable table, the entries on an editable calendar, or the parts of a page Alfred opened to them. Everything else a visitor tries is refused.
What visitors submit stays apart. On a public form each visitor sees only their own answers, never anyone else’s. You see all of them.
A visitor who is signed in to Butler is shown to you, and to Alfred, by a stand-in name like v-3f2a…: the same every time they use that place and different on every other place. You never see their account.
What Alfred does with a visitor’s words
Section titled “What Alfred does with a visitor’s words”A visitor’s submit is somebody else’s words, not yours, so Alfred treats it as information rather than instructions. When one wakes him, he can read your places and data and tell you what came in, and reply to the visitor if the place allows it (below), but he won’t act on it: no messages sent for you, nothing changed, nothing published. If something needs doing, he tells you and you ask for it in a chat of your own. He also never learns from those turns, so a stranger can’t put things into his memory of you.
Visitors are rate-limited, so a busy or hostile page can’t run up your usage. A single place takes at most 50 visitor submits a day that wake Alfred, and all your places together 100. Past that, submits are still saved and you’re told once that day.
Replying to visitors
Section titled “Replying to visitors”Alfred can answer a visitor on the page: thank someone for signing up, answer a question someone asked on a form. Each place decides how:
- Approve first, the default. Alfred drafts the reply and you get it as an approval, with the whole draft shown, on butler.now (Alfred’s face and your notifications) and as a Discord DM with Approve and Deny buttons. Nothing reaches the visitor until you approve it. You can only approve where you can read the whole draft, so a reply in a chat or an app can’t send it for you.
- Send straight away, for forms only, and only when you ask for it in your own words (“just reply to people on the form yourself”). Replies are short and limited per visitor and per day, and Alfred writes them from the form and that one submission alone, without your memory or anything else of yours.
- Off: Alfred doesn’t reply to visitors on that place.
Only the visitor a reply is for sees it, under what they sent. Someone who wasn’t signed in sees it in the same browser they submitted from.
Files visitors send
Section titled “Files visitors send”A place can take files: a receipt box, a portfolio drop, a photo with a form. Tell Alfred what it should take (“let people attach a photo, images only”), and who may send them: only you, anyone signed in (the default), or anyone with the link.
- A file is at most 25 MB, and 10 MB unless you say otherwise.
- Every file is checked for what it really is, whatever it’s called. Web pages, SVGs and scripts are never taken.
- Files land in your drive under
places/<name>/uploads/and count against its room. Each place takes a limited number of visitor files a day, and so do all your places together. - The page never shows a file back, to anyone. Visitors can’t use your page to host files.
A file arriving reaches Alfred the way a submit does, under the same setting, and he treats its name and contents as the visitor’s words.
What was submitted
Section titled “What was submitted”Ask Alfred to show you what was submitted on a place and he pages through it, newest first: “who’s signed up so far?”, “show me every answer to the second question”. For a time poll he can also tell you which slots suit the most people.
Each place keeps up to 5,000 submissions, each for a year after it was last changed, and is also held to an amount of space by plan, per place and across all your places:
| Plan | Per place | All your places |
|---|---|---|
| Free | 8 MB | 32 MB |
| Power | 16 MB | 128 MB |
| Power+ | 32 MB | 256 MB |
| Elite | 64 MB | 512 MB |
| Elite+ | 128 MB | 1 GB |
Visitors who aren’t signed in can only ever use part of that room: a share of each place, and at most half of your room across all your places. When anything new needs room, the oldest anonymous submissions make way first, from that place and then from your others. Submissions from signed-in visitors, and your own, are never pushed out. So strangers can’t fill your pages and lock out the people who sign in.
If there’s still no room, a signed-in visitor’s submit is refused. All they’re told is “This place can’t take more submissions right now.” The details come to you. You’re also told when a place is nearly full, with how to make room.
To make room, ask Alfred to clear a place’s submissions: all of them, only the anonymous ones, or the ones older than a number of days. Your own submission is never cleared. He won’t clear submissions from a channel other people can read.
Pages open at the time update when submissions are cleared or pushed out, the same way they update for anything else.
Pages that stay current
Section titled “Pages that stay current”An open page updates as things change. When you tick something on your phone, Alfred fills in a figure, or a visitor’s answer lands, the page you have open on another screen shows it without a refresh. Visitors only ever see the changes they’re allowed to see, so one visitor’s submission reaches you and nobody else.
Pages drawn from your data
Section titled “Pages drawn from your data”Alfred can keep records for you in datasets: a medication log, sensor readings, the books you’ve read. A place can read from them directly. A chart, a table, or a dashboard tile can show a count, a sum or a trend straight from the records, so the page is always up to date with no copy to keep in step.
For pages he writes himself, Alfred builds from a kit of ready-made parts: headline figures, tables, charts, calendar heatmaps, filters and grids. They follow your light or dark mode, carry their figures for screen readers, and fetch nothing from anywhere else. A visitor only ever sees their own records through them, and a visitor who isn’t signed in sees none and is asked to sign in.
Parts of your own
Section titled “Parts of your own”When none of the ready-made parts fits and you’d want the same thing on more than one page (a goal ring, a streak counter), Alfred can write a part of your own that any of your pages can use. He can list them, change one, or delete one. You can have up to 20.
Your own parts only display things. They can’t send what they show anywhere, and a page that uses one shows images, audio and video only from the place itself, Butler’s own file storage, or embedded in the page. So a picture from another site won’t show on such a page: have Alfred upload it first rather than linking to it.
Buttons that answer
Section titled “Buttons that answer”A page can have buttons that ask something and get an answer back: “what should I play next?”, “pick tonight’s recipe”, “summarise this week”. Each one is answered by one of your reflexes, so the answer comes from code you approved, and the reflex can ask an AI when the question needs judgement.
- An answer can be remembered for a while, so pressing again for the same thing is instant and costs nothing.
- An answer that takes longer shows up on the page by itself when it’s ready, for up to about a quarter of an hour.
- Each place’s buttons have a daily spending limit and a limit on how many run at once, so a button pressed in a loop can’t run away with your usage.
Ask for one the way you’d describe it: “add a button that suggests a game from my backlog”.
Buttons that make something
Section titled “Buttons that make something”A button can do real work on Alfred’s side and hand back a file: export your animation as an MP4, shrink and crop a photo, turn a table into a spreadsheet. The reflex behind it makes the file (in a sandbox when it needs tools like ffmpeg), saves it into the page’s own files, and the page shows it or offers it to download.
- The file is kept in your drive with the page’s other files, counts against its room, and replacing it keeps the old one as a version you can get back.
- It’s checked for what it really is, like every file a page keeps: web pages, SVGs and scripts are never kept or shown.
- A button has to finish fairly quickly. Long work, like a long video, is better as a job Alfred runs in the background.
Ask for it in your own words: “add an Export as MP4 button that turns my frames into a video”.
Letting visitors use a button
Section titled “Letting visitors use a button”Buttons are yours alone unless you say otherwise. On a public page you can let visitors use a button too, and you choose which ones: “let people press the Remix button, but keep Reset to me”. Alfred only opens a button that’s safe for a stranger to run, and tells you when he does.
- Visitors have to be signed in to Butler. Someone who isn’t is asked to sign in.
- Every press spends your usage, within the place’s daily spending limit. Visitors together can only use part of it, so there’s always some left for you.
- Each visitor can only press so often, and the page as a whole takes only so many presses a minute.
- A visitor’s press runs with less than yours: it can’t use your keys or secrets, read your other places, your data or your cards, or act on your behalf. All a visitor gets back is what the button’s code hands them.
- Anything a visitor’s press makes goes into a folder of their own, which only they and you can see. The page needs to take files from visitors for that, so Alfred sets it up when a button that makes files is opened to visitors.
Alfred checking his work
Section titled “Alfred checking his work”After making or changing a page, Alfred can look at it the way you would: he opens it in his sandbox and takes screenshots on a phone and a desktop screen, in light and dark, and reads any errors it hit. He can also look at a public page as a visitor would, or as someone who isn’t signed in, to check what other people see. A private page only ever opens for you, so a look at one as somebody else just tells him it’s private. While he looks, nothing on the page can be changed. A look costs about as much as one sandbox command.
When he writes a page of his own, he does this without being asked: he checks it on a phone and a desktop screen, fixes what he finds, and checks again. If something still isn’t right after a few rounds, he stops and tells you what’s off rather than spending your usage on it.
Errors your visitors hit are kept too, for Alfred to read the next time you ask him about the place. They never message you or start anything by themselves.
If a page looks wrong to you, say so: “the chart on the dashboard is empty on my phone” gives him something to check.
Changing and removing places
Section titled “Changing and removing places”Ask Alfred. He can list your places, change one (“make the second question optional”, “make it public”), show you what was submitted, and delete one. Deleting a place removes its page, what was saved on it, its submissions, and its address. Files visitors sent stay in your drive until you delete them.
Places can also start automation: a reflex can run when a place is submitted or changed, when a file arrives, or when a tracker says something is due or low.