ai-safe2-framework

NEXUS Agent Entry Point

These instructions apply to automated consumers working inside NEXUS/. Read the repository-root AGENTS.md first; this file narrows it for NEXUS.

Deterministic discovery order

  1. Parse nexus-docs.manifest.json and preserve its version and status labels.
  2. Read DOCUMENTATION.md for the human navigation and ownership boundary.
  3. Read README.md for architecture and the current release boundary.
  4. Select the relevant plane: agent-to-agent, agent-to-tool, or agent-to-payment.
  5. For payments, read payments/THREAT-MODEL.md before controls or deployment claims.
  6. Resolve schemas from schemas/, policy from opa/, and observed behavior from tests.

Interpretation rules

Change workflow

For NEXUS changes, update code, tests, human documentation, the manifest, and navigation together. Run the affected test suite plus documentation-location, manifest, and link checks. Do not claim release, deployment, conformance, or risk acceptance without the authority and evidence required by root policy.