Examples and use cases

Every prominent YAML block on this site is imported from a checked file in the agentctl repository. Normal verification uses deterministic actions, the fake provider, or local protocol mocks. Live provider examples are opt-in and labeled.

Choose an example

• Repository audit: a bounded agent reads a fixture, then deterministic tasks verify and write the report.
• Release readiness: deterministic gates must pass before bounded analysis runs.
• Scheduled operational review: an external scheduler invokes one durable non-interactive run.
• CI quality gate: typed evidence becomes a stable exit code and JSON result.
• Approval-gated action: policy pauses a mutation for operator review.
• Selective workflow repair: reuse compatible upstream output and execute a corrected failed suffix.
• Offline recorded replay: a terminal result is reconstructed without executors.
• Provider portability: one neutral agent shape uses fake and OpenAI configurations with distinct evidence levels.
• Framework completeness: combine parallel tasks, bounded expansion, routing, loops, sub-workflows, compensation, protocols, and typed handoffs.
• Live framework verification: inspect sanitized GPT-5.6 recovery, replay, streaming, usage, and container evidence.

Verification levels

Label	Meaning
Deterministic	Runs locally without a model or remote protocol.
Mock-backed	Uses the real adapter or agent loop against deterministic local behavior.
Retained live evidence	A bounded live run was recorded previously and sanitized.
Static validation	YAML or platform syntax is checked, but the hosted system did not execute it.
Opt-in live	Requires an explicit credential and network call outside normal verification.

Run cargo xtask docs-verify in the canonical repository to validate documentation examples without provider credentials.