Bo
e1fae0dae6
RPI now owns the authorized outcome through finish, with Plan and Memory
loaded only when useful. Known defects get direct repair, and evidence
can change the approach under unchanged acceptance. Fresh exact-content
validation remains required. Memory provides optional recall, mining and
curation of reviewed topic pages; specialists and the fixed-dispatch
adapter remain optional.
The change reconciles current documentation and generated skill
projections. It preserves native budget and permission authority, BD
work ownership, protected external evidence storage and the distinction
between a supported lesson and demonstrated later benefit. It adds no
scheduler, work store, Go command or evidence schema.
Validation: required local Go/build/vet/race checks, aggregate suite,
generated-output check and 72 gates pass. The complete 44-test executor
suite passes; its shared-deadline fixture now tolerates CI scheduling
jitter while still requiring deadline exhaustion and preventing a third
launch. Fresh author-distinct review passed all 112 changed paths with
no findings; all seven exact-head CI checks passed at bfce33cce. Native
restricted-source enforcement and reduced token use are not established
by this change.
2.5 KiB
Architecture
AgentOps has a small semantic core and optional adapters around it.
existing bead or caller intent
-> on-demand planning and bounded implementation
-> runtime-derived subject-manifest.v1 + check receipts
-> fresh Validate
-> PASS | FAIL | NOT_PROVEN
-> direct repair and fresh revalidation within real bounds when needed
-> completed acceptance or truthful unfinished result
Core
- Plan shapes missing intent and revises disproved approaches under unchanged acceptance and scope; clear work need not invoke it.
- Implement performs bounded implementation and direct known-defect repair and returns runtime-derived subject identity, actual changed paths, and factual check receipts.
- Validate identifies the exact subject without Git, checks scope and acceptance, and obtains one judgment from a distinct declared context. It stores a content-addressed verdict atomically only when requested by the caller or a declared downstream consumer.
- RPI owns the authorized outcome through checks, direct repair and fresh final judgment; specialists and planning are on demand (ADR-0017).
- Memory optionally recalls reviewed topic pages or separately mines and curates supported claims. It cannot change completed product verdicts.
Known findings are repaired within authority and real remaining bounds. A genuine causal stall admits at most one bounded fresh helper; an unhelpful answer, cancellation, refusal or a spent real bound ends the attempt. Explicit repair-round bounds still apply, and no invocation renews an allowance. The fixed-dispatch adapter keeps its narrower optional contract; it does not govern native RPI execution.
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 one is persisted. Provenance and artifact storage are never required for a fresh validation result to be valid.
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.