Run it every day

Your part is small

The agents do the writing. The librarian does the checking. Your job is to say yes or no, and to answer questions only you can answer. It takes about ten minutes a day.

The daily habit

Do this once a day, after the librarian runs.

1. Open the librarian's pull request. Read the summary at the top of the report.
2. Answer each new flag. One line is fine. Answer where the flag lives, such as the issue in your tracker.
3. Look at the page changes. If a fact looks wrong, say so in the pull request. Do not fix the page yourself.
4. Merge the pull request when it looks right.
5. Close the intake PRs that the librarian already brought in. The report lists them.
6. Once a week, ask the librarian for pages that are past their review date.

Five rules that keep it true

• No secrets, ever. No passwords, keys, customer data or call transcripts in the brain. Link to where they live instead.
• Only the owner decides. An agent can propose. The brain calls it a decision only with the owner's name, the date and the proof.
• Keep the history. Old updates and receipts are never edited. A fix is a new update that points to the old one.
• Say when it is stale. Every page has a last checked date. An old date is fine. Pretending it is fresh is not.
• Measure before you add. Do not add a search engine or a new tool until you can show the plain files are too slow.

When something goes wrong

• An agent edited a page directly. Close that change. Ask the agent to send the same fact as an update instead.
• Lint fails on an update. Fix the draft and submit it again. Never edit an update that is already in the inbox.
• The scheduled run did not happen. Check the scheduler first. Then run the librarian by hand once, so no updates are lost.
• Two updates disagree. The librarian flags both. You decide which is right, or ask for proof.

The prompt: weekly check

You are the librarian for my private company brain at <brain repo URL>. Do not edit pages in this pass.

1. Run `python -m librarian health` and `python -m librarian lint`.
2. List the pages that are past their review date. For each, give the page ID, its owner,
   and the source to check.
3. List the flags that are still open and past their follow-up date. Give the owner and the question.
4. List any agent or repo that sent no updates this week but changed code.

Keep it to one short list per section. End with the three things I should do first.

What you can do now

You have a private brain, one rules file, agents that read and report, a librarian that checks, a team that shares facts, and a habit that keeps it true.

Where to go next

• The Librarian template on GitHub, with every command and rule.
• The Librarian prompt page, with the full setup, handoff and schedule prompts.
• The Orchestrator Course, for the agent team in depth.