Attention queue
Grounded exceptions and explicit requests.
AC Control Centre | Operations workspace
Exceptions and decisions first. Runtime claims remain separate from verified outcomes.
Grounded exceptions and explicit requests.
Current published items only.
Execution, output validity, action verification and assurance stay separate.
Availability metadata only.
Blocked or failed Publishing Studio schedules. The Studio republishes this on every scheduler run, so a stale panel means the scheduler itself has gone quiet.
Current feeds for decisions and commitments. Missing and stale sources remain explicit.
Private, current aggregate only.
Registry, schedules and a read-only four-dimension health projection. Submission creates one queue record only.
Expand for schedule, source and outputs.
No credential or session handling.
You can still create and edit a local request draft. The server must explicitly enable the queue write lane before it can be submitted.
Draft locally, review the boundaries, then submit only if the server reports the lane enabled.
Runtime reports, review states and verified outcomes remain visibly distinct.
An approval is an immutable gate decision about a stated effect. It is never proof that work completed.
Evidence-backed changes to process loops, prompts, tools or verification.
Published with evidence and a bounded experiment.
Observed failures and staleness. These are not recommendations by themselves.
Output references, check summaries, assets and source freshness.
Hub, Admin and Publishing sessions. Global sign-out revokes the Hub parent and every linked application session.