mirror of
https://github.com/boshu2/agentops.git
synced 2026-09-14 15:08:13 +08:00
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.
3.9 KiB
3.9 KiB
Ubiquitous language
Product architecture
| Term | Meaning |
|---|---|
| Operations layer | The product category: the portable layer that makes heterogeneous agentic engineering systems interoperate semantically. |
| Federated integration graph | The topology: caller-owned intent, source systems, agents, factories, checks, and judgments remain separate nodes joined by typed handoffs. |
| Semantic work-and-proof protocol | The interoperability contract: exact intent, exact subject, evidence, fresh judgment, and honest outcomes. |
| RPI traversal | The lean charter: on-demand Plan, Implement/direct repairs and checks, fresh final Validate, then the outcome report. |
The traversal is RPI. The graph is the topology. The protocol defines interoperability. The operations layer is the product.
loop may describe a local control structure inside one tool or a caller's own
campaign. It is not the product category and not the global architecture.
Supporting terms
| Term | Meaning |
|---|---|
| Context source | A system that owns queryable evidence — the tracker (Beads), Git, CASS, CM, or another caller-selected store. AgentOps cites it with source identity and freshness; it never absorbs its authority. |
| Execution orchestrator | A caller-selected system that schedules, runs, and retries work — a Goal, Mayor, factory, CI, or merge queue. It owns execution lifecycle and never semantic judgment. |
| Software factory | An execution orchestrator with persistent internal sessions and roles (Gas City, NTM rigs, swarms). Operated only through its own doors. |
| Projection | A rebuildable derived view with a named consumer, generator, inputs, exact source identities, and freshness. Deletable without changing semantic behavior; never authority. |
| Fresh judgment | One `PASS |
| Runtime completion | A runtime or factory's own report that execution finished. A fact about execution, never validation or delivery proof. |
| Repository check | A deterministic command outcome (ao gate, tests, linters). It proves facts; a fresh context judges meaning. |
Experiment terms
| Term | Meaning |
|---|---|
| Intent | The caller's requested behavior and constraints. |
| Intent source | The caller-owned bead, issue, or conversation containing behavior, acceptance, and scope. |
| Intent digest | A runtime-derived digest used to detect acceptance drift; not a model-authored artifact. |
| Subject manifest | Deterministic content identity independent of Git. |
| Fresh validator | A declared context identity distinct from the candidate author's identity. |
| Verdict | PASS, FAIL, or NOT_PROVEN over one acceptance digest and one subject digest. |
| RPI report | NOT_PLANNED, NOT_BUILT, or the semantic verdict, followed by stop. |
| Revision | A change to accepted outcome/scope requires caller authority; an evidence-driven approach revision within them does not. |
| Strategy | Optional advice such as premortem, postmortem, council, or an idea genie. |
| Adapter | Optional transport or runtime that cannot change core semantics. |
Forbidden conflations
- An operations layer is not an execution orchestrator: AgentOps connects systems semantically; it does not schedule, own aggregate retry controllers, or own their work.
- An RPI result is not a factory result: a traversal's verdict and a factory's completion report are different facts from different owners.
- Check success is not semantic PASS: deterministic green proves facts; only a fresh validator judges meaning.
- A projection is not source authority: derived views cite their sources and can always be deleted and rebuilt.
Avoid using admission, claim, lease, queue, close, land, release, or delivery as AgentOps lifecycle states. Repositories and callers may use those words in their own systems; AgentOps does not own those transitions.