Knowledge Base CMS · Documentation
Architecture
Knowledge Base CMS's pipeline, its owned data, the events it emits/consumes, and what is out of scope.
← Knowledge Base CMSPipeline + owned data
Authoring, search, versioning, and chunking are deterministic; the one metered stage is auto-tag. The app owns knowledge_article in its demo_eco_c3_article table; a published article's body re-chunks into demo_eco_c3_kb_chunk (the concierge grounding unit). It reads the shared host #01 catalog for context. The data invariant holds: owner writes canonical (credential_id NULL); viewer writes credential-scoped, ephemeral, reset-clearing; the DO-UPDATE scope guard blocks a viewer write from clobbering canonical.
Metered AI + dual-mode, out of scope
The one metered stage (autoTagArticle, an AI-assist) runs dual-mode: Cloud claude-haiku-4-5, cost-capped at $0.05 per session and fail-closed — over the cap it falls back to recorded OSS (qwen2.5-7b-instruct) at $0, recorded on local hardware and never fabricated. Each run writes a cost_ledger row and a demo_cache replay key. Publish emits article.published to the durable event log. Out of scope and clearly labelled: auto-tag is a deterministic keyword-hint simulation in the prototype; content is synthetic; no production prompts appear. Honesty is inspector-only.