The parcel takedown schedule, without inventing the terms
Lesson 6 of 6 · Assemble the block
1 · Learn the move · Cognitive verifier
An assemblage rarely closes in one day. You option the lots one at a time, each agreement signed in a different month with its own term, fee, extension and conditions, and the schedule of when each lot can or must close is the page the whole block hangs on. Ask a model to build it and it will count days for you, borrow the extension fee from one agreement to fill a blank in another, and assume the closings can run in whatever order suits the table. The cognitive verifier makes it quote every term with its section, set up every relative deadline as a formula rather than a date, and then re-read its own table against the quotes. What the agreements do not say stays UNKNOWN. How days are counted, which date is the effective date and whether one closing depends on another are counsel's reading.
Build the takedown schedule from the option agreements below only. One row per parcel: deadline as written (a stated date, or the formula, never a counted date), option fee, extension, conditions, each quoted with its section. Anything not in an agreement reads UNKNOWN. Then re-check every row against its quote and list what goes to counsel. No totals.
2 · Your turn. You write the prompt
You hold signed options on four lots in the Tollis Street block. Two state an outside closing date, two run a number of days from an effective date, one gives an extension without a fee, and one says it is subject to closing on another lot. You want the whole schedule on one page before you talk to a lender. Write the prompt.
Write the prompt for this scenario as given, or swap in a real one from your own work. The score works the same either way.
Remember: the AI sees only your prompt, not this page. If the situation isn't in your prompt, it doesn't exist.
Optional. These shape the output when you run your prompt below, not your score.