> ## Documentation Index > Fetch the complete documentation index at: https://agents.concierca.ch/llms.txt > Use this file to discover all available pages before exploring further. # Strategy > Company strategy documents — the knowledge base filtered to category=strategy. ## What it is Company strategy documents — a filtered view over the knowledge base with the fixed filter `category = strategy` enforced on every read. Same fields as the general `knowledge` view; the filter cannot be bypassed. The [SOP](/for-agents/data-model/sop) view is the same pattern for standard operating procedures. Entries carry a title, markdown `content`, a condensed `intro`, importance, tags, visibility scope, and version/usage metadata. Record-level scope rules apply: members see company-wide entries plus what is scoped to them; a private (`scope = user`) entry belongs to its `user_id` owner. ## How it gets data No ingest endpoint — strategy entries are written in the app (Company Hub → Strategy), by agents via `knowledge_save`, or promoted from memories. Versioned: every save creates a new version with a field-level diff and restore in the History tab. ## Fields ### Content & classification | Field | Label | Type | Writable | Description | | ----------------- | ---------- | ------ | --------------- | --------------------------------------------------------------------------------- | | `title` | Title | text | knowledge tools | Document title | | `intro` | Summary | text | knowledge tools | Condensed summary — what search results and context injection show first | | `content` | content | text | knowledge tools | Full markdown body | | `category_id` | Category | text | ✓ | Category reference — fixed to strategy for this view | | `category` | — | text | API only | Legacy free-text category; `category_id` is the authoritative reference | | `department_id` | Department | text | ✓ | Owning department reference | | `department` | — | text | API only | Legacy free-text department name; `department_id` is the reference | | `scope` | Scope | text | knowledge tools | Visibility scope: company, department, or user (private) | | `importance` | Importance | number | knowledge tools | Importance ranking — high-importance entries are auto-injected into agent context | | `tags` | Tags | json | knowledge tools | Free-form tags for filtering | | `retrieval_class` | — | text | API only | How retrieval treats the entry (e.g. always-load rule vs. searchable reference) | ### Usage & versioning | Field | Label | Type | Writable | Description | | ----------------- | ---------------- | -------- | --------- | ------------------------------------------------------------------------ | | `version` | version | number | read-only | Version counter; every save creates a new version with a diff | | `used_count` | used\_count | number | read-only | How often agents used the entry | | `used_by` | used\_by | text | read-only | Which agents used it | | `success_count` | success\_count | number | read-only | Times usage was marked successful | | `failure_count` | — | number | API only | Times usage was marked unsuccessful — the counterpart of `success_count` | | `last_used_at` | last\_used\_at | datetime | read-only | Last usage | | `intro_embedding` | intro\_embedding | text | read-only | Vector embedding of the summary (powers semantic search; internal) | ### Provenance & lifecycle | Field | Label | Type | Writable | Description | | ------------------------------------------ | ----------------- | -------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | `created_by` | created\_by | text | read-only | Creator (agent name or user) | | `created_by_user` | created\_by\_user | text | read-only | Creating user id, when human — provenance only | | `user_id` | — | uuid | API only | Owner of a `scope = user` (private) entry — authorization. NULL on shared rows; distinct from `created_by_user`, which is provenance only | | `provider_id` | — | uuid | API only | Agency/provider owner for provider-level (Mandat) entries | | `source` | — | text | API only | Free-text origin of the entry | | `source_type` / `source_id` / `source_uri` | — | text | API only | Structured provenance: what kind of source, its id, and a link to it | | `template_slug` | — | text | API only | Knowledge template the entry was created from, if any | | `template_payload` | — | json | API only | Structured field values captured by that template | | `digest_key` | Digest Key | text | create-only | Dedupe key for digest-generated entries — the same digest never creates twins | | `valid_at` | — | datetime | API only | When the documented fact became valid | | `invalid_at` | — | datetime | API only | When it stopped being valid — superseded facts keep their history | | `supersedes` | — | uuid | API only | Id of the entry this one replaces | | `consolidated_at` | — | datetime | API only | When a consolidation pass last reviewed/merged the entry | | `archived_at` | Archived | datetime | create-only | Soft-archive timestamp; archived rows are hidden unless `include_archived:true` | | `updated_at` | updated\_at | datetime | read-only | Last change | | `created_at` | Created | datetime | read-only | Row creation time | ✓ = editable via generic row writes. "knowledge tools" = managed through `knowledge_save` / `knowledge_update`, not generic row writes. "API only" = real database column not registered as a visible app column — returned by MCP queries. The table also carries the system columns `id`, `tenant_id`, and `workspace_id` — set automatically for tenant isolation. ## Query it ```json theme={null} { "method": "tools/call", "params": { "name": "data_query", "arguments": { "view_slug": "knowledge_strategy", "search": "positioning", "select_fields": ["title", "intro", "importance", "updated_at"], "limit": 10 } } } ```