Blocked-by: objectstack-ai/cloud#1962
Seam card filed by the repo:cloud PM seat (objectstack#6026, session session_01EK4Q5Nrx779cxjdeTxsK7P) — 2026-09-04T03:2xZ. Named reader: the objectui execution seat (domain:ui), at candidate selection — ⛔ not before its blocker closes.
Why this card exists
On cloud#1288 (2026-08-15, os-zhuang, delegated adjudication) the maintainer ruled route B — the control plane owns the clock for hosted scheduled automation — and instructed:
Fold in the parked scope-3 item — surfacing getTriggerBindingAudit() as an environment-level health item — since it needs the same console surface; that is two cards, cloud's being the Blocked-by: of objectui's.
cloud#1962 is the cloud card (the ADR + the read-only exposure). This is the objectui card.
What it renders
The framework already produces the data: AutomationEngine.getTriggerBindingAudit() / getFlowRuntimeStates(), emitted today only as WARN lines at kernel:bootstrapped (per flow: flowName, triggerType, reason). cloud#1962 exposes them read-only as an environment-level health item. This card renders that item in the environment detail view so a user sees "this automation is not bound / not scheduled, and why" without an AI turn — the distinction cloud#1316's dev drew: letting verify_build see a binding failure is in-turn; letting the user see it is a console surface, and that is what cloud#1288 asked for.
⛔ Sequencing
Re-check
cloud#1288 (ruling comment 2026-08-15; unlock re-grade 2026-09-04) · cloud#1962 (the ADR card, its Blocked-by: and the health-item shape once drafted) · framework AutomationEngine.getTriggerBindingAudit().
Blocked-by: objectstack-ai/cloud#1962
Seam card filed by the
repo:cloudPM seat (objectstack#6026, sessionsession_01EK4Q5Nrx779cxjdeTxsK7P) — 2026-09-04T03:2xZ. Named reader: the objectui execution seat (domain:ui), at candidate selection — ⛔ not before its blocker closes.Why this card exists
On cloud#1288 (2026-08-15,
os-zhuang, delegated adjudication) the maintainer ruled route B — the control plane owns the clock for hosted scheduled automation — and instructed:cloud#1962 is the cloud card (the ADR + the read-only exposure). This is the objectui card.
What it renders
The framework already produces the data:
AutomationEngine.getTriggerBindingAudit()/getFlowRuntimeStates(), emitted today only as WARN lines atkernel:bootstrapped(per flow:flowName,triggerType,reason). cloud#1962 exposes them read-only as an environment-level health item. This card renders that item in the environment detail view so a user sees "this automation is not bound / not scheduled, and why" without an AI turn — the distinction cloud#1316's dev drew: lettingverify_buildsee a binding failure is in-turn; letting the user see it is a console surface, and that is what cloud#1288 asked for.⛔ Sequencing
Re-check
cloud#1288 (ruling comment 2026-08-15; unlock re-grade 2026-09-04) · cloud#1962 (the ADR card, its
Blocked-by:and the health-item shape once drafted) · frameworkAutomationEngine.getTriggerBindingAudit().