Directive anatomy

Build-along · ~12 min at your own keyboard

A directive is an SOP written for an AI employee: what we're doing, what comes in, the steps, what to do when it's weird, and how we know it's done. Five sections. Miss the edge cases and you get graceful, silent failure. One lead follow-up sent instead of the whole batch, no error thrown.

Your starter: Title pre-check directive

Instructions

Make it yours: Fill in your county's record sources and the instruments you see most, and set the stop line to the depth you actually search before an attorney takes over.

DIRECTIVE: title pre-check on [parcel number], [county]

Goal: list what the records show, in order, so I know what to hand the attorney. Not an opinion on title.

Read only: [the deeds I saved], [the assessor card], [the tax history].
Return:
1. Instruments in date order: type, grantor, grantee as spelled, book/page, date.
2. Gaps: any grantee who is not the next grantor, written as [PULL THE RECORD: instrument between X and Y].
3. Liens or notices mentioned in any instrument, quoted.
4. Stop at [n] instruments back or [year], whichever first, and say where you stopped.

Never write 'clear', 'marketable', 'sole heir' or 'has access'. Record first, then the number.

The coach checks that what you paste back is your own work. The starter pasted back unchanged won't pass.

Do this

0/4

Share what happened

Paste your five sections (trimmed) with the edge cases and threshold visible.