Autonomous agent graph integration

OpenGantry is the CLI contract + verify envelope for external autonomous agents (e.g. Hermes). Contract = mission YAML (scope + gate_command); verdict = gantry verify pass/fail with findings[] on failure. The executor agent implements code, builds skills, and retries — it does not parse raw terminal output.

All docs: index.md · Use cases: USE-CASES.md

Workflow

gantry init --discover [--domain code|content] — fast-path scanner emits .gitagent/discovery-proposal.json (no baseline writes until confirmed). Use --domain content for brand/compliance corpora (markdown, HTML).
gantry blueprint [--domain code|content] — interview produces ARCHITECTURE.md, TARGET_ARCHITECTURE.yaml, and .gitagent/verification_plan.json.
Executor reads required_skills in the verification plan and creates missing tooling before coding.
Executor legislates mission using gate_commands from the verification plan as gate_command.
gantry verify --mission … --json — on failure, ingest findings[] via gantry context-feed --json (compact re-entry) or the full --json payload:

{
  "status": "failed",
  "envelope_schema_version": 3,
  "findings": [
    {
      "failed_gate": "gate",
      "offending_file": "",
      "line": 0,
      "severity": "error",
      "resolution_hint": "run gate (npm test); append evidence to EXECUTOR_LOG.md",
      "fingerprint": "<sha256>",
      "semantic_fingerprint": "<sha256>"
    }
  ]
}

Retry edge — route each finding back to the Executor node as a repair hop until verify returns Exit 0, or GXT_FINDINGS_RECURRED aborts the loop when the semantic digest repeats in the ring buffer.

Surfaces

Surface	Format
`gantry context-feed --json`	Compact `RemediationSnapshot` with `findings[]`, semantic `findings_digest`, and `gate_log_path` (no stdout/stderr)
`gantry verify --json`	`VerifyFailedPayload` with `findings[]` (full debug payload)
`gantry verify --format sarif`	SARIF 2.1.0 with `properties.resolution_hint`
`gantry verify --format junit`	JUnit XML (`testsuites` / `gantry-verify`)
MCP `gxt_verify`	Same JSON payload as `--json`

With --format json, sarif, or junit, diagnostics go to stderr and the document is the only stdout payload. CI wiring: CI.md.

See ADR-0032 and ADR-0040.

Content domain example

Brand/compliance ad copy uses the same graph with --domain content and gantry perimeter check (regex rules in schema 0.3.0). Walkthrough fixture: examples/content-governance/. See DOMAINS.md.