Runner Readiness
Operating health for the connected external runtime — is it ready to work Daybreak’s briefing queue? Runtime is not runner: one runtime hosts many runner profiles.
Runtime connection
An external orchestrator runtime is connected and polling Daybreak's queue. Runtime is not runner — it hosts the profiles below.
Connected
- Connected runtimeOrchestrator runtimeOne runtime works the whole queue (demo)Ready
- Last pollToday · 5:38 AMDemo value — no polling is implementedReady
- Last receipt postedToday · 10:31 AMMost recent receipt the runtime posted backReady
Runner profile readiness
Logical work lanes the connected runtime can operate. A profile is ready when it has at least one active briefing template.
2 of 5 profiles operating
- Store OpsOrchestrator runtime lane1 active of 1 template(s)Ready
- Executive BriefingOrchestrator runtime lane1 active of 1 template(s)Ready
- Labor WatchOrchestrator runtime lane1 template(s), none active yetWarning
- Catering ProgramOrchestrator runtime lane1 template(s), none active yetWarning
- Regional PerformanceOrchestrator runtime lane1 template(s), none active yetWarning
Template readiness
Briefing templates define the work. A template is blocked when it needs setup or is missing a runner, audience, or channel.
2 active · 1 draft · 1 needs setup
- Daily Store Focus BriefingStore OpsDaily at 6:30 AM local timeReady
- Weekly Executive BriefingExecutive BriefingWeekly Monday at 7:00 AMReady
- Labor Exception BriefingLabor WatchNeeds setupBlocked
- Catering Program Weekly UpdateCatering ProgramDraft — not yet activeWarning
- Regional Performance BriefingRegional PerformanceArchived — intentionally not in rotationIdle
Recipient & channel readiness
Who briefings route to and how they reach them. Templates missing an audience or channel block delivery.
8/8 recipients reachable
- Daily Store Focus BriefingRecipients & channel set2 audience · 1 channel(s)Ready
- Weekly Executive BriefingRecipients & channel set2 audience · 1 channel(s)Ready
- Labor Exception BriefingRecipients & channel set2 audience · 1 channel(s)Ready
- Catering Program Weekly UpdateRecipients & channel set2 audience · 1 channel(s)Ready
- Primary channels8 of 8 recipientsRecipients with a primary delivery channelReady
Business object & data mapping
Business objects an external runtime can pull context for. Unmapped objects can be referenced but lack a data-source mapping.
5 of 6 objects mapped
- Catering ProgramNo data source mappingprogramWarning
- Tampa-East RegionMapped to a data sourceregionReady
- BrandonMapped to a data sourcestoreReady
- Downtown TampaMapped to a data sourcestoreReady
- RiverviewMapped to a data sourcestoreReady
- Wesley ChapelMapped to a data sourcestoreReady
Queue health
Live state of the briefing queue the runtime works. Counts mirror the Briefing Feed exactly.
1 need attention
- In queue1 jobsQueued · claimed · generatingReady
- Scheduled2 jobsDrafted · awaiting send windowReady
- Stuck jobs0 flaggedJobs not progressingReady
- Retrying0 jobsDelivery being retriedReady
- Failing1 receiptsDelivery failedBlocked
- Escalated0 jobsAwaiting human follow-upReady
Instruction pack freshness
Packs teach the runtime how to operate Daybreak. They stay stable; regeneration is only suggested on contract-level changes. Demo values.
1 pack(s) suggest regeneration
- Orchestrator Operating ManualStableRuntime-wide — Polling, claiming, and receipt rules unchangedReady
- Store Ops lane guidanceStableStore Ops lane (section of the Operating Manual) — Up to dateReady
- Executive Briefing lane guidanceReview suggestedExecutive Briefing lane (section of the Operating Manual) — Output format rules changed — regeneration suggestedWarning
- Labor Watch lane guidanceStableLabor Watch lane (section of the Operating Manual) — Up to dateReady
- Catering Program lane guidanceStableCatering Program lane (section of the Operating Manual) — Up to dateReady
- Regional Performance lane guidanceStableRegional Performance lane (section of the Operating Manual) — Up to dateReady
This is a mock operating-health view. Runtime connection, last poll, and instruction-pack freshness are demo values; every readiness state is derived from seeded company-map and briefing data. Daybreak does not draft or send briefings itself — the connected external runtime claims jobs from the queue and posts receipts back.