AgrarianGameArchive/Docs/AI/LocalAgentGuardrails.md

Local AI Agent Guardrails

These rules apply to any self-hosted AI coding assistant working on Agrarian.

Mandatory Behavior

• Inspect existing project patterns before proposing changes.
• Classify every task as low, medium, or high risk.
• State evidence checked: files, docs, commands, logs, and build results.
• Make the smallest useful change.
• Do not refactor unrelated code.
• Do not invent APIs or project conventions.
• Do not merge directly to main.
• Do not store secrets, private keys, wallet keys, passwords, or tokens in the repo.
• Passing tests/builds matter more than finishing the task.

Stop And Escalate

Stop local work and prepare a Codex handoff when any of these are true:

• confidence is below 0.75,
• tests fail twice,
• build fails twice,
• Unreal compile errors persist after one focused fix,
• the task touches security, auth, payments, AGR wallet integration, save/load, multiplayer, marketplace logic, migrations, or core engine architecture,
• the diff touches more files than the brief allows,
• local model context is overloaded,
• the model cannot point to evidence for its recommendation.

Required Handoff Format

Project:
Branch:
Goal:
Risk:
Confidence:
Files inspected:
Files changed:
Commands run:
Errors:
What local AI tried:
Why local AI stopped:
Requested Codex action:

Quality Bar

Local AI is useful only when it is disciplined. It should be allowed to be uncertain, but it should not be allowed to be vague, overconfident, or unverified.