The release is the one document a guest signs before anything is recorded, and the
office treats it as the legal record it is. Its text is a Linear document in plain words,
read by both hosts; the engine takes each version in with its hash and mirrors it to the
archive. Each host draws a signature once on their profile, or uploads a photo of one, and
signs each version there; a version is issued, and shown to guests, only when every host
has signed it, because countersigning afterwards would be the wrong order and no real
copy should carry a placeholder. The guest reads it in the office, types their name, draws
on the pad with a finger or a mouse, ticks and signs. Recorded with the signature: the
address the code verified, the time, the network address, the device, and the text's
hash, which is what makes a simple electronic signature worth something. The copy is a
PDF with the three signatures and the record on its last page, made by the engine's one
Python dependency with a font embedded so a name in any alphabet sets; the same as an
HTML file and a JSON record, all three in the archive, the PDF to the guest by mail with a
copy to hello@, and the issue told and labelled. One lesson from the first week: the pad
draws in the theme's ink, which is near-white in dark mode, and an uploaded image keeps
its own, so one host's signature vanished on the page and the other's on the PDF; every
signature is now normalised to one ink on transparent as it is saved. Not built: asking a
guest to sign a newer version. A later version never voids an earlier signature; the
guest's copy is the version they signed.
Once the release is signed the guest sits down with the office. The first version
was the twenty questions' shape, one question at a time to a brief, and James called it,
after a day with it, a particularly onerous experience for a podcast guest: the client
intake stretched too far. So it was rewritten on 1 November to start open and ask only for
what is missing. The office says what it is, that this takes about ten minutes and ends
in a draft the guest can change, and that nothing is published until they have approved
the recording, and then asks: what is the episode about, and why you? After the first
answer it says in two or three sentences what it thinks the episode is and asks whether it
is warm. There are seven things a run-sheet needs, from the claim to whether it is thirty
minutes or an hour, and when one answer gives three of them it takes all three; six
questions is plenty and ten is the ceiling. It mentions the show's ten questions at most
once, when the episode plainly wants one. And it has read the show: every episode so far
by summary and chapters, and the latest transcripts word for word, so a guest whose idea
is an episode already made is told which, warmly and specifically, and asked what they
would add or argue with. The skill is one Markdown file and the only source; a guest who
would rather take it to their own assistant is handed the same file and pastes the
run-sheet back.
The controls are what make hosting it safe. Only a signed-in guest who has signed the
release; twenty turns and a token budget per guest, with the skill and the transcripts as
one block cached for an hour, a cache read costing a twentieth of the price and not
charged to the budget; no tools; the model sees this guest's conversation and nothing
else; one reply at a time per guest. The reply streams to the page as it is written, and
since 12 November it is finished and kept whether or not the browser is still listening,
after a guest sent a message, saw nothing for long enough to call it stalled, sent
"continue" and was told the office was still writing. The page now shows the turn being
written when it comes back mid-reply, asks after it every few seconds, says what the wait
is while the model is silent, and keeps a heartbeat on the line so no proxy gives up. The
whole conversation is kept on the guest's issue as one comment the worker rewrites after
each exchange, in the guest's words; the draft is its own comment, and the first one is
mailed to the guest with the next step in it. Beside the conversation a short form
collects what the pipeline wants: the name as shown, a line, a link, a headshot and a
time zone. The hosts' own page on the guest, the title and description of their issue, is
read in as background, hourly at most, with a standing instruction never to quote it: the
guest decides what the episode is about.