coulomb/key-cape
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record the stale-claim correction alongside the others

Browse source 
A message to railiance-platform listed the upstream issuer pin as outstanding
when the committed receipt showed it done ten hours earlier. Corrected to them
directly; recorded here with the other two instances because the pattern is the
point, not the individual slip. docs/evidence/ is the authoritative artifact for
live proofs in this repository, and reading it is cheaper than the corrections
it prevents.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NV9oijZukGyGbRQGGKnK4P

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 713576@bnt-lap001
Assistant-Session: 384c511d-9bce-4cb8-a676-2aef6c0c8df6
This commit is contained in:
tegwick 2026-09-09 16:41:10 +02:00
parent cb25ec2a8d
commit 04931387f5
1 changed files with 12 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

14
workplans/KEY-WP-0028-browser-client-field-validation.md
View file

@ -74,6 +74,16 @@ Two consequences, both corrected within the session:
unimplemented was withdrawn with a rationale pointing at the implementation.
Nothing was built on it.
A third instance followed the same day, outside this task: a message to
railiance-platform (d361bf28) listed the upstream issuer pin as outstanding when
`docs/evidence/2026-09-09-upstream-issuer-pin.json` showed it done ten hours
earlier — `check_before.issuer_matches: false`, then pinned to
`https://auth.coulomb.social`. Corrected in dd827b9f. The concern itself was
sound; only the claim that it was still owed was wrong, and the two are worth
separating rather than letting the correct half excuse the other.
The lesson worth keeping: in a repository where several sessions work at once,
blocker prose ages faster than the code it describes. Re-read the source before
acting on a workplan's description of it.
prose ages faster than the code and the receipts it describes. `docs/evidence/`
is the authoritative artifact for anything claiming a live proof here. Read it
before writing "outstanding", "unproven" or "not done" — that check is cheaper
than any of the corrections it would have prevented.