Facts and curation

Evaluations retain findings as facts. Repeated sightings add evidence to a lesson; curation decides whether it should guide future work.

For routine curation, start with Docs and skills. Docs group related facts into guidance you can review and approve as a skill. You do not need to promote the whole fact list one item at a time. Use Facts and Queue when a specific lesson needs investigation, correction, a different scope, or an individual delivery decision.

Old repository Facts and Curation links open the corresponding Knowledge view.

Review a fact

Choose a repository in the scope selector, open Knowledge → Facts, and use search and the State, Category, Audience, and Min weight filters to find a lesson.

Open the row before promoting it. The detail shows source sessions, related work items, sightings by repository, applicability, and the history of curation decisions. Source sessions remain subject to their own access rules.

Action	Effect
Promote into guidelines	Approve the lesson and choose how it reaches agents.
Dismiss	Set aside a lesson that should not become guidance.
Undo curation	Return a promoted or dismissed lesson to an undecided state.
Mute for me / Unmute	Control your own delivery of the lesson without changing the team’s curation decision.
Delete / Restore	Remove or restore an incorrect retained finding, when you have moderation permission.

Available actions depend on the item’s state and your permission at its scope. Human guidance is intended for people and cannot be promoted into agent instructions. Memories have Archive memory and Unarchive memory instead of fact-curation actions.

Curate the repository queue

Open Knowledge → Queue at repository scope. The Lane filter selects Pending, Promoted, Dismissed, or Regressions; the category filter narrows the type of lesson.

Each cluster shows its wording, category, weight, last sighting, and the number of phrasings behind it. Weight reflects accumulated evidence; decayed effective weight helps distinguish a current pattern from old history.

Choose Promote, edit the final wording, and select one or more destinations:

• Inject at SessionStart for automatic delivery to applicable new sessions.
• Write to CLAUDE.md / AGENTS.md for explicit write-back in the repository.
• Create an org memory, when offered to an administrator, for durable shared memory.

The optional Where this applies controls restrict vendors, session kinds, flow roles, and platforms. Keep the derived applicability unless you have a reason to change it.

Dismiss accepts a reason. Revoke undoes either promotion or dismissal. The Regressions lane highlights patterns that continued growing after promotion; inspect the new evidence before deciding whether to revise the guidance.

Set place and audience

A curated fact can move between repository, project, and organization scopes when you have the required authority. In its detail, stage a Move to… destination, adjust For (audience), and choose Save. Audience choices are Everyone, Only me, or A team when a team is available.

Place determines where the lesson applies. Audience controls delivery; evidence can continue accumulating from sightings outside that audience. Moving a fact to a wider scope can require approval. The Queue’s Approvals area collects scope promotions, twin nominations, and org-memory promotion requests for the people allowed to decide them.

Choose what new sessions receive

At repository scope, open Knowledge → Settings:

• Promoted-only (default) delivers curator-promoted guidance.
• Promoted + top-weighted uncurated also delivers high-weight uncurated facts.

Dismissed lessons are excluded. Promoted guidance from applicable organization and project scopes can also be delivered; audience, applicability, personal mutes, and per-session limits still apply.

To disable guideline injection for your own profile:

kcap config set disable_session_guidelines true

This is separate from the memory index. Prefer Docs and skills for reusable guidance. Injection is a bounded selection, so promoting more facts does not mean every one will appear at session start.