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

01

Versioned source

Public schemas, mappings, packs, benchmark records, and generated artifacts are tied to explicit versions and reproducible checks.

02

Checked releases

Each production release is tied to a saved source version and must pass automated checks. The website and documentation deploy separately.

03

Maintainer review

Every current Control Pack remains in review. Some carry a recorded maintainer review; none has been independently reviewed yet. A pack can be marked released only with an independent technical and evidence review on record.

04

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.

Reuse

What you can reuse, and on what terms

CC BY 4.0

Packs, data and documentation

Control Packs, failure patterns, benchmark datasets and results, platform vocabulary, and the documentation text may be shared and adapted with attribution to AgentDirective.

Apache 2.0

Schemas and code samples

The published JSON schemas, the example code in packs and documentation, and generated directive files may be used in your own projects, including commercially.

Not covered

The hosted service

These licences cover the published artifacts, not the website's implementation or the AgentDirective name. Cite the pack or dataset version you used.

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.