akb_put
Store a new document in the knowledge base. Provide title, content, and optional parent. Returns a canonical URI. Content is chunked and indexed for semantic search.
Instructions
Store a new document. The response carries the canonical uri — akb://{vault}/coll/{collection}/doc/{filename} when stored under a collection, or akb://{vault}/doc/{filename} at the vault root. Use that URI to address the document from every other tool. Automatically chunked and indexed for semantic search.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| parent | No | Parent location as a canonical URI — `akb://{vault}` for the vault root, `akb://{vault}/coll/{path}` for a collection. When given, the doc is placed there and `vault`/`collection` are derived from the URI. Use this in drill-down chains: paste the `uri` from an `akb_browse` response straight back in. | |
| vault | No | Target vault name. Required unless `parent` is given. | |
| collection | No | Collection (directory) path, e.g. 'api-specs' or 'meeting-notes'. Ignored when `parent` is given. | |
| title | Yes | Document title | |
| content | Yes | Document body in Markdown | |
| type | No | Document type | note |
| status | No | Lifecycle status. Defaults to 'draft'; pass 'active' to publish on create instead of promoting later with akb_update. Descriptive metadata only — it does not gate search, browse, or access. | draft |
| tags | No | Tags for classification | |
| domain | No | Domain: engineering, product, ops, legal, etc. | |
| summary | No | Brief summary (auto-generated if omitted) | |
| depends_on | No | akb:// URIs this depends on | |
| related_to | No | akb:// URIs of related resources | |
| file | No | Local file path to read as document body (alternative to content). Provide either file or content, not both. |