Name the migration repository in the map, so nobody has to be told it exists #99

2026-09-24T00:01:58Z

jschoubben commented

2026-09-24 00:01:58 +00:00

The operator asked why the migration's hand-off was not in hq, having had to be told where it was. It cannot be in hq — it names machines, addresses, ports and paths, because a procedure that cannot be followed is not one, and this repository is public. But hq can say where that record is, which is exactly what 00-META/repos.md is for, and I should have used it.

One row: what the migration repository holds, why it is private, and that HANDOFF.md is where somebody picking the work up starts.

The operator asked why the migration's hand-off was not in hq, having had to be told where it was. It cannot be in hq — it names machines, addresses, ports and paths, because a procedure that cannot be followed is not one, and this repository is public. But hq can say **where** that record is, which is exactly what `00-META/repos.md` is for, and I should have used it. One row: what the `migration` repository holds, why it is private, and that `HANDOFF.md` is where somebody picking the work up starts.

jschoubben added 1 commit 2026-09-24 00:01:59 +00:00

Name the migration repository in the map, so nobody has to be told it exists 545d038198

hq cannot hold the migration's operational record — it names machines, addresses and
paths, and this repository is public — but it can say where that record is, which is what
this map is for. Asked for by the operator, who had to be told.

jschoubben merged commit 91a5c63d65 into main

2026-09-24 00:02:08 +00:00

jschoubben deleted branch meta/name-the-migration-repository

2026-09-24 00:02:08 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#99