Knowledge Publishing Architecture
A living knowledge base of design decisions, trade-offs, and architectural patterns for ListHub and WikiHub — two products that share DNA but optimize for different things.
What this is
A Karpathy-style LLM wiki: a markdown knowledge base that grows over time as we make decisions, discover patterns, and learn from implementation.
Index
Architecture
- beads-vs-wikihub-architecture — Steve Yegge's Beads (SQLite→JSONL) vs WikiHub (git→Postgres)
- two-bare-repos-per-wiki — Authoritative + public mirror architecture
- post-receive-vs-plumbing — No-loop sync invariant
Data Model
- acl-codeowners-pattern —
.wikihub/aclglob-based permissions - visibility-modes — The 8-mode vocabulary
ListHub Specific
- listhub-db-git-mirror-pattern — DB source-of-truth + one-way per-user bare git mirrors
Open Questions
- milkdown-editor — Rich editor choice
- deployment-domain — wikihub.globalbr.ai? Separate Lightsail?
- concurrent-edit-posture — Last-write-wins vs git-merge vs optimistic-lock
- events-jsonl-scope — v1 or v2?
Products covered
| Product | Stack | Live |
|---|---|---|
| ListHub | Flask + SQLite + Jinja | listhub.globalbr.ai |
| WikiHub | Flask + Postgres + Jinja + bare git | wikihub.globalbr.ai |