Documentation · Releases · Nemesis

Nemesis — H.1.5

v.Chronos.1.Nemesis — legacy v.H.1.5

Red no longer just looks red — a red node stops earning. The gate is forward-only, the same single-source red verdict drives every surface, and the operators get the controls and visibility to see and fix a red node.

Nemesis closes the economic hole where a node with a stale, version-mismatched, or failed-sub-component benchmark still accrued stoicism every tick and still showed a non-zero Earn Score. Before this release red was purely cosmetic. Nemesis makes red mean what operators always thought it meant: while a node is red, stoicism accrual for that node produces exactly zero — both the per-tick scoring path and the lower-level tip-accrual path refuse to add stoicism, and a Tunnelee that is red zeroes the whole accrual including the Tunneler's fee slice. The gate is strictly forward-only: when a node turns red, future accrual stops, but stoicism already accrued (pending or current) and already redeemed is never reduced, reversed, recomputed, or clawed back — and a node that returns to gold resumes accrual on the very next tick with no manual step beyond the re-bench. A single canonical determination decides red: a node is red if any contributing sub-component is red — a visible bench-version mismatch, a red disk entity, or a red CPU, RAM, or network contribution — and gold requires every contributing sub-component to be current. There is no partial gold; any red component is decisive, and a missing or pre-versioning stamp is treated as red. That one verdict feeds every surface so the ServerScoreCard headline, the Nodes page, the Stoicism page, and the Argus and Triton surfaces always agree. The operator-facing surfaces are filled in to match: red is shown red on the ServerScoreCard headline and the Nodes-page ServerScore, a red node's Earn Score is forced to 0.0 in its usual yellow tone, the Stoicism page shows red for a red node, the Triton Panel becomes three tabs with a disk-tweaked eligibility view, the Jobs page gains friendly labels and a node/drive target, and the Argus rebench indicator becomes a clickable per-entity action. No scoring constant, weight, or mismatch rule moved; this is the missing economic gate plus the red visibility and controls, layered on top of Triptolemus's executable reuse.

Why “Nemesis”

Nemesis was the Greek goddess of divine retribution — the power that measured out fortune and struck down anyone who enjoyed good fortune they had not earned or escaped the consequence they were due. The codename captures the shape of this release relative to the one before it: Triptolemus propagated greenlight-gated reuse everywhere and made it a real bench-time decision, but a node whose score was red — stale, version-mismatched, or built on a failed sub-component — still quietly drew stoicism every tick and still displayed a non-zero Earn Score. That is unearned fortune. Nemesis exacts the reckoning: a red node stops earning the moment it is red, the same single verdict that says “red” is enforced everywhere the operator looks, and the only way back to earning is to re-bench and turn gold. The retribution is strictly forward-only — Nemesis withholds what is not yet earned; she never reaches back to take what was already justly accrued.

Headline changes

  • A red, stale, or red-sub-component score no longer generates stoicism — forward-only. While a node is red, stoicism accrual for that node produces exactly zero: both the per-tick scoring accrual path and the lower-level tip-accrual path refuse to add stoicism, and a red Tunnelee zeroes the whole accrual including the Tunneler’s fee slice. The gate is strictly forward-only — when a node turns red, future accrual stops, but stoicism already earned (pending or current) and already redeemed is never reduced, reversed, recomputed, or clawed back. There is no clawback. A node that returns to gold resumes accrual on the very next tick with no manual step beyond the re-bench; the red period remains a permanent gap with no retroactive backfill.
  • One single-source red determination drives every surface. A node is red if any contributing sub-component is red — a visible bench-version mismatch (minor, major, or unknown), a red disk entity, or a red/failed/stale CPU, RAM, or network contribution. Gold requires every contributing sub-component to be current; there is no partial gold and any red component is decisive. A missing or pre-versioning stamp is treated as red (worst-case assume not-current until a re-bench proves otherwise), and a never-benched node resolves to red — it is not a separate fourth state. The economic gate, the ServerScoreCard headline, the Nodes page, the Stoicism page, and the Argus and Triton surfaces all reach the same red/gold verdict for the same node at the same moment.
  • Red is shown red everywhere — and a red Earn Score is forced to 0.0. Red beats gold in the ServerScoreCard headline (a red sub-component renders the headline red even when the breakdown’s own version classification alone would have been gold), the Nodes page ServerScore is now rendered gold/red by the single-source determination instead of unconditionally gold, the Nodes Earn Score for a red node is forced to 0.0 while keeping its usual yellow tone (a yellow value that is automatically zero so the operator sees they are not earning), and the Stoicism leaderboard shows red for a red node so it agrees with the Nodes page and the score card. Already-accrued and already-redeemed totals on the Stoicism page display unchanged in value — the red signal is a status indication, not a restatement of history. A red Tunneler still collecting fees from gold Tunnelees shows those retained fees, not a misleading 0.0.
  • The Triton Panel is triple-tabbed, with a disk-tweaked eligibility view. The three entity groups (Virtual Chainweb, Real Chainweb Containers, Disk Entities) are now three tabs instead of three stacked sections; the content and selection behaviour of each group is preserved exactly. Selecting a Disk Entity now mounts a disk-tweaked Stoicism Eligibility view (previously a disk selection mounted nothing): there is no Provisioning commitment sub-tab, the Benchmark sub-tab shows only the Disk subscore with CPU/RAM/Network greyed and inert, and a disk benchmark runs a disk-only progress phase set rather than full-host or slice phases — using the existing disk-entity benchmark enqueue, no new trigger invented.
  • Jobs show friendly labels and a node/drive target; Argus rebench is a clickable per-entity action. The Jobs page renders a human-friendly label for each job kind instead of the raw internal job-kind string and adds a target identifier — which node and which drive — so a running disk benchmark is unambiguously attributable. On the Argus bench-versioning page the Status “rebench” indicator — previously plain, non-actionable text — becomes a clickable action that triggers the appropriate existing benchmark for that entity. The affordance applies to every Status the single-source determination classifies as red (“recalibrated” minor as well as “rebench” major/unknown); “current” and “patch” stay inert text, and the triggered job is discoverable on the Jobs page with its friendly label and target.

For operators

A red node now means exactly one thing: you are not earning until you re-bench. When a red node is skipped for accrual the gate emits a dedicated accrual-skip event, so you can see you stopped earning because the score is red and the remedy is to re-bench. The forced 0.0 Earn Score on the Nodes page (still in its usual yellow tone) and the red ServerScore are your at-a-glance signal; the score card headline and the Stoicism page agree with it because they all read the same single-source verdict.

Nothing you have already earned is at risk — the gate is forward-only and there is no clawback of accrued or redeemed stoicism. The remedy for a red node is always the same: re-bench. The Argus Status cell is now the fastest way to do that — click the rebench indicator for a red entity and the right benchmark is enqueued and shows up on the Jobs page with a friendly label and its node/drive target. The Triton Panel’s three tabs and the disk-tweaked eligibility view let you focus on one entity class and act on a disk entity the same way you already act on virtual ones.

Related

  • /docs/scoring — the canonical scoring documentation, now describing the red→no-stoicism economic gate: the single-source red determination (any red sub-component makes the whole node red), the forward-only zero-accrual rule, and that gold requires every contributing sub-component to be current.
  • Triptolemus — H.1.4 — the immediately preceding arc; Nemesis opens the H.1.5 minor on top of Triptolemus v.H.1.4, carrying its executable greenlight-gated reuse forward and adding the economic consequence: a red node that fails the reuse gate now also stops earning until it is re-benched to gold.