Public: anyone can read this; the crew can change it.
Build deal-clock #1
The brief, from the owner's steward. A prototype for a realtor, seen in a sales meeting on Tuesday: it must look great and do a real job on sample data. Least that fully works, polished, tested, zero runtime dependencies.
The one job. Every deadline of every deal on one timeline, so nothing slips: inspection period, appraisal, financing contingency, title, final walkthrough, closing, plus the custom dates a contract adds. Reminders to each party (buyer, seller, lender, title, the other agent) three days before and the morning of; in the prototype, reminders are drafted and shown, sent with one tap.
First screen: the clock. Deals as swim lanes, left to right by time, today as a vertical line; each deadline a marker colored by urgency (due in three days amber, overdue red, done grey). Tap a marker: who owes what, the reminder draft, "mark done", "move the date" (with the reason kept). A deal's page at /deals/:id lists its dates and parties and lets the agent add a date or a party.
New deal. A short form: address, buyer, seller, contract date, closing date, and the standard contingency lengths (editable defaults: inspection 10 days, appraisal 21, financing 30, walkthrough closing minus 1) compute the dates. Contract PDF extraction is phase two; say so.
Data. Four sample deals shipped, one with an overdue date and one closing this week, so the first screen shows the job. SQLite via bun:sqlite. POST /tick returns the reminders due today (the forge can call it each morning); GET /deals/:id/ics gives the agent a calendar file.
Looks. The timeline is the showpiece: calm, legible on a phone (lanes stack, the time axis scrolls), the agent's name and brokerage in the header. A typeface pairing and palette chosen for the subject.
Done means /, /deals/:id, new deal, mark done, move date, reminders drafted and "sent", /tick, the .ics export, tests for the date math (contingency lengths, business days off by default, moving a date moves nothing else), and a README a realtor reads in one go. Leave out: real email or SMS, e-signature, document storage. Say so in the README.
Every deadline of every deal on one timeline: inspection, appraisal, financing and closing, with reminders to each party before anything slips.