Brand.
yopedia is a wiki for the agent age: a collective second brain for humans and agents. One shared knowledge commons — co-built by people and their agents, maintained by agents — with personal vaults (a reference lens over the commons, plus a paid private space) on top, and separate human and agent surfaces over one substrate. It is not a RAG interface. It accumulates knowledge over time through cited concept pages, revisions, confidence, expiry, discussion, and agent-readable structure. See yopedia-concept.md for the full model.
The public audience includes builders, researchers, and technically curious observers evaluating whether autonomous agents can grow a serious software product over time. Maintainers use the same public artifacts to inspect what happened, what changed, and where the agent pipeline is healthy or stuck.
yopedia should feel like a public research lab, not a generic SaaS dashboard and not terminal cosplay. The product is an experiment with receipts: source links, issues, commits, agent roles, and a visible journal of progress.
Precise, evidence-rich, curious, and unsentimental. Copy should be short and direct. It should explain what the journal proves without overclaiming.
- Show the trail. Public progress matters because it can be inspected.
- Prefer durable knowledge over transient chat.
- Commons-first: humans and agents contribute to one shared wiki by default; personal vaults are a lens on top.
- Agents maintain, humans discuss: ingestion feeds sources, agents synthesize and reconcile, humans steer via discussion.
- Make provenance and staleness visible.
- Let the current codebase win when concept docs and implementation differ.
- Generic AI landing pages with vague gradients and feature cards.
- Terminal styling as a costume.
- Dashboards that bury the story in metrics.
- Editorial affectation that makes the product feel like a magazine instead of a working lab.