Documentation · Releases · Asclepius

Asclepius

v.G.1.x — Asclepius — stamped against H.1.19

The audit-cycle codename: a reserved landing place where future audit cycles append, mending and hardening the launched system one patch-number at a time.

Asclepius is the v.G.1.x audit-cycle codename inside the Genesis launch era — the mender that hardens and repairs the launched system across recurring audit cycles. It is a real additive Boreas forest node whose Genesis-0 is reserved-empty at spec-start: its prior firewall content was faithfully attributed to its own distinct node, Cerberus (legacy v.G.1.1), so Asclepius's member tier is legitimately empty until a real audit cycle lands as patch-number 1. This deliberately-reserved-empty state is doctrine, not a defect — it is never fixed by synthesising a fabricated entry. Each future audit cycle ships with its own spec, its own phase plan, its own audit trail, and appends under Asclepius as the next patch-number.

Why “Asclepius”

Asclepius is the healer-physician of Greek myth, son of Apollo — the mender who restores what was broken. The codename captures the shape of this release: the v.G.1.x line is not a feature launch but the recurring audit cyclethat diagnoses and repairs the system Genesis shipped, hardening it cycle by cycle. The original “Genesis Patches” was a placeholder label rather than a drawn codename; the re-draw gives the audit-cycle line a proper mortal-tier Name under the codename-uniqueness / major-tier rule.

Codename note: this node ships at the legacy coordinate v.G.1.x. The Name was re-drawn from the placeholder “Genesis Patches” to the minor-figure pool draw “Asclepius”. The legacy v.G.1.x token round-trips unchanged; only the human Name moved. Old /docs/releases/genesis-patches bookmarks keep working — they permanently redirect here, to the re-drawn /docs/releases/asclepius page.

The reserved-empty Genesis-0 (audit-cycle codename)

Asclepius is the designated landing place for the Genesis post-launch audit cycles. Under the Genesis-0 anchor model every codename’s prior history compacts to its patch-number 0 “Genesis” entry — but a reserved codename’s Genesis-0 may legitimately be empty. That is exactly Asclepius’s state at spec-start: its prior firewall content was faithfully attributed elsewhere (to the Cerberus node, see below), leaving its member tier the empty set ∅ until a real audit cycle lands as patch-number 1. This deliberately-reserved-empty state is stated explicitly as doctrine — it is nota defect, never “fixed” by synthesising a fabricated entry, and never manufactured by falling back to a coarser grain. The codename and its node still exist; only the member tier is empty.

Future audit cycles append under Asclepius as patch-numbers 1, 2, 3, … — each its own spec with its own phase plan and audit trail.

Cerberus is its own distinct node

Cerberus (hub-managed UFW) is not Asclepius content. The firewall material was aligned out of the audit-cycle section into its own ## Cerberus — v.G.1.1 changelog section, and Cerberus is its OWN distinct Boreas forest node (legacyMap:['v.G.1.1']) with its own canonical per-codename page. It is the first patch of the Genesis post-launch line at its own coordinate — distinct from, not the same as, the Asclepius audit-cycle codename.

Cerberus release page — the canonical per-codename surface for the v.G.1.1 hub-managed UFW release lives at /docs/releases/cerberus, its own distinct node — not embedded here.
Cerberus public docs chapter — the operator-facing reference for hub-managed UFW lives at /docs/tools/firewall, covering baseline policy, per-server overrides, drift detection, and the audit surface.
Asclepius release page — this page. The home for every future Genesis audit cycle; each new cycle appends under Asclepius as the next patch-number.

Patch log

No audit cycle has landed under Asclepius yet — the Genesis-0 member tier is reserved-empty at spec-start by design. The patch log will populate as v.G.1.x audit cycles ship as patch-number 1, 2, 3, ….

Cerberus — v.G.1.1 — its own distinct Boreas node: the first Genesis post-launch patch (hub-managed UFW). Asclepius is the audit-cycle codename; Cerberus is a separate node/page, not Asclepius content.
Versioning — the grammar explainer, including the audit-cycle-codename governance rule and why a reserved codename’s Genesis-0 can legitimately be empty at spec-start.