An example Forge board — sample data, one made-up world⌂ Back to homepage← The board
FICTITIOUS DOCUMENT — FORGE DEMO ONLY · specimen data built for a product demonstration · no real firm, client, vendor, bank, or person is depicted
Larkspur Studio · Office Overview · Nora Ellison, Studio Manager

The obligation calendar

Everything this studio owes anyone between 2026-07-23 and 2026-09-21 · merged from three machines, one desk of vendor bills and the office spine · rendered Thursday, July 23, 2026
One deliverable is already three days overdue — the revised brand proposal owed to Meadowlark. Then $8,000 of vendor bills falls due before August 12th — but the $16,800 of client invoices that would cover them isn't due to land until August 14th, after both. And a retainer renewal 54 days out (Junebug, Sept 15) sits in a folder the renewals machine cannot see, because no signed agreement was ever filed for it.
Already overdue
1
since Jul 20 · Nora Ellison
Bills due in the window
$8,000
Jul 28 · Aug 12
Arriving
$16,800
both Aug 14 — after the bills
Past due, no payment record
$6,700
three bills · one a possible double

Everything owed, in date order

One row per dated obligation. The From column names the machine or folder each row was lifted out of — four different sources on one timeline, which is the whole point of this page. Money coming in is kept out of this table on purpose; it has its own band below.
DateDaysWhat's owedOwner / clientAmountFrom
Overdue
2026-07-20−3 Send the revised brand proposal to Meadowlark Foods 3 days late
Owed to the studio's anchor retainer client; approved at the Q3 review.
Nora Ellison Meeting Notes action-items.md
Next 14 days
2026-07-285 Ridgeline Print RP-338 — offset print run, Trailhead seasonal packaging Ridgeline Print Co.$4,800 Bills RP-338
2026-07-318 Confirm venue + catering for the Junebug Press launch event Priya Shah Meeting Notes action-items.md
2026-08-0513 Meadowlark retainer renews — send the updated SOW
The renewal date is on the agreement; the SOW task is the owned action.
Nora Ellison Agreements + Meeting Notes meadowlark-retainer.md
The rest of the window
2026-08-1220 Fieldnote Studios FS-112 — spot illustrations, Meadowlark summer campaign Fieldnote Studios$3,200 Bills FS-112
2026-09-0847 Prep the Q3 close review deck Devin Cole Meeting Notes action-items.md
2026-09-1049 Q3 close review Larkspur Studio Office spine calendar.md
2026-09-1554 Junebug Press retainer renews no machine sees this
There is no signed agreement for Junebug anywhere in the drawer, so the renewals machine has no record of it and its renewal raises no flag. The client roster lists Junebug as a retainer and the calendar carries the date — those two files are the only places in the office this renewal exists. Shown in full on the absence view.
Junebug Press[confirm] Office spine — no agreement record calendar.md · clients-roster.md
Next after the window: Harbor & Vine project agreement ends 2026-09-30 · Coastal Cyclery retainer renews 2026-10-12 · business-license renewal 2026-10-31 · Trailhead retainer renews 2026-11-01.

Money arriving — kept separate on purpose

A client invoice you've sent is cash coming in, not something owed. It belongs on this page because it answers "can we cover the bills?" — but folding it into the owed total is how a page tells someone they're covered when they aren't.
Due inInvoiceClientAmountFrom
2026-08-14 INV-2026-107 — July retainer + photography add-on in Meadowlark Foods$12,000 Billing INV-2026-107
2026-08-14 INV-2026-105 — July retainer + packaging proofs in Trailhead Coffee$4,800 Billing INV-2026-105
The timing, in plain words. Eight thousand dollars of vendor bills falls due first — $4,800 to Ridgeline on July 28th and $3,200 to Fieldnote on August 12th. Sixteen thousand eight hundred of client money is due to arrive on the 14th, after both bills are due. Nothing in this office can see that on its own: the bills sit in one machine and the client invoices in another, and no folder joins a due date to a pay date. This page joins them because it reads both.

Already past due — and what this office can and cannot tell you

There is no payment ledger anywhere in this office, so "unpaid" is not a knowable fact and this table does not claim it. Each row says only what is knowable: the due date has passed, and what — if anything — some document says about payment.
BillVendorDueAmountWhat the office says about payment
NG-77 Northgate Web Hosting2026-06-28$1,900.00 Nothing on file.
RP-201 Ridgeline Print Co.2026-07-05$2,400.00 Same amount, description and service dates as RP-219 possible double — see the note under this table. No payment record either way.
RP-219 Ridgeline Print Co.2026-07-19$2,400.00 Ridgeline's own email calls this a re-send of RP-201 possible double — see the note. No payment record either way.
$6,700.00 across three bills has no payment record of any kind; $2,400 of it may be a duplicate.
One proof-printing job, two invoices, and no way to tell if the studio paid one or both. RP-201 and RP-219 are two different invoice numbers carrying the same $2,400.00, the same description — "proof printing, Meadowlark spring campaign" — and the same service dates, May 1–15, 2026. Ridgeline's own email calls the second a re-send: "if you already have the first one (RP-201) on file, please just ignore this second copy — no need to pay it twice" (email-ridgeline-resend.txt, undated). Three files, none of which is wrong on its own: the vendor said ignore one, and nothing in this office joins a cover email to a payment record. Which to pay is the bill-payer's call, not this page's.
Rendered from roll-up.md, which carries every figure on this page with its source path. Same roll-up, other cuts: everything touching Meadowlark Foods · what's supposed to be here and isn't. This page is a snapshot of Thursday, July 23, 2026 and goes stale honestly — nothing watches for changes; ask for it again and it re-reads the office.