From 77e0ac2bca6c55ae01a50498bad56462d015ac47 Mon Sep 17 00:00:00 2001 From: codex Date: Mon, 17 Aug 2026 10:19:03 +0200 Subject: [PATCH] docs(canon): correct ADR-007 second-instance attribution custodian-sync@railiance.local is a hardcoded default git identity in consistency_check.py, not proof of which machine synced. The real evidence is the timezone split (+0000 and +0200) across sync commits. Co-Authored-By: Claude Opus 5 --- ...r-007-workplan-identity-and-repo-worker-topology.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/canon/architecture/adr-007-workplan-identity-and-repo-worker-topology.md b/canon/architecture/adr-007-workplan-identity-and-repo-worker-topology.md index afffb47..af8c357 100644 --- a/canon/architecture/adr-007-workplan-identity-and-repo-worker-topology.md +++ b/canon/architecture/adr-007-workplan-identity-and-repo-worker-topology.md @@ -29,7 +29,15 @@ UUIDs: | Registrar | Workplan UUID | Reachable at `127.0.0.1:8000` | |---|---|---| | Workstation hub (`make api`, local postgres) | `03f38314` | yes | -| railiance01 primary, via `custodian-sync@railiance.local` | `bbfce36a` | **404** | +| A second instance, over a second database | `bbfce36a` | **404** | + +The second instance is *not* identifiable from the commit author. +`custodian-sync@railiance.local` is a hardcoded default git identity in +`scripts/consistency_check.py:1899` (`GIT_SYNC_USER_NAME` / +`GIT_SYNC_USER_EMAIL`), so every machine running `fix-consistency` commits under +that name. The discriminator is the timezone: sync commits appear under both +`+0000` and `+0200` (the workstation's offset), which is independent evidence of +two machines writing to one repository. Both write their IDs into the same git-tracked workplan file, so each sync overwrites the other's IDs and the file flip-flops on every round trip. The same