Documentation · Releases · Daedalus

Daedalus — H.1.3

v.Chronos.1.Daedalus — legacy v.H.1.3

Why “Daedalus”

Daedalus is the master craftsman of Greek myth — the maker who built the Labyrinth and the engineered wings, the figure of the constructed, measured artefact. The codename captures the shape of this release: before Daedalus the disk was a derived afterthought, a number computed on the fly from container rows and never owned by anything, so two parts of the system could construct it differently and disagree. Daedalus turns the storage substrate into a deliberately engineered, measured thing — a first-class entity that is benched, scored, and stamped in its own right, exactly the way container entities are, so every surface reads the same single figure built once at the same forge.

Codename note: this node ships at the legacy coordinate v.H.1.3 / H.1.3 — its canonical 4-designator coordinate is v.Chronos.1.Daedalus. The Name was re-drawn from the Olympian “Demeter” (major-tier deity, reserved for a Release-tier letter) to the next-unused minor-figure pool draw “Daedalus” under the codename-uniqueness / major-tier rule. The legacy v.H.1.3 token round-trips unchanged; only the human Name moved.

Headline changes

• Disk is a first-class benchmark entity. Every eligible drive now has its own Score, Stamped version, Last benched, Time since, and Status — surfaced the same way container entities are. The disk is no longer a value computed incidentally inside a container’s score path; it is its own measured thing that can be read, ranked, and rebenched on its own.
• Single-source disk subscore. The headline disk figure and the “details” disk figure are always the same number for the same drive. The drive entity is benched and scored once, and every container that touches it reads that one stored value. The prior class of divergence — where the same drive could show 1.738291 on one panel and 0.366113 on another — is gone by construction, not by reconciliation.
• N=1 Prime / ÷N slave equivalence. A Prime container that owns its whole drive gets exactly the disk entity score (the N=1 case — the full disk number for the whole drive). A slave container gets that same disk entity score divided by the number of containers on the drive. It is one formula whether the drive is shared or not — the shared case is just the unshared case with N greater than one.
• Drive benches carry a version stamp and join the greenlight / rebench-drift discipline. A drive bench run under a greenlit version stamps that version and reads gold; a non-live or absent stamp reads red and is retestable; an inherited or old-stamp disk value reads red. Rebenching any container on the drive — or triggering a direct disk bench — refreshes and re-stamps the drive entity, the identical discipline container entities already had.
• Argus is now a four-tab surface. The admin oversight panel splits into Fleet Distribution, Real Container Entities, Virtual Container Entities, and a new Disk Entities tab — so an operator can read drive entities directly instead of inferring drive health from the containers that happen to sit on it.
• Triton is now a three-group panel with a per-disk bench trigger. The user-facing panel shows Virtual Chainweb Entities, Real Chainweb Containers, and Disk Entities. A per-disk bench trigger lets an operator rebench a drive directly without going through a container; benching a container or a virtual entity also auto-populates the related disk group so the drive row is never blank for a benched fleet.

For operators

There is no operator action required for the divergence fix. It is structural — the headline and detail disk figures are the same number now because they read the same single source, not because anything reconciles them after the fact. Pre-existing drive-benchmark values that predate the single-source model read as red and retestable; there is no historical backfill. To clear a red drive, rebench it — that refreshes the entity and stamps it under the live version.

Two things are new at the operator surface. You can now rebench a disk directly from the Triton panel’s per-disk bench trigger without having to go through a container that sits on it. And you can read drive entities as first-class rows in the Argus Disk Entities tab — Score, Stamped version, Last benched, Time since, and Status, the same columns the container entity tabs carry. Old /docs/releases/demeter bookmarks keep working — they permanently redirect here, to the re-drawn /docs/releases/daedalus page.

Related

• /docs/scoring — the canonical scoring documentation, now describing the disk as a first-class benchmark entity: the single-source model, the N=1 Prime / ÷N slave equivalence, and disk greenlight/rebench-drift participation.
• Argus — H.1.2 — the immediately preceding arc; Daedalus opens the H.1.3 minor on top of Argus v.H.1.2n, carrying forward the bench-version stamp and greenlight discipline Argus established and extending it to the new disk entity.