The workplan list read as though GROUND-WP-0002, 0003 and 0005 each
existed twice. They did not: three inbound clay-borg finding reports were
filed in workplans/ borrowing the number of the workplan they bear on, and
each was registered in State Hub as a workplan.
A report is correspondence, not a unit of work. The three move to
reports/YYMMDD-<slug>.md with their own id space (GROUND-RPT-0001..0003),
keeping type: report, status: informational and the extends: link to the
workplan they relate to. Their state_hub_workstream_id bindings are
dropped and the hub registrations archived, so the hub's workplan list
matches the files.
Five workplans, one file per number.
AGENTS.md records the convention, since the reports arrive regularly and
nothing in the repo said where they go.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
fix-consistency C-06 registered the report file and wrote back its id.
Note: it is a report extending GROUND-WP-0002, not a workplan of its own
-- the hub now carries a workstream row for it because it lives under
workplans/. Harmless, but if report files become common they want their
own directory.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Extends GROUND-WP-0002 as a file rather than an inbox message -- the
message of 2026-07-30 sat unread for four days, and the failure was that
nothing pointed at it.
clay-borg retracts "4/6/9 against 5/7/9, no dataset reconciles them."
With Problems.csv imported the measurement is 6/9/12 against 5/7/9 and the
scenario is renamed -unreachable- to -reachable-, confirming this repo's
2026-08-03 void ruling from the engine side. It was still queued to be
re-sent until clay-borg's adversarial review caught it.
Also acknowledges that all ten U-item rulings of 2026-08-03 had not been
collected by clay-borg -- its own survey still said "0 of 10 ruled" two
days later. No ruling is requested in this report.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
