Files
boshu2__agentops/docs/dependencies.md
T
Bo 7a765cde19 Align AgentOps around its operations-layer identity (#1051)
Executes docs/plans/2026-08-07-agentops-operations-layer-alignment.md:
AgentOps is the operations layer for agentic engineering; the federated
integration graph is the topology, the semantic work-and-proof protocol
is the contract, and RPI is the standard one-experiment traversal.

Retires the ao flywheel command family and all knowledge-flywheel
product state, tombstones the seven-move operating-loop workflow,
narrows ao init and the .agents state writers to declared destinations,
renames the core architecture page to rpi-traversal.md with a
compatibility redirect, aligns AGENTS.md, 25 skills, public and package
copy, regenerates every owned projection, and strengthens the
conformance gates with planted-negative proofs.

Both the alignment subject and the follow-up gate-bookkeeping commit
carry fresh author-distinct validation PASS verdicts with empty
not_checked scope.

Test-Removal-Reason: dead knowledge-flywheel and session-store surfaces were deleted with their tests (operations-layer alignment)
2026-08-07 18:37:03 -04:00

1.4 KiB

Dependencies

AgentOps's core protocol requires an agent runtime capable of reading and writing files. It does not require Git, the ao CLI, a tracker, a queue, a network connection, or a delivery system.

Tool or substrate Role Core requirement
Agent runtime Runs Plan, Implement, and a distinct fresh Validate context Required
Filesystem + SHA-256 helper Computes content identity and stores verdict.v2 Required
ao Repository utilities and ordinary deterministic ao gate check checks Optional
Git or a forge Version control, review, and delivery owned by the caller Optional
br, bv, or another tracker Caller-owned work organization Optional
NTM, Agent Mail, Gas City, Swarm, or another factory Caller-selected execution or coordination adapter Optional
Council or Dueling Idea Genies Additional independent judgment strategy Optional
Go Builds the optional ao CLI from source Optional

Optional tools may produce factual evidence or execute explicit packets. Their attempts, queues, leases, commits, or delivery state never become AgentOps correctness state. Missing optional tools can reduce what was checked, but they cannot reorder RPI or manufacture a PASS.

For CLI installation details, see the README. For the exact core boundary, see the RPI traversal.