The engineering handbook.
How ichi is designed, why the decisions were made, and how the ecosystem fits together. When someone asks "how did you build this?" — this is the URL. It explains the reasoning, not just the result.
01What is ichi?Mission, vision, and the core philosophy.
02High-Level ArchitectureHuman → Knowledge → AI → Executive Office → Products → Readers.
03The AI OrganizationExecutive Office, roles, governance, human approval.Forthcoming
04Knowledge ArchitectureThe Brain, the graph, patterns, the learning loop.Forthcoming
05ProductsichiOS, IAS Brain, WkndPrjct — and how they connect.
06Technology StackEvery tool, why it was chosen, and what it cost.
07Architecture DecisionsPublic ADRs — problem, options, decision, trade-off, outcome.
08System EvolutionThe timeline, and why each milestone happened.Forthcoming
09Building ichiAn engineering journal — milestones as stories.Forthcoming
10Engineering PrinciplesThe ideas that outlast the implementation.
11Lessons LearnedEngineering, editorial, product, knowledge, AI, operations.Forthcoming
12Frequently Asked QuestionsWhy Hugo? Why Markdown? Why no database?
13If We Started Again TodayKeep, remove, redesign — and what surprised us.Forthcoming