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

docs(canon): correct ADR-010 on divergence shapes, mechanism, and outcome
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Three dated corrections, following the blockquote convention ADR-007 uses:

- Decision 2's merge/refresh dichotomy is not exhaustive. Repository records
  took a third shape — cache-only records whose source exists and is reachable
  but was never introduced to central. Refreshing would have destroyed them.
- The Context recorded the shared port but not why it was silent: an unbound
  ssh -L binds every loopback family, and ExitOnForwardFailure fires only when
  every bind fails.
- A new Outcome section states that the ADR's own remediation never landed and
  the condition was still live seven weeks later.

Refs CUST-WP-0067-T06

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
codex 2026-08-24 23:46:33 +02:00
parent 3c1e93186f
commit 563e7811b9
2 changed files with 91 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

22
workplans/CUST-WP-0067-hub-authority-target-resolution.md
View file

@ -265,7 +265,7 @@ only there.
```task
id: CUST-WP-0067-T06
status: todo
status: done
priority: medium
state_hub_task_id: "007bfcf1-3b17-5d4a-b16a-b80ebf273934"
```
@ -290,6 +290,26 @@ this record class and record the local-instance retirement as the outcome.
Acceptance: ADR-010 revised with a dated superseding note linked to this
workplan; `ops-bridge` and the port map documented as the structural fix.
**Done (2026-08-24):** three dated corrections added to `ADR-010`, following the
in-file blockquote convention `ADR-007` already uses.
- **Decision 2** — the merge/refresh dichotomy is not exhaustive. Records the
third shape: cache-only records whose authoritative source exists and is
reachable but was never introduced to central, remedied by re-derivation
rather than refresh or merge. Refreshing would have destroyed the 44.
- **Context** — the ADR recorded the shared port but not why it was silent,
which is the part that let it persist for seven weeks. An unbound `ssh -L`
binds every loopback family and `ExitOnForwardFailure` fires only when all
binds fail, so the tunnel reported success while serving an address nothing
resolved to by default.
- **Outcome section** — states plainly that the ADR's own remediation never
landed, and that the condition it measured was still live seven weeks later.
An ADR describing a fix in the present tense reads as a fix that happened.
Also records the deeper cause as a second instance of the ADR's own theme:
the hub resolved its classification vocabulary from developer-workstation paths,
so authority depended on where a process happened to run.
## Repoint the fleet's copied port map
```task