coulomb/activity-core
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
activity-core/activity-definitions/weekly-railiance-allocation-review.md
tegwick 4ae00fcd23
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Build and Publish Container Image / build-and-push (push) Successful in 2m22s
Details
feat: route Custodian routines through bounded owner operations 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a15374-f59f-7a31-86d2-d23b5d2ed181
2026-10-19 13:53:00 +02:00

2.3 KiB
Raw Permalink Blame History

id name enabled owner governance status trigger context_sources
weekly-railiance-allocation-review Weekly Railiance allocation review false activity-core custodian proposed
type cron_expression timezone misfire_policy
cron 0 8 * * 1 Europe/Berlin skip
type query operation required params bind_to
shell custodian_allocation_review custodian_allocation_review true
timeout_seconds evidence_sinks
240
type event_type author
state-hub-progress custodian_allocation_review activity-core
context.custodian_result

Weekly Railiance allocation review

Disabled source preparation using the existing ACT-ADR-007 bounded-operation stage. This definition emits no agent tasks or ops_runs. The worker runs one code-fixed owner command, retains a counted/hash receipt in the activity context, and passes it through the existing progress evidence sink. No model or coding profile executes this routine. No arbitrary command, import, executable or path is accepted from definition parameters.

The operator must bind the actual deployed owner code, fleet snapshot root, private external state, and scoped Hub access/input request before enabling. See docs/custodian-bounded-operations.md. These bindings are absent by default; missing paths, redirected paths and unbound requests fail before subprocess execution. This is not a credential-isolation claim or a runtime acceptance.

Single Temporal attempt; skip misfires. Owner checkpoint/retention semantics govern retries. A completed command is not owner acknowledgment or independent missed-run recovery. No schedule has been activated or deployed. Rollback is enabled: false, retaining reports/checkpoints.

CUST-WP-0071-T05 owns acceptance, after T04. The fixed owner command is scripts/weekly_allocation_report.py --request <operator-bound request>. The request binds real retained captures, explicit as_of and durable output; inputs remain under accepted roots and output stays in private runtime state. The committed null request template is not production input. Stable recommendation IDs are downstream upsert keys; the adapter neither creates owner work records nor delivers their acknowledgments. Actual collection, durable retention, accepted owner routing, weekly report receipt and missed-run recovery remain gates.