An example Forge board — sample data, one made-up world⌂ Back to homepage← The board

📄 roll-up.md

On a real Forge this is a plain text file sitting in a folder you own. This page just shows what's inside it.

Office Overview — roll-up (Larkspur Studio · sample)

*The plain-text join the three views render from. Every line carries its source path. Read this when you want

the numbers without the HTML. Rendered from the sample world; window measured from 2026-07-23 (today) through

2026-09-21 (+60 days). Sources discovered by walking the world root — six machines + the office spine.*

§1 — Obligation calendar (date join)

Overdue

sample/meeting-notes/meetings/2026-07-09-q3-portfolio-review/action-items.md

Next 14 days

sample/bills/bills/ridgeline-print-RP-338.md

sample/meeting-notes/.../action-items.md

sample/agreements/agreements/meadowlark-retainer.md · sample/meeting-notes/.../action-items.md

Rest of the window

sample/bills/bills/fieldnote-illustration-FS-112.md

sample/office/calendar.md + sample/office/clients-roster.md · (renewals machine cannot see this — see §3)

Money arriving (in — its own band, never the owed total)

Cash timing (the question no single folder asks): $8,000 of fresh vendor bills fall due (Jul 28, Aug 12)

before the $16,800 of client invoices is due to land (both Aug 14). Nothing in this office joins a bill's

due date to an invoice's pay date — the bills and the invoices sit in different machines.

Past due (careful wording — no payment ledger in this office)

spring campaign"), same service dates (May 1–15). Ridgeline's own email calls the second a re-send: "if you

already have the first one, please just ignore this second copy" (sample/bills/bills/email-ridgeline-resend.txt,

undated). No payment ledger exists to say whether either cleared. The bill-payer's call, not this page's.

§2 — Entity dossier: Meadowlark Foods (name join)

FS-112 $3,200 (summer illustrations) · sample/bills/bills/

Both figures sourced; the invoice note and the meeting minutes both name the $2,500 add-on. No discrepancy —

the reconciliation is shown.

§3 — Absence view (expected-vs-present join)

Promises checked: 8 · open: 3 (walked per references/finding-absences.md; satisfied ones drop off.)

LEAD (dated, red — the flagship): A signed retainer agreement for Junebug Press.

retainer agreements on file." Three are filed (Meadowlark, Trailhead, Coastal); Junebug's is not.

agreement on file — tracked here 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." Working exactly as written.

is not on the retainer roster — legitimate: Harbor & Vine is a fixed-fee project, not a retainer. Two

lists that differ; both correct on their own terms.

Open (amber, outside window): A document behind the business-license renewal (2026-10-31,

sample/office/calendar.md) — the compliance row names it; nothing is filed against it. Where it would live:

office/.

Open (informational cross-read — NOT emitted): Junebug Press appears in no review minutes. It is one

of four retainers but the Q3 portfolio review (sample/meeting-notes/.../minutes.md) explicitly carried it to

the next session — a retainer getting no review airtime is a real fact only a cross-read can see. Reported,

not characterised, not emitted (no date, no single clear action).

Also open, but not an absence: the RP-201/RP-219 double-bill (§1) — those documents exist and are

complete; what's in question is which to pay, which belongs to the bill-payer.