20-year AI engineer / former hacker / local operator

I help working businesses stop losing the thread.

Plain-English AI systems for Appalachian firms, realtors, law offices, and operators who have too much living in email, PDFs, texts, calendars, and somebody's head.

> ask jdot what needs handled

See the approach
Find it Explain it Move it Prove it
// about

Context engineering in plain English: make the office remember.

A real estate team, law office, or local business does not need vendor jargon. They need to know which file is current, what the client said last time, which deadline matters, and what can be safely drafted or followed up now.

That is the work: organize the scattered context, keep proof beside every answer, and turn the repeated office grind into reliable next steps without taking judgment away from the people responsible.

// work
01

Real estate follow-through

Listings, buyers, inspection notes, lender emails, forms, showings, and promises kept together so the next action is obvious.

02

Legal office context

Client intake, timelines, filings, evidence packets, correspondence, and review-ready summaries with sources still attached.

03

Local business loops

Lead intake, scheduling, quotes, payments, follow-ups, job notes, and internal know-how turned into a system people actually use.

Map a workflow →
// context engineering

The tools change. The job stays the same: get the right context to the right person at the right moment.

Client intake Document recall Conversation history Source trails Deadline visibility Draft review Human approval Privacy boundaries Office handoffs Follow-up loops Plain-English search Local workflow maps
// now

Translating scattered office knowledge into plain-English systems.

Keeping sensitive client and business context private by default.

Turning the useful pieces into Fieldkraft-grade workflows for firms that need follow-through.