coulomb/the-custodian
Archived
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Record daily triage clean streak checkpoint

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-30 10:07:28 +02:00
parent 3ef57f63c1
commit cb7fd7b19d
3 changed files with 65 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
docs/daily-triage-stabilization-status.md
View File

@@ -1,6 +1,6 @@
# Daily-Triage Stabilization Status
Updated: 2026-06-27
Updated: 2026-06-30
## Purpose
@@ -20,10 +20,16 @@ Recent scheduled run evidence:
| 2026-06-25 | `cbba6bc0-14cb-492b-ab23-74b9349326c8` | schema-valid daily triage, working memory written |
| 2026-06-26 | `97fd20a0-eee0-45ea-8290-6d91874e1515` | validation failed at char 5268, working memory written |
| 2026-06-27 | `c5ab50a8-404b-4e30-849f-841b059ace65` | validation failed at char 5246, working memory written |
| 2026-06-28 | `f0d8477e-1db9-4c07-bb8c-d28cbb868abc` | schema-valid daily triage, working memory written; still emitted 10 recommendations |
| 2026-06-29 | `176d2ea7-f0e3-48cd-999b-4ab6055c6a55` | schema-valid daily triage, working memory written; still emitted 10 recommendations |
| 2026-06-30 | `27d695b2-a537-481b-ada6-ca84ec24cd96` | schema-valid daily triage, working memory written; still emitted 10 recommendations |
The 2026-06-26 and 2026-06-27 failures are both overlong malformed JSON
responses from `daily-triage-report`. They are not missed schedules and they are
not silent sink failures.
not silent sink failures. The 2026-06-28 through 2026-06-30 events restore a
three-run schema-valid streak, but they do not prove the bounded WP-0016
contract because the reports still emit 10 recommendations instead of the
targeted top-N framing.
## Current Blocker
@@ -40,15 +46,16 @@ malformed tail.
- producer guardrails and ADR-004;
- regression tests for the 2026-06-26 failure shape.
The remaining gate is the live deployment/smoke path:
The remaining gate is the live contract/smoke path:
1. Deploy the WP-0016 code and schema together.
2. Update the Railiance runtime prompt bundle with bounded top-N instructions,
per-item framing, value vocabularies, and sufficient `max_tokens` headroom.
3. Run a live daily-triage smoke on railiance01 and confirm malformed-tail
output degrades to partial valid output with quarantined items.
4. Resume the three-clean-scheduled-run gate for `ACTIVITY-WP-0006-T03` and
`ACTIVITY-WP-0010-T04`.
4. Record the 2026-06-28 / 2026-06-29 / 2026-06-30 three-clean-run
calibration result with the caveat that top-N contract adoption is still
pending.
## Hygiene Note
@@ -66,3 +73,14 @@ to remove or reconcile stale duplicate task rows from the State Hub index.
runner evidence proves the State Hub sink and working-memory path are reachable.
The live human-needed notes now sit on the post-deployment smoke, WP-0016 live
proof, and three-clean-run calibration tasks.
2026-06-30 recheck: State Hub now has schema-valid scheduled `daily_triage`
events for 2026-06-28 (`f0d8477e-1db9-4c07-bb8c-d28cbb868abc`), 2026-06-29
(`176d2ea7-f0e3-48cd-999b-4ab6055c6a55`), and 2026-06-30
(`27d695b2-a537-481b-ada6-ca84ec24cd96`), all with working-memory notes. This
is enough to bank the scheduling/sink/schema-validity streak for calibration,
but not enough to close the WP-0016 live-proof gate: the reports still contain
10 recommendations rather than the bounded top-N contract, and the local
activity-core worktree already has separate in-flight diagnostic/status changes
that should be committed by their owner before Custodian treats them as source
truth.