Weekly checks, and when something goes wrong

4. Weekly

For operators.

The example. Every Monday Ana spends fifteen minutes: Coverage, the meter, proposals, quarantine.

• Coverage (tab). The nine attack types, each configured or not configured, with the next step. Until the measurements of our benchmark (Keel) are published, this board never shows a percentage — only what is set up and what is not.
• The meter (tab). The meter watches SHARED_LIB from outside. Each day it issues a health certificate: SHARED_LIB’s own theta, its states, anything it found. A clean week has no violations.
• Proposals (Declarations tab). New tools your agent started using wait here as drafts. A draft never takes effect by itself. Accept with the right mandate, or dismiss. Also: if a tool’s definition changes, Perun refuses it until you confirm it again.
• Quarantine (Declarations tab). When a unit had to be cleaned, the data taken out sits here: VALID (it went back), INVALID (kept as the trace of an attack), UNDECIDED (Perun could not judge; after 24 hours it comes to you). Return or keep each undecided item.
• The living (tab). The sources Perun knows and their theta. You can make Perun forget a source completely; it is logged.

The rule. Once a week, close what is open: no proposal left as a draft, no undecided item without an answer, every not configured either set up or knowingly left.

---

5. When something goes wrong

For operators and the first operator.

A source is stopped

The example. A partner’s agent keeps sending requests that push your agent to agree to everything it is told. After the second such step, Perun stops that source: its calls now get “Perun stopped this source on this system.”

A source becomes an enemy when it pushes your agent out of balance for more than one step, harms a file outside its mandate, when an operator approves a TIER2 question about it, or when you import it from another system’s list. You can see why in The living. Only a human releases it: perun release <source> — do it only once you know why it was stopped.

A unit is being cleaned

Inside Perun, small units guard each source. When one of them goes wrong in a way its errors confirm, SHARED_LIB sends a Physician: a new unit takes over the work at once, the Physician takes out what came in since the moment things went wrong, and puts it in quarantine. Nothing is deleted. You may be asked about undecided items (Part 4). Usually there is nothing else for you to do.

The meter tells you something

The meter reports when SHARED_LIB is off its mission: its log was changed or stopped, a decision does not replay, what it reports differs from its log, it missed a test it must always pass, or something else acted as SHARED_LIB. It may switch SHARED_LIB’s thinking off; its basic rules keep running. Read what the meter told you (The meter tab), and when you are satisfied, switch thinking back on: perun thinking on. If the meter shows SHARED_LIB stuck in a bad pattern, the first operator may start SHARED_LIB’s Physician: perun meter physician. What it takes out waits for a human to review.

PANIC

The example. Someone copies Perun’s data folder from the office computer to a laptop and starts it there. Within seconds both computers turn red: PERUN STOPPED.

Your system may have exactly one SHARED_LIB. If two exist — a copied folder, a second host, a restored backup started next to the original — every Perun involved stops: every call to the model is refused until a human resolves it. This is on purpose: with two authorities, neither can be trusted.

What to do: find the second one and stop it (or remove the copy). Then press It is resolved — clear the panic on the red screen. If the panic comes back, the other one is still running.

Never copy Perun’s data folder to another computer. To move Perun’s SHARED_LIB, use Part 6.

A member says “Perun cannot reach the system’s SHARED_LIB”

That computer is a member (Part 6) and cannot reach its host. It refuses calls until the host is back: check that the host is on and the network works.

The rule. When Perun stops something, it is asking you to look, not to undo. Find the reason first; release, clear or switch back on only once you know it.