coulomb/activity-core
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
activity-core/activity-definitions/daily-security-flow.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 Blame History

id name enabled owner governance status trigger context_sources
daily-security-flow Daily Security Flow false activity-core custodian proposed
type cron_expression timezone misfire_policy
cron 30 7 * * * Europe/Berlin skip
type query operation required params bind_to
shell custodian_security_flow custodian_security_flow true
apply timeout_seconds evidence_sinks
true 240
type event_type author
state-hub-progress custodian_security_flow activity-core
context.custodian_result

Daily Security Flow

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.

ACTIVITY-WP-0047 / CUST-WP-0079-T03 owns acceptance. The former harness.agent-dev-local@1.1.1 rule was incompatible: its green-commit-only allowlist cannot invoke Python and its sandbox denies Hub egress. The fixed owner command is scripts/security_flow_daily.py --apply, with operator-bound --root, --hub and --state-dir. The owner script performs decision sync and deduplicated messages; the adapter does not message independently. Its receipt does not prove transport delivery or acknowledgment. The old ops_run-based first-fire criterion is replaced with bounded activity/report/sink receipts.