coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

docs(canon): correct ADR-007 second-instance attribution
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
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 <noreply@anthropic.com>
This commit is contained in:
codex 2026-08-17 10:19:03 +02:00
parent dd65c91b4f
commit 77e0ac2bca
1 changed files with 9 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

10
canon/architecture/adr-007-workplan-identity-and-repo-worker-topology.md
View file

@ -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