What problem does it solve? Teams and individuals struggle to keep knowledge both readable and queryable: wikis capture synthesized understanding but drift out of date, while databases store structured facts but lack narrative context. This Skill produces a concrete, buildable architecture that combines both layers with defined data flows, update loops, and failure-mode mitigations. ## Core Features & Use Cases - Two-Layer Architecture Design: Defines a wiki layer for compiled understanding and a database layer for structured recall, including schemas, page types, and linking rules. - Ingestion and Update Workflows: Specifies what happens when new sources arrive, when to regenerate syntheses versus append, and how to prevent drift. - Failure-Mode Mitigation: Explicitly addresses wiki drift, contradiction hiding, database gaps, re-derivation tax, and semantic conflicts from multiple editors. - Use Case: A research team needs a knowledge base where AI agents query structured entities while humans read synthesized topic pages. The Skill interviews the user about use cases, tools, and volume, then delivers a phased implementation plan with checklists and acceptance tests. ## Quick Start Use the hybrid-knowledge-architecture-blueprint skill to design a hybrid wiki and structured knowledge system for my team's research notes and project data.