Cross-project patterns

Without Klio

Teams solve the same problem in every repo. The ranking approach that worked in project A gets reinvented — worse — in project B, because the learning stayed behind.

With Klio in the loop

1. 1

   Durable, project-independent lessons are recorded at org scope; project-specific ones stay filed under their project.

2. 2

   An agent in a new project recalls org-wide memory alongside the project’s own.

3. 3

   The visibility ladder holds the line: private stays private, projects stay theirs, org is deliberate.

The call an agent makes

note(
  {
    "content": "For rank fusion across incomparable scores, use RRF — weighted blends drift as the corpus grows.",
    "scope": "org"
  }
)

Real tool, illustrative payload. The full contract for every tool is in the docs.

What changes

The second project starts smarter than the first. Scope rules decide what travels, not luck.