69 lines
2.9 KiB
Markdown
69 lines
2.9 KiB
Markdown
# Daily-Triage Stabilization Status
|
|
|
|
Updated: 2026-06-27
|
|
|
|
## Purpose
|
|
|
|
Track the current daily-triage blocker chain for `CUST-WP-0051-T04` without
|
|
duplicating the source activity-core workplans.
|
|
|
|
## Current Evidence
|
|
|
|
State Hub `daily_triage` progress shows the scheduled activity-core runner is
|
|
alive and can write both State Hub progress and working-memory notes.
|
|
|
|
Recent scheduled run evidence:
|
|
|
|
| Date | State Hub event | Result |
|
|
| --- | --- | --- |
|
|
| 2026-06-24 | `8b4c16ee-ac47-4581-b3ee-a23fc1f682e6` | schema-valid daily triage, working memory written |
|
|
| 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 |
|
|
|
|
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.
|
|
|
|
## Current Blocker
|
|
|
|
The old `ACTIVITY-WP-0010` State Hub bridge note is partially superseded by the
|
|
newer evidence: scheduled runs are reaching State Hub and the working-memory
|
|
sink. The current primary blocker is that the live activity-core runtime still
|
|
uses an output path that can discard the whole report when the model emits a
|
|
malformed tail.
|
|
|
|
`ACTIVITY-WP-0016` has the repo-side mitigation:
|
|
|
|
- strict bounded report schema;
|
|
- item-granular recovery and quarantine;
|
|
- producer guardrails and ADR-004;
|
|
- regression tests for the 2026-06-26 failure shape.
|
|
|
|
The remaining gate is the live deployment/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`.
|
|
|
|
## Hygiene Note
|
|
|
|
The State Hub task index currently shows stale duplicate tasks for
|
|
`ACTIVITY-WP-0016` in addition to the source-file task records. Before relying
|
|
on activity-core task counts for triage ranking, run activity-core consistency
|
|
sync and prune or reconcile any stale generated task rows that are no longer
|
|
linked from the workplan file.
|
|
|
|
2026-06-27 status-normalization: ACTIVITY-WP-0016 source task blocks now
|
|
match the progress notes for T04 (done) and T05 (progress). Remaining hygiene is
|
|
to remove or reconcile stale duplicate task rows from the State Hub index.
|
|
|
|
2026-06-27 gate cleanup: ACTIVITY-WP-0010-T02 is now done because scheduled
|
|
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.
|