coulomb/activity-core
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Set up daily WSJF closure gates

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-07 11:00:03 +02:00
parent 418eb4ffda
commit 4e8ccbb344
9 changed files with 431 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
workplans/ACTIVITY-WP-0006-post-triage-operational-hardening.md
View File

@@ -8,7 +8,7 @@ status: active
owner: codex
topic_slug: custodian
created: "2026-06-03"
updated: "2026-06-06"
updated: "2026-06-07"
state_hub_workstream_id: "5646e13a-13af-4724-bca6-3c0d86f96733"
---
@@ -134,6 +134,22 @@ worker let Temporal complete the run, and the hardened report path emitted a
validation-failure note instead of losing the evidence. This run is useful
calibration input, but it is not a clean consecutive scheduled success.
2026-06-07: Investigated the missing June 7 WSJF result. State Hub had no
`daily_triage` event for the date, no local activity-core DB/Temporal/API ports
were reachable, and the current Railiance Kubernetes context had no
`activity-core` namespace. The Railiance runtime projection also lacked
`daily-statehub-wsjf-triage.md`, and the node-local State Hub bridge target
`127.0.0.1:18000` returned connection reset. Patched activity-core to project
the daily definition, mount the schema and working-memory storage, expose
`LLM_CONNECT_URL`, include `working_memory_path` in State Hub progress detail,
and emit a visible `execution_failed` report for report-sink instructions when
llm-connect is missing or broken. Cross-repo closure tasks were posted via
State Hub to `state-hub` (`dc10704f`), `railiance-cluster` (`53e78702`),
`llm-connect` (`cf758ed8`), `the-custodian` (`7a5d4e62`), and
`activity-core` (`28d11021`). This task remains waiting on a deployed, healthy
activity-core runner plus three clean scheduled daily runs and calibration
feedback.
## Rule Action Contract Documentation
```task

15
workplans/ACTIVITY-WP-0007-ops-inventory-probe-runner.md
View File

@@ -8,7 +8,7 @@ status: active
owner: codex
topic_slug: custodian
created: "2026-06-05"
updated: "2026-06-05"
updated: "2026-06-07"
state_hub_workstream_id: "c91a0946-92f9-4b41-8a92-005b29952916"
---
@@ -252,6 +252,19 @@ activation, the operator-gated ops-hub widget/API-key path in `CUST-WP-0047`.
closure remains waiting on applying the updated Railiance manifests and on the
operator-gated Inter-Hub ops-hub widget/API-key path.
2026-06-07: Added the remaining deployment handoff for this gate while
investigating the missing daily WSJF run. The Railiance runtime projection now
includes the daily WSJF definition alongside the disabled ops probe definition,
schema/config support needed by the shared worker, and a working-memory PVC.
No live `ops_inventory_probe` event exists yet, and the cluster currently lacks
an `activity-core` namespace. Cross-repo closure tasks were posted via State
Hub to `railiance-cluster` (`53e78702`), `inter-hub` (`f3ec4a36`),
`the-custodian` (`7a5d4e62`), `state-hub` (`dc10704f`), and `activity-core`
(`28d11021`). This task remains waiting on live manifest application,
`actcore-sync`, a disabled manual probe trigger, State Hub
`ops_inventory_probe` evidence, and an Inter-Hub activation or explicit defer
decision.
## Review Verdict
activity-core should provide this as a bounded probe-and-evidence capability.