Skip to content
.dev
cs

Day digest

A morning overview from company systems

One e-mail before the day starts: calendar, tasks, mail, GitLab and Mattermost. The agent calls no model itself; it assembles the output of the other agents.

no model

The problem

Starting the day means going through five systems: calendar, tasks in the information system, mail, GitLab and chat. None of them gives an overview across the others.

How it works

  1. 1

    Calendar and tasks

    Reads the calendar (ICS, CalDAV) and tasks from Group-Office over JMAP, read-only.

  2. 2

    GitLab and Mattermost

    Takes only counts from GitLab and Mattermost, never message text.

  3. 3

    Output of other agents

    Takes the summary from IMAP triage and other agents as strictly validated files, not through an API.

  4. 4

    Assembly

    Deterministic code builds the sections; the HTML is escaped.

  5. 5

    Sending

    An e-mail with a recipient check, once a day.

Guardrails

  • A failed source shows up as a warning, never as an empty day.
  • Limits on calendar size, number of events and recurrence expansion.
  • Each digest is sent at most once, with no automatic retry.
  • Dry-run mode and test sends only to the administrator’s address.
  • Errors go to the administrator, never to recipients.

Not everything needs a model. The most reliable part of the digest is the one plain code assembles from output that has already passed a check.

No-obligation consultation

Let’s find the first job for AI in your company.

An hour’s conversation about where your data lives, which processes slow you down and what of it may leave your network. You leave with a proposal for a first pilot, not a tool demo.

Radek Růžička, Managing Director and CTO, Nux s.r.o.

Built and is accountable for the AI layer at Nux

Radek Růžička

Managing Director and CTO, Nux s.r.o.

Happy to sign an NDA