Knowledge

The product surface labels this area Knowledge Bases. It is where builders create and maintain reference material that the Agent can search and retrieve while doing work.

Typical content includes policies, procedures, manuals, product documentation and internal guidance.

The Knowledge Bases surface

Builders can search the available Knowledge Bases, change the list presentation, create a new Knowledge Base and open an existing one for editing.

The list is project context: a Knowledge Base should have a clear purpose and a recognisable body of source material, rather than becoming a catch-all bucket for every document the project has seen.

When to use Knowledge

Use Knowledge Bases for maintained material that is primarily read as reference.

Use:

• Tables for structured maintained mappings and datasets;

• Skills for reusable operating instructions;

• Files for case material and general project artefacts;

• source systems for authoritative live records.

Make authority and provenance clear

Good Knowledge content makes it possible to understand where a retrieved statement came from and how current it is.

A plausible retrieved passage is still only as reliable as the source material behind it. If a policy or procedure changes, update the maintained source rather than relying on the Agent to infer that an older version is obsolete.