Turn a tax-sale statute into a calendar
Lesson 4 of 6 · Pick the county before the parcel
1 · Learn the move · Template pattern
Delinquent-tax work runs on a clock - notice, sale, redemption, deed - and the clock lives in state statute plus county practice. This is the most dangerous place to let a model count. It reads 'two years from the date of sale' and hands you a date, and the date can be wrong four quiet ways: which event starts the count, whether the start day counts, what happens when the last day lands on a weekend or holiday, and whether the county's practice differs from the text. The template fixes the shape so the counting cannot hide. Every row is an event; the trigger and the period are quoted from the text you pasted; the DATE column reads [NEEDS: computed and confirmed by counsel] unless a pasted document prints the date itself. What you get is a calendar skeleton to take to an attorney licensed in the state and to the county collector. It is not a calendar to rely on.
Build a table from the statute text and sale notice below. Columns: EVENT | TRIGGER (quoted) | PERIOD (quoted) | DATE | SOURCE | CONFIRM WITH. Never compute a date. DATE reads [NEEDS: computed and confirmed by counsel] unless a pasted document states the date outright. Then list every ambiguity in how a period is counted. [statute text] [county sale notice]
2 · Your turn. You write the prompt
You want to buy at, or after, the Sallow County tax sale. You pasted the tax-sale sections of your state's code as you found them and the county's published sale notice. Write the prompt that turns them into a calendar skeleton without the model counting a single day.
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.