AgentDirective

05 / Improve · Optional follow-up

Check the evidence your agent reported.

Compare your directive with your agent’s status files to find missing evidence, inconsistent claims, and open decisions. This checks reported metadata—not your source code, deployed site, or runtime behavior.

Need to inspect a project first? Create an inspection prompt.

Your journey

Step 5 of 5 · Improve
  1. 1
    Describe
  2. 2
    Confirm
  3. 3
    Decide
  4. 4
    Download
  5. 5
    Improve

This is an optional follow-up, not a required restart. Review the sanitized status your agent returned, then use the report to guide the next review.

What does a “supported” result actually mean?
An example of the review boundary—not a result for your project.
  1. 1 / Your agent’s claim

    “Approval checks are implemented.”

    The status file names the requirement and lists code paths, test results, and other evidence pointers.

  2. 2 / Metadata review

    Are the expected records present?

    AgentDirective compares the supplied records with the directive. Missing evidence or a reported failed test is flagged.

  3. 3 / Separate verification

    Does the approval check really work?

    A person or testing tool must inspect the code and run meaningful tests. A “supported” metadata result does not answer this question.

1 / Choose files

Choose the project records

These small metadata files describe the project and its reported progress; they are not source code. Files stay in this page until you consent.

Required: .agentdirective/agent-directive.json (the build rules) and .agentdirective/control-status.json (the progress record). Optional: change history, bundle list, test summary, and evidence list.

No files selected yet.

Choose both required files to continue. You can remove a file and choose its replacement.