wiki-synclisted

# Wiki Sync A session that is not logged did not happen, as far as the next session is concerned. This is the close-out routine: decide what is durable, write it where the next session will actually read it, and flag honestly what is still open. ## The knowledge base Any directory of markdown files works — an Obsidian vault, a `docs/` folder, a wiki. What matters is the shape: ``` log.md chronological, newest first. The entry point index.md table of contents and current status entities/ people, organisations, standing facts projects/<name>/ one directory per project concepts/ frameworks and reusable thinking ``` **One canonical location.** A second mirrored copy will drift, and then no session knows which one is true. If a mirror exists, delete it. ## Load first 1. `log.md` — your entry goes at the **top** 2. `index.md` — update if pages were created or a status changed 3. The specific pages this session touched ## Steps ### 1. Decide what is durable The knowledge base records: - What shipped - What was decided, **and why** - What is still open - Which files are canonical It does **not** record what other tools already know: code structure, git history, one-off chat. Duplicating those is how a knowledge base becomes noise nobody reads. ### 2. Update the pages first Edit the existing page rather than creating a near-duplicate beside it. Only create a new page for a genuinely new project or concept — and th