Skip to content

Use the web dashboard

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

The dashboard is a website that reads the campaign back to you: who spoke in which session, how the world connects, which forms the tool does not yet recognise. Nearly every screen is a view of what is already committed, so you can open it, click through it, and close it without touching the lore. A few screens do write, and each shows you the change before anything is saved: the Edytor publishes a lore edit, the Minimapa saves a map placement, and Rozstrzyganie records a ruling. Nothing on this site writes without showing you what it is about to write.

Open it at dev-astral.nerthus.pl.

astral.nerthus.pl opens and then shows you nothing

That address is the one production will use. The page loads, and the campaign it is built to read does not answer yet, so every screen stays empty and nothing on screen says why. Use dev-astral.nerthus.pl until somebody tells you otherwise. Whoever stands production up deletes this box in the same change - a warning with nobody named to remove it becomes permanent.

Sign in

You need a klucz API — the value on your @klucz_api line. A Radny grants one; API keys is the article that covers asking for it and what to do when it stops working.

  1. Open Ustawienia.
  2. Paste the key into the token field.
  3. Leave the address field alone. The site already knows which campaign it belongs to.

The key stays in your browser. Nobody else sees the screen you are looking at, and closing the tab does not revoke anything.

If you arrived from the addon inside Margonem, you are already signed in — the addon hands the site a session that lasts about four hours. When it runs out the site asks again. That is not a fault.

The screens

The site opens on Start: what changed since you last looked, and what the corpus holds. Every other screen draws a pill along the top, and the site draws only the pills your key can open, grouped by whose work they are - Lore, Moderacja, Rada, IT. A pill you do not see is a screen your role does not use. That is the intended state, not a fault.

The Lore group is the narrator's set:

Tab What it shows you
Transkrypty who spoke, in which session, and what they said
Higiena forms the index does not know: aliasy, tytuły, narratorzy, mapy, roszczenia
Repo the lore files themselves - prose and session blocks, where they are written
Edytor lore edits staged in the browser - you see every change as a diff, and publishing writes it as a commit
Sesje every session of the campaign, by date, title, Narrator and place
Minimapa the rendered maps on one tile grid - where each piece of the world lies

Name-shaped words the lore does not know — "Kapłan", "Elfka", "Zakon" — wear a dotted underline in the transcript lines of Transkrypty and Sesje, in the muted tone, with the head word's lemma and kind in the hover title. They are the language pipeline's mention candidates (format 10, 123-ner-plan): not links, since nothing answers to them yet, and not warnings, since a candidate is a guess and not a finding against the lore. A name the lore does answer to keeps its coloured link on the same letters. The marks come from a small read beside the transcript, so an evening opens as fast as before and a daemon without the annotation layer simply shows none.

On a session page the candidates also sit under the head as chips — most frequent first, a click jumps to the first line that carries the word — and the head strip counts them ("4 wzmianki"). A legend over the lines says what the dotted rule means and carries the switch «podkreśl kandydatów», remembered per browser. Forms of address («Pan», «Pani», «Sir»…) are never marked or counted: on one measured evening they were the two biggest chips and neither is somebody. Once the Kto to? panel (below) has read the evening, a mark whose form the engine bound takes the confidence colour and names the block in its tooltip («Elfka → Riveth (silnik)»); one a person ruled is underlined solid.

Editing is a mode of reading: you open a file on the Repo screen, switch it to editing, and the change waits in the Edytor until you publish it. Placing a map on the Minimapa saves the same way - the placement becomes a diff you can read before it is committed, never a silent write.

Three more Lore screens stand beside Higiena: Próbki, Rozstrzyganie and Model. The tools write down what they worked out about the corpus - that a nick belongs to a character, that a post records somebody taking an office, that a line was speech rather than narration - and every one of those is a guess until a person says otherwise. Rozstrzyganie is where you say. The sample and model screens is the article for those three and for the three further screens they lead to: what a ruling costs, what it buys, and why rejecting is worth as much as accepting. Nicki is not one of them - it is one of the six surfaces inside Higiena, listed below.

The world is drawn on the Minimapa screen. An old Świat link still opens: #/swiat lands on the same grid.

Outside the groups stand Szukaj - a phrase across the whole corpus: prose, sessions and speech - and Ustawienia, your key and which campaign the site is reading.

Three more screens belong to the Rada group:

Tab What it shows you
Dyżur what is owed, to whom, and what clears it - The Dyżur screen
Władze who held which office and when - the register as it stood on any day you name - The Władze screen
Regulamin the regulation corpus, version by version - a link you paste carries the version you were reading, so the person who opens it sees the same wording - The Regulamin screen

Two more stand in the Moderacja group, for the people who do chat moderation:

Tab What it shows you
Moderacja who can open the sealed moderation records, and what is missing - The Moderacja screen
Kary the register of sanctions - dates, sizes and signatures; the content itself stays encrypted - The Kary screen

Flota and Sejf, in the IT group, are for whoever runs the machines. Nothing on them is about lore, and nothing on them needs you.

Dyżur is role-gated and you may not have it. Each of its five panes is drawn for the people whose work it is, so a Gracz sees the tab with one pane, a Narrator with three, and a Radny with all five. A reader whose role uses none of them sees no tab at all, which is the intended state and not a fault.

The address bar carries the whole screen, so any view you are looking at is something you can paste into Discord and somebody else will open exactly what you saw.

https://dev-astral.nerthus.pl/#/Eraster
https://dev-astral.nerthus.pl/#/Eraster/l/Thuzal
https://dev-astral.nerthus.pl/#/Lord Tussal/q/korony
https://dev-astral.nerthus.pl/#/sesja/2024-03-17 Rozmowa w Thuzalu

The first shows everything the tool knows about Eraster. The second narrows it to Thuzal. The third keeps only the lines mentioning korony. The fourth opens one session by its nagłówek.

Two names at once work the same way, separated by a comma:

https://dev-astral.nerthus.pl/#/Eraster,Lord Tussal

That is how you check whether two characters were ever in the same scene.

Read the Higiena list

Higiena is the one tab that asks you for something. It lists forms the campaign has written that the index does not record, on six surfaces:

Surface What the row is telling you
Aliasy a name a transcript uses that no @alias covers
Nicki somebody speaks under a nick the index does not know
Narratorzy one Narrator signing under two spellings
Mapy one map render serving blocks that disagree about the place
Wzmianki a name the campaign talks about that has no entry at all
Roszczenia a claim naming a form no session ever wrote

The strip above the list says how much of the archive the page was computed over. It matters: "nothing to fix" over two thirds of the sessions is a different statement from the same words over all of them, and a session whose description no longer matches its text counts as unread.

A row marked in crimson is sporne — another spelling of the same name points at a different person, and at most one of them is right. The row names both, so you can see the disagreement without opening anything.

Click the arrow at the start of a row to see why it is there: the reason in full, and up to three real sentences from the archive with the name marked. That is usually what settles it. Karka looks like a person until you read the line it came from and find it is half the name of a town.

Use ↓ to put a row aside and ✓ to mark one you have already fixed. Both are remembered in this browser and sent nowhere. The list opens on Nowe, so the second visit is shorter than the first.

A row is a suggestion, and one kind of row becomes a change on its own. Nothing on this tab writes anything when you click it. An Aliasy row at exact with no rival is written by the daemon itself within half an hour, as an @alias line marked (auto) — you will see it in the next commit, and deleting the marker adopts it, deleting the line refuses it (ruling H124.1). Every other row you act on by hand, in the file it names, the ordinary way — Add and edit entities for an @alias, Record a session for a title, Locations and maps for a map — or with one key on the session page's Kto to? panel.

Adopting a form works backwards. Once an @alias is in place, a transcript from years ago starts resolving that name too, so one line can change what an old session shows you today.

The Aliasy and Wzmianki rows arrive a few seconds after the rest. The other four surfaces are quick; those two read every archived transcript.

Kto to? — fix an evening while you still remember it

Every session page ends its right column with Kto to?: every form the evening's transcripts write that the lore does not name, in three groups. Do rozstrzygnięcia is the work — forms the engine could not place, with the whole cast as numbered chips and, where somebody answered a line naming the form, how often. Rozpoznane are the engine's own answers, each marked with how it knew: silnik (one cast member answered lines naming the form and nobody else did), obsada 1 (a cast of one), z sesji 08-01 (a person ruled the same form in another session with the same character present), sito (an alias sieve at high confidence). Rozstrzygnięte are the rulings already made. Forms the lore already names are counted in the foot («12 form zna lore») and never listed; the same panel sits in the board's session panel (read on press, never on scroll) and in the closing drawer, where it replaced Pytania.

The keys are the whole overhead. With a row focused: t keeps the engine's answer, 1–9 names a rival instead, n says the form is not a name, r shows the other lines it sits on; a accepts every recognised row at once. One key writes one ruling and greys the row; nothing is asked twice. A ruling on a question the store proposed answers that question (with the referent); a ruling on a form nobody asked about deposits one confirmed span per occurrence, scoped to this session, under your name; n on such a form deposits the same rows denied, so the form stays gone from this session and the model learns a negative (ruling H124.3); a sito row at exact writes the @alias line through the same route the Higiena tab uses, and a weaker alias row still shows the line to paste. Without sample.confirm the rows read as text; on a host without the sample store the keys say so and write nothing. On the transcript, a form you ruled becomes a link to its block; the engine's own answers stay a coloured mark with the block in the tooltip (ruling H124.4).

The engine's answers are served, never stored: a recognised form stays recognised on every read until a person presses a key, and a confirmed row always means a person was shown it. The corpus-wide Higiena tab stays for the archivist; the person who ran the evening is the one who knows who Frycek was, and this panel is where they say so.

When something looks wrong

The dashboard shows the campaign as it was last committed, not as your working copy has it. A session you recorded a minute ago appears once the change is in and the tool has caught up.

If a name resolves to the wrong character, that is a fact about the lore rather than about the site: the fix is an @alias, and Add and edit entities covers it.

If every screen is empty and Ustawienia shows your key, the key has probably been revoked. Ask a Radny — API keys has the rest.