About Wiki
How this wiki is created, governed, maintained, and used by MCP-aware agents.
13 pages
- The Hussh Mega MapOne picture of the whole Hussh platform: seven layers (what it is) and ten end-to-end user-story flows (how it connects), with the consent model, encrypted personal memory, agents, and channels in a single view.
- Claude session wiki-touch protocolHow Claude.ai sessions should proactively read, write, capture, and maintain the Hussh wiki. The operating discipline that turns ad-hoc wiki work into a self-maintaining system.
- About WikiCanonical guide to how the Hussh Wiki is created, structured, governed, and used by humans and MCP-aware AI agents.
- Artifact capture — chat artifacts as first-class wiki entriesArchitecture for capturing Claude.ai conversation artifacts (code, HTML, SVG, mermaid, documents) as wiki pages with optional Google Drive backing. Routes private artifacts to the dedicated wiki Shared Drive and prepares public artifact migration once Drive public ACLs are verified.
- Hussh wiki — scalable app + MCP architectureThe live architecture that turns the Hussh wiki into a Drive-sourced, GCS/Firestore-served public/private reader and MCP server for agents.
- LLM Wiki Landscape — Three LevelsSVG landscape map of LLM Wiki implementation levels (May 2026): Level 1 RAG → Level 2 agent-writable closed → Level 3 open + MCP + agent-writable. Hussh sits at Level 3.
- LLM Wiki pattern — landscape & R&DHow people are spinning up LLM Wikis as of May 2026. Karpathy's origin gist, three implementation levels, known failure modes, tooling landscape, and how Hussh's wiki compares.
- Public vs Private — auth-tier on one Hussh wikiHow the Hussh wiki serves anonymous public readers and the authenticated owner from one MCP server and one reader, including HCT bearer auth, OAuth 2.1 + PKCE, tool/resource/prompt tiering, sanitization rules, and content guards.
- Wiki as App — Architecture — Editable SourceMermaid editable source for the wiki-as-app three-tier architecture. Same structure as the SVG, intended for revision.
- Wiki scaling — search architecture and growth pathHow Hussh wiki search and serving work across Drive source, GCS/Firestore indexes, MCP, and the reader; what breaks as the corpus grows; and how the architecture scales without redeploying for content CRUD.
- Wiki search — dual-audience UX + AX (R&D)Has anyone shipped a wiki search interface optimized for both humans (UX) and agents (AX)? Survey of the design space and the few existing examples.
- Wiki-as-app — Three-Tier ArchitectureSVG three-tier architecture for the Hussh wiki: clients (Capacitor + Next.js + agents) → API (HTTP reader + MCP) → store (git + Drive + qmd). Drive-visible canonical.
- Wiki-code alignment loopA drift-control pattern for keeping founder intent, wiki terminology, MCP behavior, repo docs, and tests synchronized.