Instruction Packs

The instruction pack. One stable operating manual that teaches the connected runtime how to use Daybreak — poll the queue, claim due jobs, fetch live context, work the job, and post receipts. Per-briefing detail (what, for whom, on what cadence) comes from Briefing Builder templates, due jobs, and the live company map — not from this pack.

• Connect once and work the entire queue continuously.
• Treat Daybreak's live API responses as the source of truth on every poll.
• Treat the lane guidance below as optional sections of this manual — they are operating focus, not separate 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.

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

• 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.

• 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.

# Orchestrator Operating Manual
Kind: Operating manual · Scope: Runtime-wide · Lane focus: All lanes · Runtime: Orchestrator runtime

## Purpose
The instruction pack. One stable operating manual that teaches the connected runtime how to use Daybreak — poll the queue, claim due jobs, fetch live context, work the job, and post receipts. Per-briefing detail (what, for whom, on what cadence) comes from Briefing Builder templates, due jobs, and the live company map — not from this pack.

## 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.