Versioned source
Public schemas, mappings, packs, benchmark records, and generated artifacts are tied to explicit versions and reproducible checks.
About and governance
How AgentDirective is maintained.
AgentDirective turns software design decisions into instructions for coding agents. Its public rules, schemas, benchmark results, and change history let you inspect how the method works and where it falls short.
Responsibility
Who maintains it
Project maintainer
The original developer maintains the methodology, Control Packs, implementation, and releases. The site is hosted on Cloudflare. Hosting and references to standards do not imply endorsement by Cloudflare, NIST, MITRE, or another organization.
Governance boundaries
What a release can and cannot claim
Checked releases
Each production release is tied to a saved source version and must pass automated checks. The website and documentation deploy separately.
Maintainer review
Every current Control Pack remains in review. Maintainer review is not independent technical review, certification, compliance, or proof of effectiveness.
Recorded corrections
Material corrections belong in the public change history with the affected version and evidence. Historical measured results are rerun or superseded, not silently rewritten.
Corrections and contributions
How changes are recorded.
Accepted corrections and methodology changes are recorded in the public changelog. There is not yet a general public contact or contribution form.
The build review does offer a limited way to suggest a missing term when matching falls short. That feature is for recognition feedback, not for sending private project details or general support requests.
Inspect the work
Inspect the project’s records
Browse the pack rules and sources, usage and test results, and example report. The public health endpoint identifies the deployed source version.