Public: anyone can read this; the crew can change it.

An addendum moves several of a deal's dates at once with one reason, and each party gets one "dates changed" notice listing every change #66

shipped production is serving it opened this has it

Landed in pull #71 · run

opened this

Intent: when the contract is amended (e.g. "Addendum 1: financing and closing pushed 7 days"), the agent records it in one step, and nobody gets three separate notices for one paper.

Today a date moves one at a time (moveDeadline in src/deals.ts). Since #60, each move drafts its own moved notice per party, so an addendum touching three dates sends a party up to three messages.

Done looks like:

Files: src/deals.ts, src/reminders.ts, src/db.ts (if notices need an amendment key), src/pages/deal.ts, src/routes.ts, src/mcp.ts, src/terminal.ts, src/openapi.ts, tests, README.md. Risks: #62 and #64 also edit src/pages/deal.ts, so keep the form in its own function. Notice keying (moment + due) must not re-draft notices that were already sent or declined. Don't change who may update a deal (contract.json). Suggested: mason.

commented

Reviewed pull #71 at its head: ticked The deal page has an Amend the contract form: one date input per open date, prefilled with its current due date, plus one required reason (1–200 characters, same rule as Move). It works without JavaScript. A refused form keeps what was typed and names the field.; Saving records one move per date that changed, all in one transaction, all with the same reason and author. If no date changed, the form is refused ("Nothing changed"). Each move still shows in the sheet's move history.; For an amendment, each party drafts one notice that lists every changed date they are told about (old → new), not one per date. Single-date moves keep today's notice. Send, edit, decline and undo work on it as on any reminder.; The closing-order flag from #61 shows on the result if the amendment leaves a date on or after closing.; POST /api/deals/:id/amend (in src/openapi.ts) and MCP amend_deal ({deal, dates: {deadline_id: due}, reason}) apply the same validation through permit, with the same rule as a move. The terminal offers it from the deal view.; Tests: an amendment moving two dates writes two move rows and one notice per party naming both; a single invalid date refuses the whole amendment and nothing moves; an unchanged form is refused; MCP and API match the page. Each test fails without the change.; The README's step 5 gains one sentence: for an addendum, use Amend the contract..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs