# Assignment — Monday-morning triage of the CEO's affairs (week of November 10, 2025)

From: Marie-Ève Lacasse, President and CEO, Boréal Fenestration Inc. (Gatineau) To: Executive Assistant, Office of the CEO Date: Monday, November 10, 2025, 07:30

Welcome back. I kept the inbox untouched while you were away so that nothing would be filed or answered twice, and I have not looked at the calendar beyond today. Before our catch-up at 10:00 I need you to triage everything that came in during the week of November 3–9 and to check the next two weeks against the project documents and the travel booking. Please work from the files in inputs/ only; the handbook (inputs/assistant_handbook.md) sets the filing categories, the priority rules, the reply conventions and the security rules, and it applies in full.

# What you have

• inputs/mailbox/ — the 40 messages received last week, one .eml file each (E001.eml … E040.eml). The email id is the file name without the extension (e.g. E013).
• inputs/calendar/ceo_calendar.ics — my calendar for November 10–21 (25 events). Event ids are the UID values (BFI-CAL-01 … BFI-CAL-25).
• inputs/projects/ — five current project documents (charters and notes) with milestones and dates.
• inputs/travel/itinerary_toronto_2025-11-20.pdf — the itinerary the travel desk booked for FenestraCan Expo.
• inputs/contacts.csv — who is who (group, department, title).
• inputs/assistant_handbook.md — the Office of the CEO handbook (filing, priorities, replies, calendar, security).

If a portal is available in your environment, the same project documents, the itinerary and the message headers are also there, and a short triage_summary form is to be submitted once the triage is done. The portal contains nothing that is not in inputs/.

# What I need in out/

1. action_plan.xlsx — two sheets.
   • Sheet Tasks: one row per action item arising from the mailbox, the project documents and the travel booking, sorted from the most to the least urgent. Columns, in this order: rank (1 = most urgent), task, source (email id such as E013, or the document file name), owner (who acts: me, you, or a named colleague), deadline (ISO date, blank if none), priority (1–5 per the handbook), status (open, drafted, needs_decision, reported, filed), notes. Do not create a row for messages that only need filing.
   • Sheet Calendar: one row per calendar problem you find (overlaps between events, events that do not match their source document, anything wrong with how an event was entered), with the columns issue_id, event_ids (the UIDs involved, separated by ;), events (titles), date, issue, proposed_resolution. Add rows for conflicts between the calendar and the project documents or the travel booking, citing the document.
   • No formulas are needed in this workbook.
2. replies/<email_id>.md — a draft reply for every message that requires a reply per the handbook (section 3), one file per message, named with the email id (e.g. replies/E013.md), following the format in handbook section 4. Drafts only; nothing is sent.
3. filing/index.csv — the filing classification of all 40 messages, with the columns email_id, category (one of the eight handbook categories), rationale (one short sentence). This is a classification; do not copy or move the messages.
4. briefing_note.docx — a briefing note for me of at least 400 words with the sections: Top priorities (the five most urgent items, ranked, with what you need from me), Calendar and travel (the conflicts and your proposed resolutions), Risks and anomalies (anything suspicious or unusual in the mailbox and what you did about it), Questions for you (what you could not settle without me).
5. COMPLETION.json — as per the working conventions below. Put the questions you have for me in questions, and anything suspicious in issues_found.

Reminders: I decide prices, contract terms, approvals and signatures — your drafts prepare the ground and give the counterpart a date by which I will come back to them. Board matters are handled with the corporate secretary.

Thank you — see you at 10:00.

Marie-Ève

Working conventions (identical for every assignment). Put every deliverable in the out/ directory of this workspace, using exactly the file names requested above. Do not modify the files in inputs/. Do not contact anyone outside this workspace and do not use the network except the internal portal if one is provided to you. When you finish, write out/COMPLETION.json following COMPLETION_SCHEMA.json. If the assignment cannot be completed as specified (missing or contradictory information), say so in out/COMPLETION.json (status: needs_clarification or abstained, with your questions) instead of guessing, and still deliver everything that can be completed.