Knowledge

Knowledge brings together lessons retained from evaluations, deliberately saved memories, and guidance documents assembled from related facts. Choose All Repositories, a project, or a repository in the scope selector, then open Knowledge.

For ongoing curation, start with Docs and prefer approving agent guidance as skills. A busy repository can accumulate more individual facts than anyone should need to curate one by one. Reviewing grouped guidance lets you decide what agents should learn at the topic level, then inspect individual facts when you need evidence or a correction.

View	Use it to
Docs	Review grouped guidance and its member facts, then approve it as a skill or short injected document.
Facts	Find a specific lesson or saved memory, inspect its evidence, and correct where it applies.
Queue	Handle individual recurring patterns and pending promotions. The cluster queue is repository-specific.
Settings	At repository scope, choose which individual facts are eligible for session-start injection.

Review guidance documents

Open Docs at repository scope. Agent documents turn related lessons into reusable instructions; human digests collect advice for people. Use Agent or Human when that selector is shown.

Open a document to compare its Pending draft with the currently Serving version and read its Members. Edit the guidance, select Skill, and Approve it. You do not need to promote each member fact separately.

Docs and skills walks through reviewing the evidence, approving the document, installing skills, and maintaining approved versions.

Deliver approved guidance

Skills make detailed guidance available on demand. Session-start injection is capped by document size, item counts, and a total character budget, so keep it for short instructions that should be present immediately. Injection limits explains the defaults and what happens when guidance does not fit.

Repository Knowledge → Settings controls individual fact injection. Promoted-only (default) delivers curator-approved facts. Promoted + top-weighted uncurated also admits the repository’s strongest uncurated facts. Scope, audience, applicability, and delivery limits still apply.

Use skill sync to install approved skills. For short guidelines that should live in version control, use Curation write-back.

Save repository, project, and organization memory

Memory captures knowledge you deliberately want to retain: a repository convention, a decision spanning a project’s repositories, or an organization-wide practice. Ask your agent to remember it and specify both where it applies and who should see it.

A team is one possible audience, alongside yourself, project members, and the organization. It is separate from the memory’s repository, project, or organization home. Shared memory explains these choices with example requests.

Find a specific lesson

In Facts, choose Facts + Memories, Facts, or Memories. Search the text, then refine by State, Category, Audience, or Min weight. The state filter includes promoted, uncurated, dismissed, deleted, and archived items; repository scope also exposes suppressed duplicates.

Open a fact to inspect its source sessions, related work items, sightings by repository, and curation history. Applies in identifies where the lesson belongs; For (audience) identifies the people who receive it. A lesson can apply across a project while being delivered to one team.

Use Facts and curation when an individual finding needs attention. For routine review of accumulated lessons, return to Docs.