Maintain is the pillar that decides whether the brain is still useful in two years. A brain nobody maintains drifts: pages go stale, links break, sources quietly stop feeding it. The good news is that the upkeep is not a project and most of it is not yours to do by hand. The AI edits, creates, and maintains through the skills catalog; you review and decide, and you keep an eye on the inputs. The weekly move is oversight: run weekly-review to see what changed, and if you own or admin the brain, change-review to sign off on recent edits or revert what should not have landed. The monthly move is freshness and structure: run source-sweep so the AI re-walks your connected folders and updates the pages whose sources changed, and ask it for a health check to catch broken links, duplicate entities, and orphan pages. The one thing only you can do is watch the input side. Your brain lives on LAN servers and is snapshotted daily, so backups are not your job, but a connector that quietly expired is. Once a month, open Settings and confirm every connected source is still green, and reconnect anything that dropped. A brain that stopped ingesting looks exactly like a brain nobody wrote to, which is why this single check is worth more than any file you could have saved.
Steps
Weekly: review what changed
Ask the AI to run weekly-review. It reads the brain real change history and hands you a short, grouped summary of what was added, edited, or removed, and by whom. Owners and admins can run change-review to sign off on recent edits or revert them.
Monthly: refresh from your sources
Run source-sweep on a department. The AI re-walks the connected folders, finds what changed, and updates the pages that cite those sources, with a reason for each change. You review the diffs in the page History. It never copies documents in; the brain stays an index over the mother files.
Monthly: run a health check
Ask the AI to check the brain for broken wikilinks, duplicate entities, and orphan pages, and to fix the ones it is sure about. Open the graph view in your dashboard while you are at it, to take in the overall shape and spot corners that have gone quiet.
Monthly: check your integrations are still connected
Your brain lives on LAN servers and is snapshotted daily, so there is no backup for you to run. What needs you is the input side. Connectors expire: a password change, a revoked OAuth grant, or an admin tightening permissions stops the flow silently. Open Settings, confirm every connected source is still green, and reconnect anything that dropped. This one check catches the most damage for the least effort.
Let access scope the work for you
Every skill runs in the session of whoever invokes it, bounded by their access. An owner sweep or review covers the whole brain; a member run covers their departments. You do not set this up per role, it follows whoever runs the skill, which is why the same routines are safe for the whole team.
Resources
Troubleshooting
- I skipped a few weeks and the brain feels behind.
- Run source-sweep to refresh the pages whose sources changed, then a health check to clean up links and duplicates. The brain forgives a missed week, and even months of neglect is a real but doable cleanup.
- A source has not updated the brain in a while.
- Start with the recent activity, or ask the AI what changed. A stretch of empty days almost always means a connector dropped, not a quiet month. Check Settings and reconnect.
- I have an old skill I am not sure I still need.
- Ask the AI to list skills with their status and deactivate the ones you no longer use. Nothing is lost: a skill is a page and keeps its History, so you can restore it.
- I want someone to sign off on edits before I trust them.
- Run change-review. It groups recent changes by contributor so an owner or admin can approve them or revert what should not have landed. It is review-after: changes go live immediately so no one is blocked, and you react.