Turn the PSA into a critical-dates calendar

1 · Learn the move · Cognitive verifier

A missed date on a land contract costs the deposit, and land contracts hide more of them than most: survey objections, a zoning condition with an outside date, extension options that each need a notice and a fresh deposit. The move is to make the model show its work on every line and then check its own table. Quote the clause. Name the event the count runs from. State the count, and whether the contract says calendar or business days, and where it does not say, write that it does not. Then stop short of the last step. A model counts days the way it does arithmetic, nearly right, and a nearly-right date is the most dangerous entry in the file because it looks finished. So the date cell is yours to count on a real calendar, and the model's verification pass checks the quotes, the conventions and the chain between rows instead. Any count that runs from an event that has not happened - receipt of the commitment, delivery of the survey - is marked WAITING, never estimated.

Build a critical-dates table from the PSA clauses below. Columns: EVENT | CLAUSE QUOTED | TRIGGER | COUNT AND CONVENTION | DATE, always [YOU COUNT] | WHO ACTS | CONSEQUENCE QUOTED. Unstated conventions read UNSTATED. Triggers that have not happened read WAITING. Then verify your own table against five questions and list every correction.