DaybreakInstruction Packs
orgdev-org
DU
AI RunnersInstruction Packs

Instruction Packs

The stable operating manual Daybreak hands an external orchestrator runtime so it can work the briefing queue. Runtime is not runner: one runtime hosts many runner profiles, and lane guidance is optional focus, not a separate pack per profile or per briefing type.

Copy manualExport

The Orchestrator Operating Manual is the instruction pack. It teaches the connected runtime how to use Daybreak — poll the queue, fetch live context, work the job, post receipts, and respect boundaries. Lane guidance below is optional operating focus for a runner profile, not a separate pack.

Per-briefing detail — what to draft, for whom, on which cadence, about which business objects — lives in Briefing Builder, due jobs, and the live company map. Adding a new briefing template (including niche briefings) does not require a new instruction pack or regeneration.

Lane guidance

Labor Watch lane guidance

Labor Watch lane (section of the Operating Manual) · Lane focus: Labor Watch · Owner Daybreak admin / leader · Orchestrator runtime

StableCopy

Purpose

Why this pack exists

Triggers labor exception insight routes when variance is elevated. This is optional operating focus for the Labor Watch lane the runtime hosts — a section of the Orchestrator Operating Manual, not a separate pack and not one pack per briefing type. Per-briefing detail still comes from Briefing Builder and the live queue.

  • Operate the Labor Watch lane the runtime hosts — a focus area, not a separate tool.
  • Inherit polling, claiming, output, and boundary rules from the Orchestrator Operating Manual above.
  • Resolve the 1 briefing template(s) currently routed to this lane from Briefing Builder and live queue context — never from this guidance.

Per-briefing detail lives outside this pack

Briefing Builder + live queue context, not new packs
  • New briefing templates — including niche briefings — are configured in Briefing Builder, not in this pack.
  • Per-briefing audience, business object, channel, and objective context is carried by due jobs and the live company map, fetched on every poll.
  • Adding, renaming, or removing a briefing template does not require regenerating this pack.

Live context to fetch

Fetched live from Daybreak each poll — never embedded in this pack
Fetch liveRecipients & rolesWho receives briefings and the responsibility each role implies.
Fetch liveGroups & departmentsGroup/department structure and membership for audience resolution.
Fetch liveBusiness objectsStores, regions, programs a briefing is about, with their data mappings.
Fetch liveObjectivesWhat the business is trying to improve, to frame relevance.
Fetch liveChannelsApproved delivery channels and destinations per recipient.
Fetch liveBriefing templatesWhat to generate, for whom, about what, in which format — owned by Briefing Builder.
Fetch liveRunner profilesThe lane this runtime is operating and its responsibilities.
Fetch liveCadences & windowsGeneration windows and delivery times that decide when work is due.
Fetch liveDue jobsThe concrete queue of work Daybreak has determined is due now.

Queue operating loop

Poll → claim → generate → schedule/send externally → post receipt
  1. PollAsk Daybreak for due jobs and scoped context on a simple cadence.
  2. ClaimClaim a due job so other workers do not double-process it.
  3. GenerateDraft the briefing from live context fetched from Daybreak — not from this pack.
  4. Schedule / send externallyDeliver or schedule through the approved external channel; Daybreak does not send.
  5. Post receiptReport what was drafted/sent/failed, to whom, when, and through which channel.

Output & receipt expectations

What the runtime reports back
  • Report the job, recipient, channel, runner profile, and runtime.
  • Report the outcome: drafted, scheduled, sent, failed, retrying, or escalated.
  • Include an external message reference when delivery occurred.
  • On failure, report the reason and retry/escalation state — do not silently drop work.

Boundaries

What the runtime must not assume Daybreak does
  • Daybreak does not run the AI model or generate the briefing itself.
  • Daybreak does not send or schedule the briefing through any channel.
  • Daybreak does not own OAuth or provider credentials — the runtime holds its own.
  • Daybreak does not hold the schedule or run a cron; due jobs come from the queue.
  • Daybreak does not store stale live truth inside this pack — fetch current context live each poll.
  • Each new briefing template is not a new instruction pack — Briefing Builder owns templates; this pack is the operating manual.

When to regenerate this pack

Stable by design — only operating-rule changes matter; new briefing templates do not

No regeneration needed for

  • A new briefing template is added in Briefing Builder (including niche briefings)
  • An existing briefing template is renamed, edited, or removed
  • Per-briefing recipients, business objects, channels, or objectives change
  • A new recipient is added or a group membership is set
  • An objective is renamed or its applies-to changes
  • A recipient email is updated
  • Normal cadence changes inside a template

Regeneration suggested when

  • Runner responsibilities or lane guidance change
  • Output format rules change (the contract for what a briefing should look like)
  • Receipt / logging contract changes
  • Polling or claiming behavior changes
  • Failure / retry policy changes
  • A new delivery channel type is added (e.g., chat alongside email)
  • A new data-access method is introduced
  • A major cadence strategy change

Manual preview

Copy/export-ready text — selectable; copy and export are not wired up yet
# Labor Watch lane guidance
Kind: Lane guidance · Scope: Labor Watch lane (section of the Operating Manual) · Lane focus: Labor Watch · Runtime: Orchestrator runtime

## Purpose
Triggers labor exception insight routes when variance is elevated. This is optional operating focus for the Labor Watch lane the runtime hosts — a section of the Orchestrator Operating Manual, not a separate pack and not one pack per briefing type. Per-briefing detail still comes from Briefing Builder and the live queue.

## Per-briefing detail lives outside this pack
- New briefing templates — including niche briefings — are configured in Briefing Builder, not in this pack.
- Per-briefing audience, business object, channel, and objective context is carried by due jobs and the live company map, fetched on every poll.
- Adding, renaming, or removing a briefing template does not require regenerating this pack.

## Fetch live context from Daybreak each poll (do not embed)
- Recipients & roles: Who receives briefings and the responsibility each role implies.
- Groups & departments: Group/department structure and membership for audience resolution.
- Business objects: Stores, regions, programs a briefing is about, with their data mappings.
- Objectives: What the business is trying to improve, to frame relevance.
- Channels: Approved delivery channels and destinations per recipient.
- Briefing templates: What to generate, for whom, about what, in which format — owned by Briefing Builder.
- Runner profiles: The lane this runtime is operating and its responsibilities.
- Cadences & windows: Generation windows and delivery times that decide when work is due.
- Due jobs: The concrete queue of work Daybreak has determined is due now.

## Queue operating loop
1. Poll — Ask Daybreak for due jobs and scoped context on a simple cadence.
2. Claim — Claim a due job so other workers do not double-process it.
3. Generate — Draft the briefing from live context fetched from Daybreak — not from this pack.
4. Schedule / send externally — Deliver or schedule through the approved external channel; Daybreak does not send.
5. Post receipt — Report what was drafted/sent/failed, to whom, when, and through which channel.

## Output & receipt expectations
- Report the job, recipient, channel, runner profile, and runtime.
- Report the outcome: drafted, scheduled, sent, failed, retrying, or escalated.
- Include an external message reference when delivery occurred.
- On failure, report the reason and retry/escalation state — do not silently drop work.

## Boundaries
- Daybreak does not run the AI model or generate the briefing itself.
- Daybreak does not send or schedule the briefing through any channel.
- Daybreak does not own OAuth or provider credentials — the runtime holds its own.
- Daybreak does not hold the schedule or run a cron; due jobs come from the queue.
- Daybreak does not store stale live truth inside this pack — fetch current context live each poll.
- Each new briefing template is not a new instruction pack — Briefing Builder owns templates; this pack is the operating manual.

## Regenerate this pack only when operating rules change
No regeneration needed for: A new briefing template is added in Briefing Builder (including niche briefings); An existing briefing template is renamed, edited, or removed; Per-briefing recipients, business objects, channels, or objectives change; A new recipient is added or a group membership is set; An objective is renamed or its applies-to changes; A recipient email is updated; Normal cadence changes inside a template.
Regeneration suggested when: Runner responsibilities or lane guidance change; Output format rules change (the contract for what a briefing should look like); Receipt / logging contract changes; Polling or claiming behavior changes; Failure / retry policy changes; A new delivery channel type is added (e.g., chat alongside email); A new data-access method is introduced; A major cadence strategy change.
DEMO DATA

This is a mock of the operating manual Daybreak would give an external runtime. Pack content and freshness are seeded demo values. Daybreak does not generate, send, or run anything itself — the connected runtime reads this manual, fetches live context from Daybreak, and works the queue.