Files
boshu2__agentops/docs/contracts/lesson-format.md
T
Bo 62cc3b6ee0 Clear the operations-layer alignment residuals (#1054)
Closes out the six residual items #1051 disclosed: terminology residue
on non-authority surfaces, the eval command-surface fixture that failed
when executed (#{3,4} -> #{3,5}), the vacuous retrieval-quality canary
and the nightly job that ran it, the consumer-free dream config block
and its exclusive helpers, the remaining knowledge-shaped writers moved
to the scratch tier, and the MEMORY.md consumer audit.

bin/ralph still resumes legacy .agents/ralph/ checkpoints so the
documented backwards-compat contract holds without a migration; both
paths and the outside-both refusal are now tested.

Fresh author-distinct validation returned PASS with empty not_checked,
after an earlier revision failed on a dangling nightly invoker and a
back-compat test regression that were fixed and independently
re-verified.

Test-Removal-Reason: the dream config subsystem was deleted with its tests (operations-layer residuals)
2026-08-08 14:34:14 -04:00

1.6 KiB

Optional Lesson Format

Learn may analyze collections of durable verdicts after an RPI traversal has finished. When a caller chooses to preserve a recurring pattern as a lesson, use one Markdown file under a caller-selected directory such as .agents/learnings/. Lessons are advisory evidence; they never change RPI sequencing, a candidate identity, or a verdict.

Required fields

---
id: <kebab-case>
date: YYYY-MM-DD
pattern: <specific recurring behavior or defect>
evidence:
  - <verdict digest or stable artifact pointer>
scope: <where the pattern applies>
falsified_by: <observable evidence that would invalidate it>
suggested_action: <reference, skill edit, deterministic check, or none>
---

The body explains the observed cases, why they appear related, uncertainty, and the smallest proposed response. Use at least two independent examples unless a single authoritative incident is explicitly sufficient.

Boundaries

  • A lesson records an inference; it is not a linter, policy, queue item, or release gate.
  • Promotion into a skill, reference, or deterministic check is a separate caller-authorized change with its own acceptance and validation.
  • Do not create tracker work, install hooks, mutate CI, or start another RPI invocation from the lesson writer.
  • Preserve source verdict digests so later readers can reproduce or refute the pattern.
  • Archive or delete lessons that are contradicted, unactionable, or no longer relevant.

Search and retention belong to the caller's filesystem or knowledge tools. AgentOps does not require a recall service, provenance ledger, or hosted store.