Knowledge Bases

A knowledge base is a set of notes with folders and links between them. A scene can have one; a provider can ship one. The notes are ordinary Daslab notes — same editor, same tools — the knowledge base adds the structure.

Most teams already keep this kind of content somewhere: a GitHub repo full of markdown, a folder of Google Docs. Both work until an agent needs to read them, search them, or quote them mid-job. A knowledge base is that same pile of markdown, kept in the scene that uses it, covered by the same tools that do the work.

Notes with folders and links

There is no new document type. A note joins a knowledge base and gets a path — sops/packing.md — and folders are just the paths, the way Obsidian treats a vault. A link is a note's name in double brackets: [[Packing checklist]]. Links are read on save, and every note shows what links to it.

Every scene can have one

A knowledge base belongs to a scene. A world is the root scene, so a workspace-wide knowledge base is the root scene's — there is no separate mechanism. A link resolves inside its own knowledge base first, then walks up the parent scenes, the same way a scene finds its credentials. Linking into a sibling scene takes a qualified name: [[warehouse/Packing checklist]].

The agent reads it the way you do

Search covers every knowledge base a scene can see: its own, its parents', and the ones providers ship. An SOP in the knowledge base is something the agent can find, quote, and link to in its answer. Writes go through the same note tools as anywhere else, with the same history.

Providers ship their own

An integration's guides — setup, connectivity, troubleshooting — are a knowledge base too: read-only, written by the provider, available before you connect. "How do we connect our on-prem SAP system?" works in a fresh scene with nothing connected; the agent reads SAP's guide and answers with the services to activate and the technical user to create. Shipping one with your own integration is a markdown file and one declaration — see provider scenes.

Where this stands

Notes, the scene hierarchy, and provider guides exist today. Folders, links, and knowledge-base search are specified here and land next.

What's next

• Assets — notes are assets; a knowledge base is how they get structure.
• Scenes — the hierarchy links resolve through.
• Providers — the integrations that ship their own.

Updated 2026-07-20