docs: expose daily security flow scheduling boundary
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a15374-f59f-7a31-86d2-d23b5d2ed181
This commit is contained in:
parent
f9f8df0392
commit
70ff24197a
1 changed files with 13 additions and 0 deletions
13
SCOPE.md
13
SCOPE.md
|
|
@ -342,3 +342,16 @@ description: >
|
|||
normalized execution evidence while leaving work-item lifecycle downstream.
|
||||
keywords: [temporal, workflow, event-bridge, ops-run, glas, task, report, evidence, cron, event, rule, instruction, org-automation]
|
||||
```
|
||||
|
||||
## Daily security-flow consumer
|
||||
|
||||
`activity-definitions/daily-security-flow.md` supplies a fixed-command daily
|
||||
schedule for the Custodian security-flow runner (CUST-WP-0079-T03,
|
||||
ACTIVITY-WP-0047). Activity Core owns scheduling and ops_run evidence; the
|
||||
claiming workstation rein owns execution, and the Custodian script owns report
|
||||
and recipient checkpoint delivery. The definition carries no repository grant.
|
||||
|
||||
The checked-in definition remains disabled pending workstation/hub acceptance,
|
||||
owner activation and the first unassisted fire. This source integration does
|
||||
not establish an active automation. Consumers can reuse the existing schedule,
|
||||
execution queue and profile contract rather than add another scheduler.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue