Skip to content

Compiled Knowledge: a wiki your agents always have open

Your agents already have two ways to reach knowledge: the company knowledge base (documents, retrieved semantically per issue) and each agent's own context compression (a running summary of its work). Both are retrieval — the right passage is fetched when a question happens to match.

Compiled Knowledge takes the opposite bet. Instead of searching raw sources at question time, an LLM distils them ahead of time into small, typed, cross-linked wiki articles, and a compact index of those articles is injected into every heartbeat prompt. The agent always sees the shape of what's known — titles, one-line summaries, and how articles link — without spending a retrieval call. It complements the knowledge base; it doesn't replace it.

The four article types

Each compiled article is one of:

  • concept — a durable idea, term, or mechanism.
  • decision — a choice that was made, and why.
  • connection — how two things relate.
  • qa — a settled question-and-answer.

Articles cross-link with [[type/slug]] wikilinks, so the index reads as a small map rather than a flat list.

Three tiers

Compiled Knowledge is compiled per scope, at three tiers that mirror Trimus's tenancy:

Tier Source Injected for
company the company's company-wide knowledge docs every agent in the company
project a project's own (project-owned) knowledge docs agents working an issue in that project
agent the agent's latest context-compression summary that agent

An agent working a project issue sees all three; an agent with no issue project sees company + its own. Precedence for display is project > company > agent.

Turning it on

Compiled Knowledge is off by default. Set the feature flag on the worker and engine tier:

TRIMUS_COMPILED_KNOWLEDGE_ENABLED=true

The company must have an LLM provider configured (the compile is a single provider call per changed scope). A background worker recompiles on a ~30-minute cadence, but only for scopes whose source actually changed — an unchanged source is skipped by a content hash, so steady state is cheap. The flag is runtime-editable.

Promotion

Sometimes an article compiled at the agent or project tier deserves to be seen company-wide — a decision one agent reached that everyone should share. An instance admin can promote it from the compiled-knowledge management page (/companies/{id}/compiled-knowledge): the article is copied up to the company tier, stamped with a promoted_from provenance note, and thereafter injected for every agent. The original stays where it was.

Promoted articles are pinned: a later company recompile won't archive them, even though no company source produced them.

Notes

  • Opt-in. Nothing compiles and nothing is injected until the flag is on.
  • Incremental. Each tier/scope is hashed independently; only changed sources recompile.
  • A complement, not a replacement. Semantic retrieval from the knowledge base still runs when enabled — Compiled Knowledge adds an always-present index on top of it. See the mental model for how the pieces fit.