coordination: attach accepted daily security schedule owner workplan
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Reject generated-only commits / generated-commit-guard (push) Successful in 7s

This commit is contained in:
codex 2026-10-13 21:17:19 +02:00
parent 1d9814b887
commit 8fb66bcbce
2 changed files with 24 additions and 6 deletions

View file

@ -4,9 +4,14 @@
"beneficiary_workplan_id": "CUST-WP-0079",
"beneficiary_task_id": "CUST-WP-0079-T03",
"obligor_repo": "activity-core",
"obligor_workplan_id": null,
"obligor_workplan_id": "ACTIVITY-WP-0047",
"state": "waiting",
"reason": "Awaiting schedule owner acceptance and named non-residual owner task; workstation user service bus unavailable. No founder act requested.",
"reason": "Schedule owner accepted; awaiting claiming rein workstation/hub acceptance, owner activation and the first unassisted fire. Definition remains disabled; no founder act requested.",
"proposal_message_id": "117e538e-da06-48b8-ba68-b82300a832e7",
"progress_receipt_id": "8edea261-4841-4db7-bc0e-1db8021106a6"
"progress_receipt_id": "8edea261-4841-4db7-bc0e-1db8021106a6",
"owner_reply_message_id": "00704319-97b2-469c-977e-6168ef20b9f9",
"owner_workplan_uuid": "ee97869b-dca2-54c9-aa18-0b479c244fb3",
"owner_source_commit": "83e6446807c4b36f3aa5023a5c16d4c7df8bd3df",
"observed_at": "2026-10-13",
"schedule_enabled": false
}

View file

@ -8,7 +8,7 @@ status: blocked
owner: claude-code
topic_slug: custodian
created: "2026-10-11"
updated: "2026-10-12"
updated: "2026-10-13"
flavor: implementation
depends_on: []
state_hub_workstream_id: "ab288f92-d364-5c24-9362-aee451f266c3"
@ -62,8 +62,8 @@ id: CUST-WP-0079-T03
status: wait
priority: high
state_hub_task_id: "1be0569c-221d-5925-a0ff-fd2af88e52b1"
blocked_on: message-from:activity-core
blocking_reason: "Awaiting daily schedule owner acceptance; workstation user service bus unavailable. Handoff 117e538e-da06-48b8-ba68-b82300a832e7."
depends_on: [ACTIVITY-WP-0047]
blocking_reason: "Activity Core accepted the schedule in ACTIVITY-WP-0047. Await claiming rein workstation/hub acceptance, owner activation and the first unassisted fire with report/checkpoint evidence."
```
Run `sync_resolved_decisions.py --apply` and `security_flow_report.py --json` daily (activity-core
@ -82,6 +82,19 @@ is attached to `case:cross-owner:CUST-WP-0079-T03:activity-core`
invented. Schedule activation remains pending: workstation `systemctl --user` cannot connect to its
user bus (`No data available`), so checked-in units alone do not establish daily execution.
2026-10-13 owner return: Activity Core accepted the handoff in message
`00704319-97b2-469c-977e-6168ef20b9f9`. Verified owner record
`ACTIVITY-WP-0047` (implementation, active) and committed definition
`activity-definitions/daily-security-flow.md`: daily 07:30 Europe/Berlin,
misfire skip, fixed `python3 scripts/security_flow_daily.py --apply` command,
correlation CUST-WP-0079-T03, no repository grant. Definition remains
`enabled: false`; source acceptance is complete, activation is not.
The existing coordination case now names ACTIVITY-WP-0047 as obligor. T03
remains wait until its claiming rein can reach workstation checkouts/the hub,
the owner activates the schedule, and the first unassisted fire proves completed
ops_run, report delivery and checkpoint behavior. No scheduler was enabled and
no foreign owner task was changed by this reconciliation.
## Encode the standing change rule as a policy-nexus guardrail
```task