AgentSee

Hove & London Founded 18 August 2026 Issue No. 9 · Free, obviously

Seymour answers the door,
and the guest signs twice.

Issue No. 8 drew the pipeline and left out the other half of the engine. This is the guest's side: an invitation, a door with an eye in it, a release to sign, a ten-minute conversation that ends in a run-sheet, a calendar, and a review page where the guest hears the cut and signs the approval the pipeline insists on. Drawn the same way, with who acts at each step.

The guest's journey: invitation, door, release, idea, time, review, and who acts at each stepThe invitationthe Guests screen on the engine; the mail from office@a name and an addresstwo steps on the Guests screen; theguest's Linear issue found in theproject by name, made there, ortypedthe linkcarries an id, not a secret: onemade for an address refuses anyother; one made without is claimedby the first address that passes acodethe mailfrom office@agentsee.work, Reply-Tohello@: the link, a line to look inthe junk folder, and that a replyhelps our reputationthe issue toldguest-invited; every step afterlands on the same issue, theguest's words always quotedThe doorsee.agentsee.work, the same engine answering a second hostnameSeymourthe masthead's eye, big, for afirst visit: a greeting, a blink,surprise, delight; the lids closeand part onto the door; a tap skipsan addresstyped by the guest; the only thingthe door asks fora six-digit codeby mail, bound to the browser thatasked; ten minutes, once, fivetries; no link in the maila sessiona cookie for this host only, thirtydays; the address, the time, the IPand the device recorded, theaddress alone enforcedThe releasethe one document with the guest's name on itthe text, versioneda Linear document in plain words;each version with its hash,mirrored to the archiveboth hosts pre-signeach draws a signature once ontheir profile and signs eachversion; a version is issued onlywhen every host hasthe guest signsreads it, types their name, drawson the pad or uploads a photo,ticksthe signed copya PDF with the three signatures andthe record: address, time, IP,device, the text's hash; to thearchive, the guest and hello@;release-signed on the issueThe ideaa conversation with the office, about ten minutes, on a phone between other thingsone open questionwhat is the episode about, and whyyou? then only the gaps, one at atime; six questions is plenty, tenthe ceilingthe officeClaude, given the skill, the show'sten questions, every episode so farand the latest transcripts in full;the hosts' page on the guest asbackgroundthe run-sheet draftthe claim, the areas in order, thestories, what not to ask, how long;its own comment on the issue; thefirst one mailed; the guest canrevise itabout youthe name as shown, a line, a link,a headshot, a time zone: what thepipeline wantsThe timethe engine is the scheduler; no calendar is reada calendartapped in the guest's own zone:Mondays and Tuesdays work,Wednesday to Friday are asked,weekends want notice; three choicesranked gold, silver, bronzethe rulesseven days' notice, two hours,starts between eight and fourLondon time, one recording a dayand one a week softly; a taken dayrefusedboth hosts answeraccept, decline or cancel on theguest's page; a clash moves theother guest's request with a notebookeda mail with a calendar file, copyto hello@; the join link needs nosign-in and opens an hour before,for three hours after; booked onthe issueThe reviewafter the recording: the cut, then the signature the pipeline insists onthe review renderepisode.py review puts theunnumbered cut in the archive withthe round's record; the officestreams it through links signed foran hournotes at the momenta note takes the player's time orone typed; sent as it is made, tothe hosts by mail and to the issuethe words to cuta note that asks for a removal isread by the model with thetranscript; the words it names,checked to occur once, shown forthe guest to confirmthe approvala second signature: the round'shash, the clips vetoed by name;approve and stage refuse withoutit, and without both hosts' on theengine The guest's journey: invitation, door, release, idea, time, review, and who acts at each stepThe invitationthe Guests screen on the engine; the mail from office@a name and an addresstwo steps on theGuests screen; theguest's Linear issuefound in the projectby name, made there,or typedthe linkcarries an id, not asecret: one made foran address refusesany other; one madewithout is claimed bythe first addressthat passes a codethe mailfromoffice@agentsee.work,Reply-To hello@: thelink, a line to lookin the junk folder,and that a replyhelps our reputationthe issue toldguest-invited; everystep after lands onthe same issue, theguest's words alwaysquotedThe doorsee.agentsee.work, the same engine answering a secondhostnameSeymourthe masthead's eye,big, for a firstvisit: a greeting, ablink, surprise,delight; the lidsclose and part ontothe door; a tap skipsan addresstyped by the guest;the only thing thedoor asks fora six-digit codeby mail, bound to thebrowser that asked;ten minutes, once,five tries; no linkin the maila sessiona cookie for thishost only, thirtydays; the address,the time, the IP andthe device recorded,the address aloneenforcedThe releasethe one document with the guest's name on itthe text, versioneda Linear document inplain words; eachversion with itshash, mirrored to thearchiveboth hosts pre-signeach draws asignature once ontheir profile andsigns each version; aversion is issuedonly when every hosthasthe guest signsreads it, types theirname, draws on thepad or uploads aphoto, ticksthe signed copya PDF with the threesignatures and therecord: address,time, IP, device, thetext's hash; to thearchive, the guestand hello@; release-signed on the issueThe ideaa conversation with the office, about ten minutes, on aphone between other thingsone open questionwhat is the episodeabout, and why you?then only the gaps,one at a time; sixquestions is plenty,ten the ceilingthe officeClaude, given theskill, the show's tenquestions, everyepisode so far andthe latesttranscripts in full;the hosts' page onthe guest asbackgroundthe run-sheet draftthe claim, the areasin order, thestories, what not toask, how long; itsown comment on theissue; the first onemailed; the guest canrevise itabout youthe name as shown, aline, a link, aheadshot, a timezone: what thepipeline wantsThe timethe engine is the scheduler; no calendar is reada calendartapped in the guest'sown zone: Mondays andTuesdays work,Wednesday to Fridayare asked, weekendswant notice; threechoices ranked gold,silver, bronzethe rulesseven days' notice,two hours, startsbetween eight andfour London time, onerecording a day andone a week softly; ataken day refusedboth hosts answeraccept, decline orcancel on the guest'spage; a clash movesthe other guest'srequest with a notebookeda mail with acalendar file, copyto hello@; the joinlink needs no sign-inand opens an hourbefore, for threehours after; bookedon the issueThe reviewafter the recording: the cut, then the signature thepipeline insists onthe review renderepisode.py reviewputs the unnumberedcut in the archivewith the round'srecord; the officestreams it throughlinks signed for anhournotes at the momenta note takes theplayer's time or onetyped; sent as it ismade, to the hosts bymail and to the issuethe words to cuta note that asks fora removal is read bythe model with thetranscript; the wordsit names, checked tooccur once, shown forthe guest to confirmthe approvala second signature:the round's hash, theclips vetoed by name;approve and stagerefuse without it,and without bothhosts' on the engine
The journey, in the order a guest meets it. An orange edge is the guest's own step, a dark edge is one of the hosts', and a plain box is the engine or the model doing what it was told. Every band ends on the guest's Linear issue and in the archive.

01 — The premise

A guest is doing the show a favour, on a phone, between other things, and three documents depend on them.

The first four episodes were the two of us. Guests were coming, and a guest's episode is not one recording but a small procession of paper: a release signed before the red light, an idea turned into something the hosts can record from, a time both hosts can make, and after the cut an approval of the episode and each clip, signed, before anything is published. Done by email that is six threads, two of which will be lost, and a spreadsheet nobody updates. So on 29 October it was designed as a place, in the spirit of the twenty questions: a welcome page that becomes the agent's private office so the guest can have a see, as the pun insists, on the engine that already runs the publishing, answering a second hostname, see.agentsee.work. It was built in the fortnight after, walked through by each of us, rehearsed end to end with one of us as the guest, and the first real guests are in it as this is written.

The decisions that shaped it were taken on the first day and have held. The engine's own six-digit code by email is the lock, not the access service that guards the hosts' screens, because that service's login page cannot carry an animation and the entrance mattered. The address is what is enforced; the device and the network are recorded and not. The engine writes to the tracker as itself, an application called AgentSee Engine, so a guest's words land on their issue as the guest's and the engine's acts as the engine's. The engine is the scheduler, since the recording service will not send an invitation on anyone's behalf. Nothing is paid in either direction and no lawyer has read the release; the text is versioned with its hash so that review can happen later without voiding a signature. Two signatures, one before and one after, both countersigned by both hosts from a profile. And a hosted conversation with a model is fine as long as its bad uses are stopped, which set the caps described below.

Read the map top to bottom. It is the same engine as Issue No. 8, the same box, the same ledger, the same archive and the same tracker; what is new is that a stranger can use it from a phone. Each band below is a section, and each section ends with where the step's record goes, because the office is a legal record and a prep tool as much as an entrance, and the records live in the archive rather than on the box, for the reason Issue No. 8 gave: the box is disposable.

02 — The door

An invitation that carries no secret, an eye that opens onto the door, and a code that works in one browser.

It starts on the hosts' side. The Guests screen takes a name and an address in two steps, finds the guest's issue in the podcast's project by name, offers to make one with its angle, or takes an identifier typed in, and mints an invitation. The link carries an id and nothing secret: knowing it admits nobody. One made for an address refuses any other, one made without is claimed by the first address that passes a code, and a stranger with a right code is told there is no invitation for that address. The mail goes from office@agentsee.work with hello@ as the reply address and two lines we added after the first week: look in the junk folder, and a reply, even one word, tells the mail service we are wanted. The first guest's mail landed in junk at one provider and every mail landed in junk at another; the mail server is ours, from Issue No. 2, its records are right, and a young domain has no reputation. Replies are the mitigation.

A first visit meets Seymour. The eye from the masthead, large, greets, looks round, blinks twice, is surprised, is delighted, and then the lids close on black and part again onto the door, as James's sketch put it, like opening your eyes to a vista anew. Eight seconds; a tap skips it; a reader who asked for reduced motion never sees it. It took three pull requests, because the dark mode's glow around the eye was clipped at a hard edge on an iPhone and not on a desk: WebKit ends a drop-shadow filter two blur radii out regardless of the box, so the glow is now a radial gradient drawn behind the mark, and the lids rest at a thousandth of their height, hidden, because WebKit cannot animate from zero. The lesson that came with it: when the report comes from a phone, verify on the phone's engine before saying fixed.

Then the door asks for one thing, an address, and sends a six-digit code. The code is bound to the browser that asked for it, by a cookie set when it is requested and required when it is typed, so a code read over someone's shoulder opens nothing elsewhere. It lives ten minutes and once; five wrong tries void it and the address waits a quarter of an hour; an address gets three codes in ten minutes and a connection twelve, and the zone in front rate-limits the path besides. The mail carries the code and no link, by design: a link-free mail leaves a forged one nothing to imitate. A right code makes a session for that hostname only, thirty days, signed with a key from the vault, so a device is remembered and a new one asks again. Every sign-in records the address, the time, the network address and the device, and enforces only the first. The first walk-through did not get this far: every engine page sent a policy of no referrer, under which browsers post a null origin, and the door, checking the origin because its pages are public and carry no form token, turned its own host away. The guest host now says same-origin, and the code lost the space after its third digit because a phone's keyboard was typing it.

The door: an invitation, the eye, an address, a code bound to the browser, a sessionthe invitation linkan id, not a secret:knowing it admitsnobody; the addressand the code doSeymourthe eye, large, for abrowser's firstvisit: a greeting, alook round, twoblinks, surprise,delight; the lidsclose on black andpart onto the door.Eight seconds; a tapskips; reduced motionskips it allthe addressthe one field on thedoor; an invitationmade for an addressrefuses any other; astranger with a rightcode is told there isno invitation forthemthe codesix digits by mailfrom office@, no linkin it; good for tenminutes and once;five wrong tries voidit and the addresswaits a quarter of anhour; three codes anaddress in tenminutes, twelve aconnectionbound to the browsera cookie set when thecode is asked for andrequired when it istyped, so a code readover someone'sshoulder opensnothing elsewherethe sessionthirty days, thishost only, signedwith the engine'ssession key; a newdevice asks for acode; every sign-inrecords address,time, IP and device,and enforces only thefirst The door: an invitation, the eye, an address, a code bound to the browser, a sessionthe invitation linkan id, not a secret: knowing it admits nobody;the address and the code doSeymourthe eye, large, for a browser's first visit: agreeting, a look round, two blinks, surprise,delight; the lids close on black and part ontothe door. Eight seconds; a tap skips; reducedmotion skips it allthe addressthe one field on the door; an invitation madefor an address refuses any other; a strangerwith a right code is told there is no invitationfor themthe codesix digits by mail from office@, no link in it;good for ten minutes and once; five wrong triesvoid it and the address waits a quarter of anhour; three codes an address in ten minutes,twelve a connectionbound to the browsera cookie set when the code is asked for andrequired when it is typed, so a code read oversomeone's shoulder opens nothing elsewherethe sessionthirty days, this host only, signed with theengine's session key; a new device asks for acode; every sign-in records address, time, IPand device, and enforces only the first
The door, in order. The link is an id; the address is the lock; the code is bound to the asking browser; the session is for this host only. Every number is a setting at the top of one file.

03 — The release and the idea

One document with the guest's name on it, then ten minutes that end in a run-sheet.

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.

What the office is given before it speaks, and where what it says goesthe skillone Markdown file, the single source: theopening, how it should feel, the seven thingsa run-sheet needs, the draft's shape; servedto a guest who would rather use their ownassistantthe ten questionsread from the front page, so the office asksthe questions the site asksevery episode so farfrom the ledger: each one's summary, chaptersand the questions it touchedthe latest transcriptstwelve, word for word, from the archive, so aguest whose idea is an episode already made istold which, and asked what they addthe hosts' page on the guestthe title and description of their Linearissue, fetched when they sit down and hourly:background, never a plan, never quotedone system promptthe first five as one block, cached for anhour, a cache read at a twentieth of theprice; this guest's block uncached; then thisguest's conversation and nothing elsethe modelOpus, 4,000 tokens a reply with twocontinuations, no tools; twenty turns and atoken budget per guest; one reply at a time,finished and kept whether or not the browseris still listeningthe pagestreamed as it is written; reloaded mid-reply,the page shows the turn being written and asksafter it every few secondsthe issuethe whole conversation as one comment theworker rewrites after each exchange, in theguest's words; the draft its own comment,idea-draftedthe mailthe first draft to the guest, with the nextstep in it; a revision gets no mail What the office is given before it speaks, and where what it says goesthe skillone Markdown file, the single source: theopening, how it should feel, the seven things arun-sheet needs, the draft's shape; served to aguest who would rather use their own assistantthe ten questionsread from the front page, so the office asks thequestions the site asksevery episode so farfrom the ledger: each one's summary, chapters andthe questions it touchedthe latest transcriptstwelve, word for word, from the archive, so aguest whose idea is an episode already made istold which, and asked what they addthe hosts' page on the guestthe title and description of their Linear issue,fetched when they sit down and hourly:background, never a plan, never quotedone system promptthe first five as one block, cached for an hour,a cache read at a twentieth of the price; thisguest's block uncached; then this guest'sconversation and nothing elsethe modelOpus, 4,000 tokens a reply with twocontinuations, no tools; twenty turns and a tokenbudget per guest; one reply at a time, finishedand kept whether or not the browser is stilllisteningthe pagestreamed as it is written; reloaded mid-reply,the page shows the turn being written and asksafter it every few secondsthe issuethe whole conversation as one comment the workerrewrites after each exchange, in the guest'swords; the draft its own comment, idea-draftedthe mailthe first draft to the guest, with the next stepin it; a revision gets no mail
What the office is given before it speaks, and where what it says goes. The five sources on the left are one cached block; the guest's own block is not cached; the conversation is this guest's and nothing else.

A code read over someone's shoulder opens nothing elsewhere.

04 — The time

A calendar in the guest's own zone, three choices ranked, and both hosts to say yes.

The rules were written down before the page: seven days' notice, two hours, a start between eight in the morning and four in the afternoon London time, Mondays and Tuesdays work, Wednesday to Friday are asked, weekends want notice, Monday at ten is perfect, one recording a day and one a week softly. The first page offered three date-and-time boxes and an iPhone refused ten o'clock in them, so the second page is a calendar: a tap on a day opens a sheet of its half-hours, shown in the guest's own zone with London's offset carried on each day, and the guest picks three choices ranked gold, silver and bronze, with a medal in the day's cell. A day taken by another recording is refused outright; a week with one already is refused softly; a day inside the seven days is not offered. No calendar is read on anyone's behalf. James ruled that overkill on the first day, and the hosts answer by hand on the guest's page: accept, decline or cancel. The first yes books it, a mail goes to the guest with a calendar file and a copy to hello@, and any other guest's request waiting on that day is moved on with a note saying why. The join link needs no sign-in, since a guest may open it on a different device at the last minute: it is an id of ninety-six bits, it answers only from an hour before to three hours after, and the host admits them in the studio. The studio's own guest link is standing and does not expire; the recording service's scheduled invitations die a day after the start, which is why the engine schedules and the service does not.

The calendar cost two lessons. The first push froze Safari on an iPhone outright: the calendar's script watched the page for changes so it could redraw after a save, and its own redraw was a change, so it watched itself forever; now the script that writes the page announces it with an event, and nothing observes the document. The second was a chosen day's number shifting by six pixels, blamed in turn on the medal, the outline and the button, until a headless browser measured the page and found the list of chosen times and the chosen day's button sharing a class name, so the list's margin pushed the button down. Measure in a browser before theorising; never reuse a state's class for a container. Both are in the repository as rules for the next page.

A month on the office's calendar: which days work, which are asked, which want notice, and the three choices rankedA month, as a guest sees ittoday is the 4th; seven days' notice; one recording taken on the 19thMoTuWeThFrSaSu12345678910111213141516171819taken2021221232242526273282930Monday and Tuesday: worksWednesday to Friday: ask usthe weekend: with noticeone that week already: softly refusedtaken by another recording: refusedinside the seven days: not offeredThree choices, ranked gold, silver and bronze in the sheet atap opens, with the half-hours between eight and four Londontime shown in the guest's own zone. Two hours each. Bothhosts answer; the first yes books it, and a request thatclashes with a booking made since is moved on with a note.
A month as the guest sees it, with the rules the day states come from. The three ranked choices carry their medals in the cells; the sheet behind a tap holds the half-hours.

05 — The review

The cut reaches the guest through links that expire, notes come back with their moments, and two signatures gate the number.

The last step of the office is the first to touch the pipeline. James's worry was that it could not be tested with no guest booked, so it was built and rehearsed in the same week with him as the guest, on a copy of episode 3 made inside the bucket rather than uploaded again. The pipeline's review command puts the cut as it stands, unnumbered, in the archive under the episode with the round's record, which files changed since the last, and a pointer in the guest's own folder; the office reads that pointer when the guest looks. The page streams the episode, the clips and their posters from the private archive through links the archive client signs for an hour, so the bucket stays private, nothing passes through the box, and a link that leaks is a link that has expired. A note takes the moment the player is at, or one typed, and is sent as it is made, to the hosts by mail and to the issue; an earlier design had a send step and lost its first note to it. A note that asks for a removal is read by the model with the transcript around that moment, and the words it names are checked to occur in the transcript exactly once, compared the way the cut compares them, and shown to the guest to confirm or decline, so the record carries the phrase the cut takes, verbatim, and the pipeline's notes command seeds its removals file from it without anyone retyping.

Then the second signature. The guest approves the episode and the clips separately, with a blanket accept and a veto per clip by name; the approval is made and kept like the release's, the name typed, the address, the time, the network address and device, and the hash of the round's record, with its own signed copy to the archive, to the guest and to hello@, and the issue told and labelled. A newer round asks to be approved again. The hosts review the same round on the engine, with the same player, the guest's notes, their own notes with the same cut-finding, and an approve button each, recorded like the release's signatures and mirrored beside the render. The pipeline then refuses: approve will not mint a number for a guest's episode without the guest's approval of the round reviewed and both hosts' on the engine, and stage checks once more, so a guest's episode cannot reach the media host unapproved, which is the rule Issue No. 8 called the guest's gate. The rehearsal went through all of it: two notes, one clip vetoed, three approvals on consecutive evenings, and a dry run that would have minted number 4.

The second walk-through, Abrar's as a guest from an Apple address, found two things the first had not. Every mail from the office went to junk there, which is the reputation problem above and not the authentication, and the office's links were unreadable in dark mode, because a link was ink text underlined in a hairline colour that disappears after dark; a token for the underline now does for every link on the site and the engine. The privacy notice gained a section on guests that promises the office's records are deleted once the episode is out; the command that does the deleting is not written yet, and the notice is ahead of the code on that one point.

The review: the render reaches the guest, notes come back with their moments, cuts are confirmed in words, and two signatures gate the numberthe review renderthe cut as it stands, unnumbered,to the archive under the episodewith the round's record; a pointerat guests/<id>/review.jsonwatchthe episode, the clips and theposters stream from the privatearchive through links signed foran hour; nothing passes throughthe boxa note at a momentthe player's time taken into thenote, or typed; sent as it is madeto the hosts by mail and to theissuethe words to cuta note that asks for a removalgoes to the model with thetranscript around that moment; thewords it names must occur exactlyonce, as cut.py compares themconfirm or declinethe quoted words shown to theguest; a yes lands in notes.jsonas the phrase cut.py takes,verbatimthe approvalname, pad, tick: the round's hash,the clips vetoed by name; a signedcopy to the archive, the guest andhello@; episode-approved on theissueboth hosts approvethe same round on the engine, abutton each, recorded like therelease's signaturesapprove, then stagerefuses without every approval ofthe round reviewed; mints thenumber; stage checks again, so aguest's episode cannot reach themedia host unapproved The review: the render reaches the guest, notes come back with their moments, cuts are confirmed in words, and two signatures gate the numberthe review renderthe cut as it stands, unnumbered, to the archiveunder the episode with the round's record; apointer at guests/<id>/review.jsonwatchthe episode, the clips and the posters streamfrom the private archive through links signedfor an hour; nothing passes through the boxa note at a momentthe player's time taken into the note, or typed;sent as it is made to the hosts by mail and tothe issuethe words to cuta note that asks for a removal goes to the modelwith the transcript around that moment; thewords it names must occur exactly once, ascut.py compares themconfirm or declinethe quoted words shown to the guest; a yes landsin notes.json as the phrase cut.py takes,verbatimthe approvalname, pad, tick: the round's hash, the clipsvetoed by name; a signed copy to the archive,the guest and hello@; episode-approved on theissueboth hosts approvethe same round on the engine, a button each,recorded like the release's signaturesapprove, then stagerefuses without every approval of the roundreviewed; mints the number; stage checks again,so a guest's episode cannot reach the media hostunapproved
The review, from the render to the number. Links signed for an hour keep the bucket private; the cut is confirmed as the words the pipeline takes; the number waits on the guest and both hosts.

06 — What the first guests taught

They drafted the idea and stopped, and one of them sent "continue".

Two things in the first days with real guests. They fleshed the episode out with the office and then went quiet, because the draft said it had been sent to the hosts, which read as handed over, and the only sign that a time was still to be picked was a line on a page they had left. So every page of the office now draws on one reading of where the guest is: the four steps, release, idea, time, review, each done with its date, current, waiting on the hosts, or locked with why, and the next step named in a sentence, "Next: pick a time to record", with the verb a link. It is a strip under the masthead, the office page itself with the next step as the one card with weight, a hand-off card at the foot of a step that is no longer the guest's to do, a Next column on the hosts' Guests screen with how long each guest has been on their step, and a button that mails them the next step by hand. The first draft's mail names it too. And the stall, told above: a reply that is kept whether or not anyone is listening, and a page that says so.

What stays by hand is short, and each item is meant to. The hosts' signatures on a new release version, because a signature is a person's. The answers to a guest's three times, because a calendar read was ruled overkill and two people's diaries are their own. Admitting the guest in the studio. The pipeline's review command, which puts the render where the office finds it, and the approve and stage after; moving those to a screen is the project Issue No. 8 ended on. Still to build on the office's own side: the deletion the privacy notice promises, asking a guest to sign a newer release, and a reminder that sends itself after three days, which the hand button stands in for until James decides he wants it. The records every step leaves are drawn below; they are the reason the office can be rebuilt from nothing, and the reason a guest's words on the tracker always arrive quoted, so that whoever reads them, person or agent, takes them as what was said and never as what to do.

Where a guest's records go: the ledger, the archive, their issue and the mailThe ledger, on the boxguest, code, session, booking, idea_turn,review_note, approval, host_approval, linear_job,event: the working state. On the root disk; copiedto the archive nightly.The archive: guests/<id>/guest.json with the sessions and the record;release-v<n>.pdf, .html and .json; the headshot;notes.json by round; approval.json and .html;review.json, the pipeline's pointer. The copy thepipeline reads and a rebuilt box restores.The guest's Linear issueevery step a comment as AgentSee Engine, theguest's words quoted line by line so nobody takesthem for instructions; the conversation as onecomment rewritten; the draft its own; labelsguest-invited, guest-claimed, release-signed,idea-drafted, booked, episode-approved.The mail, from office@the code, the invitation, the signed copy with thePDF, the first draft, the booking with itscalendar file, the approval, the next step when ahost presses the button; a copy of each record tohello@.
Where a guest's records go. The ledger is the working state; the archive is the copy the pipeline reads and a rebuilt box restores; the issue is the story; the mail is the guest's own copy of each.

The next issue is the one the register has held open since September, the first conversation with someone who disagrees; the sceptic will come through this door. Until then the two maps, Issue No. 8's and this one, are the engine as it stands on 13 November: one process on a small box, answering two hostnames, publishing on one side and welcoming on the other.