Larkspur Studio · Office Overview · the absence view

What's supposed to be here, and isn't

The question a folder structurally cannot answer, because it is about what is not there · rendered Thursday, July 23, 2026

●

The client roster names four retainer clients. The agreements drawer holds three signed retainer agreements — and the missing one has a renewal date. Junebug Press renews September 15th, 54 days out, and the renewals machine cannot raise its hand about it, because it is built entirely out of the agreements it holds — and Junebug's was never filed.

Four retainer clients on the roster. Three signed agreements in the drawer. One renewal that falls between them.

Both lists are correct on their own terms, and neither file knows the other exists. Every cell below quotes the file under it.

What the client roster names · retainers

Meadowlark Foods — retainer agreement on file
Trailhead Coffee — retainer agreement on file
Coastal Cyclery — retainer agreement on file
Junebug Press — retainer, renews 2026-09-15 no signed agreement anywhere

"Active retainer clients — 4 … Expected: 4 signed retainer agreements on file — one per client above." — clients-roster.md. Kept by the studio manager; no machine reads it against the drawer.

What the agreements drawer holds

Meadowlark Foods retainer renews Aug 5
Trailhead Coffee retainer renews Nov 1
Coastal Cyclery retainer renews Oct 12
Harbor & Vine Kitchen — project agreement not on the retainer roster

Three retainer agreements, one per signed file in the drawer. The Junebug retainer is not among them — and the fourth agreement the drawer does hold is a fixed-fee project for Harbor & Vine, which is legitimately not on the retainer roster.

Why the machine cannot see it, in its own words. Its rule reads "one record per signed agreement on file, and only per signed agreement … a retainer with no signed agreement filed was never inside the set it watches, so it cannot raise its hand about that renewal" (the agreements machine's own governance). It is working exactly as written: its renewal flags are built out of the agreements it has, and a retainer with no agreement was never in the set it guards. The office spine already says so in the margin — calendar.md annotates the Junebug row "no signed agreement on file — tracked here only". Nothing here is broken. It is simply a gap that only exists between two files, so only something that reads both can name it. It has been added to the to-do list as a single item — the one thing on these pages no source machine could have put there.

Dated, and unwatched

the Sep 15 renewal above — 54 days

Open findings

each one names the file that expects it

Promises checked

five satisfied — they drop off on their own

Emitted to the to-do list

the one no machine could see

The three open

A missing document has no file to appear in a listing, no row in an index and no name to search for. The only way to see one is to read the document that expects it, and then go looking — so every row below names its expecter, and an absence with no expecter never reaches this page. "The studio has no privacy policy" is an opinion about what a good office would have; "the calendar carries a renewal on September 15th and there is no signed agreement behind it" is a finding.

Walked from this machine's promise-finding method — the four shapes of a promise (a roster that states a count · a calendar that names a dated document · a document that points at another · a machine output that names outstanding work). Eight promises were checked; five are satisfied and drop off, leaving the three below. Nothing here is characterised: a missing agreement may just not have been countersigned yet. The page reports the gap and names who would know.

#	What's missing	Who expects it — and says so	Where it would live
A roster / calendar names it, and nothing is filed behind it
1	A signed retainer agreement for Junebug Press, whose retainer renews 2026-09-15 — so the renewals machine has no record of it and raises no flag inside the 60-day window Shown in full at the top of this page — the one open row with a date and a named owner behind it. Emitted to the to-do list as a one-shot.	Office spine — two expecters clients-roster.md ("Expected: 4 signed retainer agreements"; three are filed) and calendar.md (carries the Sep 15 renewal, annotated "no signed agreement on file")	agreements/
The calendar names a dated document outside the window
2	A document behind the business-license renewal (2026-10-31) — the compliance row names it and nothing is filed against it outside the window	Office spine calendar.md — the compliance section carries the date; no filing sits behind it	office/
A roster names it, and it appears nowhere it should be watched
3	Junebug Press appears in no review minutes — one of the four retainers, and the only one the Q3 portfolio review never reached not a deadline — a blind spot A retainer getting no review airtime is a real fact about how it's being watched. Not emitted — there is no date and no single clear action, so it stays on the page, not on the to-do list.	Office spine + Meeting Notes clients-roster.md lists it as a retainer; the Q3 review minutes carry it to the next session	meeting-notes/

Also open, but not an absence. The two Ridgeline proof-printing invoices, RP-201 and RP-219, carry the same $2,400, the same description and the same service dates — a possible double-bill the vendor's own email flags. Those documents exist and are complete; what's in question is which one to pay, and that belongs to the bill-payer, not this page. It lives on the obligation calendar, in the past-due panel, because both invoices are real and present — absence means nothing is filed, and here two things are.

Rendered from roll-up.md §3, which carries every row on this page with its source path. Same roll-up, other cuts: what the office owes in the next 60 days · everything touching Meadowlark Foods. Rows drop off this page on their own as promises are satisfied — file the Junebug agreement and row 1 is gone the next run.