Skip to content

What happens every month

Nerthus.Core (until cutover). This page describes the frozen system that runs today and is deleted at cutover. Replaced by: not yet written.

Once a month the tool sweeps the repository and applies the routine work that has piled up. This page tells you what that sweep does to your sessions and what you need to do about it. Usually the answer is nothing.

The sweep runs on a schedule. Nobody has to start it. It does not publish its own work, though - it proposes it, and somebody merges it.

Only PU actually waits for the month

Most of what a session does happens the moment you close it: the block goes out to everyone it names, the coin moves, the intel reaches the players - see Record a session.

PU is the exception, and it is the reason the sweep exists. The monthly cap is computed over a whole month at once, so a single session's points cannot be worked out in isolation. The month's pending grants are applied as one batch and each character's SUMA moves once. Nobody is messaged: the monthly run has Discord switched off, so a player reads their new SUMA in the lore rather than in a channel - see Grant PU.

The other two jobs are repairs

Distribution repair. Session copies that have drifted out of sync are re-copied. This covers the copies delivered into entity files at closing. The read-only copies in the Lokacje/ folder repair themselves - the tool rebuilds that tree whenever the repository changes, so the monthly sweep never needs to touch it (see Record a session).

Transfer catch-up. A session whose coin never moved has it moved now. This is a safety net, not the normal path: closing a session already applies its transfers. A transfer reaches the sweep only when the session was distributed without being closed - see Transfer coin.

Repair is not distribution

The sweep re-copies drift; it never makes the first copy. Copies drift after a session has been distributed - a character joins the cast, a merge loses a copy, an entity's @plik changes and adds a target the set never had - and the sweep re-copies what is missing so they match again.

But it only ever touches a session that was distributed at least once. A session written but never closed was never distributed: it has no copies, nothing about it has drifted, and the sweep leaves it alone.

### 2026-07-01, Eraster rozmawia z Tussalem, Anward

Eraster spotkał się z Tussalem w jego willi w Thuzal. Wypili herbatę i zjedli obiad.

- Lokacje:
    - Thuzal/Rezydencja Tussal
- PU:
    - Eraster: 0.2
    - Lord Tussal: 0.2

Anward closed this session in July, so it went out to Eraster, to Lord Tussal, and to Rezydencja Tussal. If Lord Tussal's copy goes missing later, the August sweep puts it back. Had Anward never closed it, the August sweep would pass it by.

A session you never close is never picked up

No monthly sweep will distribute a session for you. If a Narrator writes a session and never closes it, waiting for the month to catch it means waiting forever - and its PU is never awarded either.

Nothing is counted twice

The sweep keeps no list of chores. It works out what is pending each time by reading the committed repository - which files already hold which session copies, which transfers and awards are already recorded. Work already applied is skipped before anything runs.

So a sweep over an already-settled repository does nothing at all. A re-run cannot pay a transfer twice, award a month's PU twice, or send a notification twice.

The sweep proposes; a person merges

The sweep never writes to the repository's main line. It puts its work on a branch of its own - settle/20260801-030512, named after the moment it ran - and opens a merge request titled Rozliczenie 2026-07 (nerthusd) with the whole report in the description.

Until somebody merges that request, the sweep's work has reached nobody: the SUMA figures everyone reads are still last month's, the repaired copies are still missing, and a caught-up transfer is still owed. Merging publishes all of it at once. Read the report, look over the changed files the way you would look over anybody's, and merge - the branch is deleted for you.

A month with nothing pending opens no request, and a month that stopped on a name opens none either. An open Rozliczenie request always means there is real work waiting for a reader.

When a month stops

If one name under a - PU: block cannot be matched to a character, the run stops before it writes anything at all, and the report names the name that broke it - see Grant PU for the fix.

The two repairs stop with it. The sweep works the whole month out before it touches a file, so a name it cannot match costs you the distribution repair and the transfer catch-up as well, and no merge request opens. Fix the name, and the next run does all three together.

What you have to do

  1. Close your sessions. Closing is the Narrator's act, and it is what distributes the session, moves its coin, and delivers its intel. The sweep repairs copies. It never makes the first one.
  2. Fix an unmatched name when the report names one. That is the only thing that stops a month, and it stays stopped until a person fixes it. The re-run is clean, because nothing was written the first time.
  3. Merge the Rozliczenie request. The sweep proposes; a reader merges. A request left sitting holds the whole month's work off the main line.

Everything else is the sweep's business.