What the curator does
Think of it as a colleague who looks over your agents’ shoulders and takes notes:- “We run this workflow successfully again and again — let’s write a playbook.” → a skill proposal
- “We keep failing on the same kind of error — let’s write a rule against it.” → a rule proposal
- “This note is durably important — let’s keep it as knowledge.” → a knowledge proposal
What it learns from
The curator reads the log of the work, not your business data:
It sees that an agent summarized a report; it never re-reads the report’s contents. And everything is scope-filtered — the curator only ever sees its own company and department.
How a pattern becomes a skill
- The nightly sweep groups recent runs: failures by error type, successes by workflow.
- The rule of three: a pattern must occur at least three times before it is proposed. One-offs are ignored — the curator is deliberately conservative.
- Deduplication: memories are de-duplicated and marked as processed along the way — archived, never deleted.
- A proposal is written — pending, inactive, and invisible to agents until reviewed.
- You review it in Skills Review (Sidebar › Knowledge › Skills Review, admins): approve to turn it into a real skill or knowledge entry, or reject it. Only an approved proposal ever becomes active.
A proposal is not a skill. Until a human approves it, nothing the curator writes is usable by any agent. That is the governance core of the whole feature: the machine suggests, the human decides.
