Build the parcel takedown schedule without inventing the terms
Rung 8 of 10 · Cognitive verifier
1 · Learn the move · Cognitive verifier
A finished lot or pad takedown schedule is where a builder or end-user deal lives or dies on the calendar and the escalator. Miss a takedown date or fumble the price step and a quarter of revenue moves or evaporates. The move is the cognitive-verifier pattern: make the AI lay out the schedule row by row, each term quoted from the term sheet you paste, each takedown date derived in the open from the pasted start date and pace, then run a critique pass that re-checks every row against its quote. It schedules only what the paste supports. A term the sheet is silent on, a deposit, an option fee, stays UNKNOWN and routes back to confirm, never invented to make the table look finished. The escalated price per period is compound, so it gets set up as a formula and tagged, not multiplied out in the chat. Interpretation and the deal terms belong to you and counsel; this is not investment advice.
Build me a takedown schedule for the builder/user deal, 80 lots or pads, and total up the revenue.
2 · Your turn. You write the prompt
You're a land developer structuring finished lot or pad takedowns to a builder or commercial user. The term sheet gives 80 lots or pads, a 20/year takedown pace, first takedown 2027-Q2, a base price of $95,000 each, and a 4% annual escalator, but it says nothing about the deposit or option fee. You want the takedown schedule and revenue framework built now, WITHOUT the AI inventing the deposit, inventing a pace or escalator not on the sheet, or computing the escalated prices and revenue total inline. Write that prompt.
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.