boshu2__agentops/docs/ARCHITECTURE.md

Architecture

AgentOps has a small semantic core and optional adapters around it.

intent
  -> PlanPacket
  -> CandidatePacket + subject-manifest.v1
  -> fresh Validate
  -> verdict.v2
  -> RPI report and stop

Core

• Plan shapes one active behavior, normal and edge examples, non-goals, required evidence, write scope, and the first acceptance check.
• Implement performs one bounded RED → GREEN → refactor experiment and reports the actual changed paths and evidence.
• Validate identifies the exact subject without Git, checks scope and acceptance, obtains one judgment from a distinct declared context, and stores a content-addressed verdict atomically.
• RPI invokes each core phase at most once and reports the result.

FAIL and NOT_PROVEN are terminal results for that invocation. A caller may start a new invocation and may provide a revision-packet.v1; RPI never creates or consumes one automatically.

Hexagonal boundary

The core depends on contracts, not substrates. NTM, Agent Mail, Codex Exec, managed agents, Git metadata, trackers, provenance, and councils are optional adapters or strategies. Missing or corrupt adapters cannot change a core outcome.

Generic provenance may record a verdict after it is written. Provenance availability is never required for verdict validity.

Repository boundary

ao gate check runs ordinary deterministic repository checks. A successful check says only that those checks passed. Repository policy owns commits, pushes, pull requests, CI, releases, rollback, and deployment.

See the component map, ports and adapters, and public contracts.