Set up daily WSJF closure gates
This commit is contained in:
parent
418eb4ffda
commit
4e8ccbb344
9 changed files with 431 additions and 4 deletions
|
|
@ -24,6 +24,20 @@ the ConfigMap projection from that file before enabling the probe schedule.
|
|||
`OPS_HUB_KEY` is created only as an empty Secret placeholder until the operator
|
||||
provisions the Inter-Hub ops-hub key.
|
||||
|
||||
The same runtime projection now includes the active
|
||||
`daily-statehub-wsjf-triage.md` ActivityDefinition plus its JSON output schema
|
||||
and a persistent working-memory volume mounted at
|
||||
`/home/worsch/the-custodian/memory/working`. Before trusting the daily 07:20
|
||||
Europe/Berlin schedule, verify both runtime dependencies:
|
||||
|
||||
- `actcore-state-hub-bridge` can reach the State Hub API through the node-local
|
||||
tunnel expected at `127.0.0.1:18000`.
|
||||
- `LLM_CONNECT_URL` is set to an operator-approved llm-connect endpoint that can
|
||||
serve the `custodian-triage-balanced` profile.
|
||||
|
||||
If `LLM_CONNECT_URL` is missing or broken, report-sink instructions write a
|
||||
visible `execution_failed` diagnostic instead of silently producing no report.
|
||||
|
||||
## Deploy
|
||||
|
||||
```bash
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue