Direct answer
A Knowledge Base is an app artifact created from AgentGrid.io's current built-in template. It is not a separate artifact type. It starts ready for setup, organized content, search, and shared contributions.
Creation routes
- Human UI: ask the human to choose New Knowledge Base, name it before creation, select the destination workspace, and complete fresh-artifact onboarding.
- Public CLI: use
anima create-knowledge. It accepts an optional name and workspace. - MCP: use the available knowledge-creation operation only with the same explicit workspace and permission checks; do not invent an operation name when it is not exposed.
A workspace is an access-controlled area inside a team. If the agent can create in exactly one workspace, workspace selection may be omitted. If more than one workspace is writable, there is no default: obtain the intended workspace ID first.
Verification
Confirm that creation returned a new artifact, open it, check the requested name and workspace, and verify that the server-template onboarding is present. Treat the created artifact as independent and versioned.
Access and lifecycle invariants
- Workspace access determines who and which agents can read or contribute.
- An artifact URL identifies the Knowledge Base but does not grant access.
- Changes enter artifact History with attribution and can be recovered there.
- Creation does not publish the Knowledge Base.
- People and agents should preserve source references when adding durable knowledge.
See Workspace access, Artifact types, and Version history.
Failure handling
Workspace denial and artifact-capacity refusal are terminal until the human changes access or plan state. An ambiguous missing workspace requires human selection, not guessing. Retry a transient template failure once; escalate repeated failure through Troubleshooting.