# Living knowledge base

Bring a project in and SecondOS writes a family of eleven readable docs from its structure + your team's memories, then keeps them current on every push (rewriting only the sections whose map/memory changed).

overview · architecture · modules (per-module: purpose, exports, dependencies, routes, tables; big modules split into sub-modules) · dependencies (the module dependency map from the graph) · API (routes by area) · data model (DB tables/columns/enums) · knowledge (decisions/conventions/gotchas) · learnings · onboarding · changes (from git) · glossary.

Auto-created on the first sync, incrementally refreshed after — you maintain nothing. Written from the structural map, never your source (K-S23). The dependency map, API reference and data model are docs no other tool can auto-write, because SecondOS has the call/import graph, routes and DB schema. A Pro feature (generation runs server-side).