LAN Brain docs

This is the methodology reference for your brain. Guides cover conventions, best practices, backup, and maintenance. The endgame stages cover how to automate, iterate, and maintain the brain over time.

Guides

• Conventions

  Naming, folder structure, wikilinks, frontmatter, and aliases. The short reference for how things are written inside your brain.

• Best practices

  The weekly and monthly rhythms that keep a brain growing. Atomic notes, entity disambiguation, archive versus delete.

• Backup routine

  How to back up a git-backed brain, verify the backup works, and recover from a lost copy. LAN-hosted brain considerations included.

• Health checks

  Weekly linter runs, monthly graph walks, quarterly skill audits. The signals that tell you a brain is healthy or quietly rotting.

• Learning paths

  Three paths: curious beginner, power user, team operator. Pick the one that fits today and switch when it stops being useful.

• What to avoid

  Heavy files, duplicate data, broken wikilinks, skipped backups, pasted secrets. The nine mistakes that hurt brains the most.

Endgame

• Automate

  Three layers to make the brain do work for you. Tools (one-shot prompts), skills (saved patterns), and triggers (things that run on a schedule). Start small.

• Iterate

  The brain grows because you play with it. Investigate, fix, integrate. Do not be afraid of breaking it. Watch a YouTube tutorial when you are stuck.

• Maintain

  Weekly rhythm. Monthly Obsidian walk. Backups. The maintenance loop is small and runs itself once you set it up.