A live view of the suite’s rules as they fire
The Rigor Manager is an optional local app that draws the Authority System Suite's rules firing, from the project's own event log. It can add a few kinds of record through the project's write script, and it cannot edit or delete one.
The Rigor Manager is an optional app that shows the Authority System Suite's rules firing as an AI works, and it is built so that it cannot change them. The suite is a set of rulebooks that make an AI show its work. By the end of September it had a problem no rule could fix: you couldn't see it working.
The router's “loaded:” line, where the AI announces which rulebooks it loaded, is self-reported. The suite's own failure catalog says it “costs nothing to emit without reading anything”, and calls it the stated observability instrument that “observes nothing”. If the rules are going to be judged, someone has to be able to watch them.
On 1 October I decided two things: the suite would emit live events as it works, and an app would show them. I wanted the app switchable on and off, and something you can interact with while it runs, so that what the rules contribute is easier to see.
It draws the rules as they fire
The Rigor Manager is a local window, built on Python's standard library only, opening at 127.0.0.1:8765. The doctrine (the rulebooks themselves) needs nothing from it. The Live tab reads the event log as it grows and draws the doctrine as it fires: a route lights a system, such as TAS (the Topic Authority System, for evidence) or DAS (the Decision Authority System, for decisions), a load lights a module, and a write lands in the paper trail.
A turn whose trace (its log of steps) records no read of a system the session said it loaded gets a red mark, from one of the audit's checks. There are also tabs for sessions, records, the checks, settings, and “Your desk”: what is waiting for a person, such as records no second reader has confirmed.
It can add to the record but never edit it
I wanted it to be useful and unable to damage the record. It writes only through the project's record-writing script, signed as MAINTAINER, and only what Settings has switched on: confirm or dispute a session's record, add a resolution line in my words, append a directive. In the README's words, “It never edits or deletes a record, never writes as a session, never touches a doctrine file.”
Signing as the maintainer needs a key, and the README says where it must not live: outside every folder an AI session can reach, because “a session that could read the key could sign as you, and the audit cannot tell.” The switches in Settings, it says, guard against a mis-click, not against someone who already holds the window's token.
The first review found nine problems
The same evening a code review of the app found nine problems. Among them were DNS rebinding (a web page pointing its own name at your computer), a bad Content-Length (the header that gives a request's size), the key file, and which trace entry a load belongs to. Nine were fixed with tests, and three more from a second review.
The Live tab pictured here is the built-in demo, not a recorded session. It replays a sample turn shaped like a ship-cargo case, so the manager can be seen working without a real investigation behind it.
Sources and notes (5)
- Rigor Manager README — the notes this was written from
- README — the notes this was written from
- Umbrella overview — the notes this was written from
- Behavioural failure catalogue — the notes this was written from
- Directives — the notes this was written from
Authority System SuiteAll 17 parts →
