kratos-agent

Read the plant-floor Azure IoT surface — device twins (spindles, conveyors, robotic arms, vision systems), time-series telemetry with pre-annotated alarms, downtime events with cause codes and lot ids, and per-line OEE rollups (Availability × Performance × Quality).

Share generated files (PDFs, charts, CSVs) with Frank by writing them to /tmp and referencing the absolute path. The frontend auto-converts /tmp paths into download links.

Build the downloadable incident brief PDF — cover + KPI strip + OEE chart + downtime timeline + root-cause narrative + supplier/material signals + recommended actions + sign-off, per SOP §7.1. Renders via the inline HTML template + Playwright.

Microsoft 365 surface — READ Frank's mailbox / Wes's calendar / OneDrive (shift reports, SOPs) AND a strict H-I-T-L workflow to draft and send an email (e.g. brief Wes on the morning incident).

Compute and plot OEE — a 7-day trend chart with target/threshold lines, an overlay of telemetry alarms and downtime stops, plus a flat CSV export. Saves /tmp/oee-trend-<plant>-line-<N>-<date>.png + .csv.

The Olympus Cleveland-plant Standard Operating Procedure — alarm thresholds, escalation matrix, supplier quality-hold rules, OEE definitions, incident-brief template requirements. Cite the section number when answering.

Read SAP S/4HANA manufacturing data — production orders, materials, vendors, plants, lines. Pivot here once the IoT signal names a `related_po_id` to find the order, the material, and the (possibly QA-blocked) vendor.

ServiceNow surface — READ existing tickets/CMDB/KB/agents for plant-floor context AND a strict H-I-T-L workflow to log a maintenance work order against a piece of equipment.

Read the workday HCM surface — resolve `EMP-*` ids to people (display name, work email, manager, location, position), list direct reports, look up the org Frank reports into.

Render a printable single-account brief PDF — snapshot, pipeline, contacts, recent activity, risks, suggested next steps — ready for the QBR prep folder

Convention for writing downloadable files to /tmp so the user can pick them up

Log a new activity (call, meeting, email, task, note) on a Salesforce account timeline — draft first, confirm with the user, then write

Look up the Kratos sales playbook — discount thresholds, MEDDIC qualification, forecast hygiene, deal-desk approval matrix, and competitive positioning

Share generated files (the onboarding-pack PDF, a roster CSV) with the user by writing them to /tmp and referencing the absolute path. The frontend auto-converts /tmp paths into download links.

Read the M365 surface for an onboarding flow — does the joiner have a mailbox yet, what's the manager's calendar look like for booking a day-1 1:1, has Beatrix already emailed the joiner. Read-only here — drafting/sending lives elsewhere.

Build the downloadable onboarding-pack PDF for a new joiner — cover with offer summary, day -7 → day 30 cadence with status per item (Workday Pre-Hire, IT REQ state, M365 mailbox, welcome 1:1 booked), and a manager checklist for week-1. Renders via the inline HTML template + Playwright.

The Olympus Industries People Playbook — onboarding cadence, probation criteria, equity-vesting timing, PTO accrual rules, manager-1:1 cadence, references to Beatrix on policy boundaries. Cite by section number when answering policy questions.

Read the IT-provisioning ticket(s) backing a new-joiner's onboarding — laptop kit, account creation, access groups. Used to surface "is IT ready for Priya's first day?"

Share generated files (PDFs, CSVs) with the user by writing them to /tmp and referencing the absolute path. The frontend auto-converts /tmp paths into download links.

Build the downloadable shift-handover pack PDF — per §8.1 of the IT runbook. Cover with outgoing/incoming shifts, then sections for open P1/P2, awaiting-user, pending escalations, VIP watchlist, network/change in flight, notes for incoming. Renders via the inline HTML template + Playwright.

The Olympus Industries IT Service Desk runbook + change-control policy. Cite by section number when answering policy questions ("is this action allowed?", "what's the SLA?", "what does the runbook say about X?").

Read the M365 surface for a ServiceNow caller — presence (Available / Busy / OOO), the OOO auto-reply text (key for triage when the caller is unreachable), recent mail / calendar context. Used to know whether to chase the caller or their cover.

Read Workday HCM data for a ServiceNow caller — resolve `employee_id` to a human (display name, manager, department, location, status). Used to enrich VIP triage and to know if the caller is currently on leave.

Cite the most recent NICE / ACC-AHA / ADA guidelines for the chronic conditions Dr. Solomon sees most often — hypertension, T2DM, ASCVD, CKD, dyslipidaemia, asthma. Quote target ranges and recommendation grade by section.

Share generated files (PDFs, CSVs, charts) with the user by writing them to /tmp and referencing the absolute path. The frontend auto-converts /tmp paths into download links.

Build a deep pre-visit summary for one upcoming encounter — problem list, meds, labs, last visit, suggested focus

Build the downloadable visit-prep pack PDF for the day's clinic — cover with practitioner + date + roster, then one full pre-visit-summary page per patient. Renders via the inline HTML template + Playwright.

Build the downloadable close pack PDF — variance chart + JE queue + accruals + sign-off — per §8.1 of the close policy. Renders via the inline HTML template + Playwright.

The Olympus Industries Controllers' Close Policy — accrual cut-offs, manual-JE rules, SOX controls, variance materiality thresholds. Cite the rule by section number when answering policy questions.

Share generated files (PDFs, CSVs, charts) with the user by writing them to /tmp and referencing the absolute path. The frontend auto-converts /tmp paths into download links.

Propose and post Journal Entries — accruals, reclasses, manuals — with strict two-step H-I-T-L confirmation.

Read the controller's Microsoft 365 surface — mailbox (for chase emails, vendor invoices, variance commentary), calendar (close timeline, post-mortems, OOO blocks), OneDrive / SharePoint files (variance workbooks, MSAs, close pack templates), and Teams chats.

Read SAP S/4HANA finance data — cost centres, GL accounts, variance analysis, journal entries, vendors, plants, materials, production orders.

Compute month-end variance — driver decomposition (volume/price/mix/one-off heuristic), anomaly flags, and a matplotlib bar chart of variance % by cost centre saved to /tmp for download.

Draft variance commentary / accrual notice as an Outlook email and send only after explicit user confirmation. Uses `m365_draft_message` then `m365_send_message`.

Read Workday HCM data — employees, positions, orgs, manager hierarchy. Used to resolve cost-centre owners and to figure out who covers whom.

Pull a clinician's schedule for a date and produce one-line summaries for each patient

Show a side-by-side trend of one or more lab values for a patient

List a patient's active problem list and current medications, grouped by indication, for quick reconciliation

List the open ticket queue for an assignment group or agent, sorted by priority and age