Verify & handover

Adding knowledge and having it reach answers are two different things. After you upload a document, connect a data source or write up a repair in the journal, it is worth a short check before you move on. And when you stop curating a project, the next person needs to know what you were keeping in your head.

Verify your knowledge is live

The simplest check is to ask Edmund a question you already know the answer to, then look at where the answer came from. You are not testing whether Edmund is clever; you are testing whether the source you just added is the one it draws on.

1. Pick a fact that lives only in the source you just added — a torque value from a manual you uploaded, a fault you logged in the journal, a reading that comes from a connected data source.

2. Open the project and ask Edmund a question whose answer is that fact.

3. Read the answer, then open the citation it gives. Confirm it points at your source — the right document and page, the right journal entry, the right data source.

4. If the answer is right but cites a different source, or has no citation, the knowledge is not yet reaching answers the way you expect.

Run the same check after any larger change — a batch of uploads, a new data source, a reworked suggestion set. One known question per source is enough.

Handover checklist

When you leave or rotate off a project, the knowledge stays but the context goes with you. Record these so the next curator can pick it up cold:

• Which projects you curate, and for each one, what kind of knowledge you keep current.
• The journal conventions you follow — how you name faults, what a complete entry looks like, anything you do consistently so entries stay searchable.
• The suggestion sets you maintain, and the thinking behind them.
• Who owns each data-source connection — the person to contact if a connection breaks or its credentials need to change.