2026-09-25 — Edit registry for chronicle-hq org rename to chronicle-cat
rank: decision outranks: []
Section titled “rank: decision outranks: []”2026-09-25 — Edit registry for chronicle-hq org rename to chronicle-cat
Section titled “2026-09-25 — Edit registry for chronicle-hq org rename to chronicle-cat”Date: 2026-09-25 Status: ratified Verb: petrova_act_registry_edit Slug: chronicle-hq MR-compliance: MR-7, MR-12
Rationale
Section titled “Rationale”GitHub org chronicle-hq was renamed to chronicle-cat (verified via gh api orgs/chronicle-hq → 404, gh api orgs/chronicle-cat → 200, billing email
matching the operator who requested this change). Repo names under the org
are unchanged (app, relay, docs, editor, schemas, .github), only
the org segment of each URL moves.
The registry slug is kept as chronicle-hq — it is an internal identifier,
not a live pointer, and renaming it would cascade into state/chronicle-hq.yaml,
this domain file’s filename, and every cross-reference in prior decision docs
and audit sweeps, none of which need to change to fix the actual break (a
stale url). Only registry.yaml > repos[chronicle-hq].url is corrected.
Historical prose in other entries’ notes fields that uses “chronicle-hq” as
a comparison label (e.g. sparki-tools, tektree-io entries) is untouched —
those are decisions about other repos made at the time, not live pointers.
Change summary
Section titled “Change summary”registry.yaml > repos[chronicle-hq]:
url:https://github.com/chronicle-hq/docs→https://github.com/chronicle-cat/docs
docs/domains/chronicle-hq.md regenerated via npm run domains:generate
(parts 1–2 only; parts 3–5 remain author-owned/unspecified, untouched by the
regenerate per the generator’s own non-overwrite rule).
Open follow-up
Section titled “Open follow-up”This slug’s domain allocation was already unspecified before this rename
(profile standard, no DR block, parts 3–5 unauthored — see
docs/domains/chronicle-hq.md). The rename does not change that; it remains
a separate, pre-existing gap, not something this decision closes.
Sign-off
Section titled “Sign-off”Human merge required per MR-12 — this PR is opened with the
awaiting-human-merge label and does not auto-merge.