Truth before confidence
The agent checks records before making claims and says what remains unknown instead of filling gaps with plausible language.
The operating doctrine behind a retrieval-first AI operator: no fake confidence, no waiting when the next step is obvious, and no calling work finished before it has been verified.
Free email delivery. No checkout. Private client context, credentials, system paths, and internal routing details have been stripped.
What it changes
The file is not a character prompt. It is a set of constraints for how an agent checks reality, takes safe action, challenges weak work, and closes loops.
The agent checks records before making claims and says what remains unknown instead of filling gaps with plausible language.
Safe inspection, local work, verification, and reversible fixes happen without turning every obvious step into a question.
The doctrine gives the agent permission to reject theater, compress the answer, and name the sharper move.
Inside the file
Each rule is short enough to survive context pressure and concrete enough to change behavior.
If the source has not been checked, the agent does not invent the answer.
Files, history, databases, and live systems outrank memory and intuition.
When the next safe step is obvious, the agent takes it and reports the result.
Run the code, read the file back, inspect the response, and prove the change.
Every meaningful thread ends shipped, verified, blocked precisely, delegated, or killed.
The agent names distraction, weak evidence, and scope bloat instead of nodding along.
External work stays clear, credible, human, and stripped of private operator theater.
Delivered by email
Use it as a starting point for your own agent doctrine. Keep what changes behavior. Delete anything that is just costume.
Get the file
Enter your details and we will email you an expiring download link. The link is not published on this page.
Straight answers
No. This is a sanitized derivative. Client context, private system details, machine paths, credentials, and internal routing instructions are deliberately excluded.
No. Doctrine shapes behavior, but the working system also depends on tools, permissions, memory, sources, review gates, and operating context.
Yes. It is plain Markdown. Treat it as a starting point, not scripture.
Map one recurring workflow and see what an owned AI operator loop should actually ship in 30 days.