Reconciliation
The periodic drift check — verifying that the documented system still matches the real one across seven dimensions.
Documentation drifts from reality unless something forces them back together. Reconciliation is that force: a periodic protocol that verifies every entry in the LisaOS map — the document that catalogues the whole system — against actual state, and reports the drift. It runs weekly as an automated job and can be invoked on demand.
The seven checks
| # | Check | Verifies |
|---|---|---|
| 1 | Governance documents | Every governance doc the map lists actually exists |
| 2 | Architecture documents | Every architecture doc exists |
| 3 | Frameworks | Every framework referenced is present |
| 4 | Agent prompts | The agent roster matches the installed agent definitions |
| 5 | Skills | The map's skill inventory matches the skills registry |
| 6 | Scheduled jobs | The documented jobs match the installed scheduler entries |
| 7 | Integrations | The declared integrations are actually reachable |
Each check compares a claim in the map against a fact on disk or on the wire. A passing check means the map told the truth about that dimension; a failing check is drift.
Method: measure, do not trust the map
The discipline that makes reconciliation trustworthy is that it re-derives each fact mechanically rather than believing the document under test. A row that the map calls "present and correct" is still checked against the installed reality — because the whole point is to catch the map being wrong. The same rigour applies to counts: a claimed tally is confirmed by counting, never assumed.
Drift response
Reconciliation reports; it does not silently rewrite. When it finds drift it surfaces the specifics — what the map claims, what reality shows — and the discrepancy is resolved deliberately: usually by correcting the map, sometimes by discovering that reality itself has a problem (a job that should be installed but is not, a skill that drifted out of the registry). Corrections flow through the ordinary dependency-propagation discipline, so fixing one entry pulls its downstream references along with it.
Why weekly
Weekly is frequent enough that drift is caught while its cause is still fresh, and rare enough that it does not become noise. Between runs, the reconciliation any structural change triggers manually — every rename, move, or new governance document propagates its own downstream edits at the time — so the weekly run is a backstop, not the only line of defence.