Skip to content

See your week across every layer

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. Proven against quoxcli 0.5.0 on 2026-11-08.

What does my week look like?

Ask for one merged view of every calendar layer, then ask whether anything clashes. Then check the layers yourself.

What you get: one view of the week across your own events, team schedules and workflow cron, which layers it covered, and whether anything is double-booked.

Ask in plain words:

quox · talking to Quox

Show me my merged Quox calendar across every layer for this week, and tell me which layers it covered.

▤ AOCL │ L1 identity complete · allowed · 0ms

▤ AOCL │ L3 policy gate complete · proceed · 4ms

◐ CALENDAR │ overlay ✔ CALENDAR │ overlay │ 3 layers, 7 occurrences, 1794143108693 generatedAt · 8.1s

⛓ AEE │ envelope opened · ops.tool · calendar_overlay ok

⛓ AEE │ envelope opened · stream_success

Your merged calendar for 8 to 14 November 2026 (UTC) has seven entries, and all of them
are automated workflow runs. There are no human events.

The window starts today, Sunday. If you meant the week that began Monday 2 November,
tell me and I'll rerun it.

Layers covered

Layer                │ Coverage        │ Entries
─────────────────────┼─────────────────┼────────
My events (personal) │ Complete, empty │ 0
Team schedules (org) │ Complete, empty │ 0
Workflow cron (org)  │ Complete        │ 7

I didn't check a provider calendar such as Google or Outlook. The layer list for this
view contained only these three layers.

What's scheduled

Workflow  wf-1793804026088-kk3usv  (trigger t1) runs once a day at 03:17 UTC. The seven
runs fall on 8, 9, 10, 11, 12, 13 and 14 November. Today's run at 03:17 has already
passed. None of them block time on your calendar.

You have no meetings or personal commitments this week. Your two empty layers reported
complete, so that is a confirmed empty, not missing data.

24.9s · 1 tool · 0 approvals

A real turn on our own install (CLI 0.5.0, 8 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 8 Nov 2026 · test report mw7uh1

Then ask whether anything overlaps:

quox · talking to Quox

Am I double-booked anywhere on my calendar? Check for clashes.

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 7ms

◐ CALENDAR │ clashes ✔ CALENDAR │ clashes │ 0 clashes · 1.8s

⛓ AEE │ envelope opened · ops.tool · calendar_clashes ok

⛓ AEE │ envelope opened · stream_success

No clashes turned up for 8 to 14 November (UTC).

That is thinner than it sounds, though. My own events and the team schedules came back
empty, and only the workflow cron layer reported as complete. Cron firings never count
as clashes, so the result mostly means there are no human commitments on this calendar
to overlap. No provider calendar, such as Google or Outlook, appeared in what I checked.

If you expect meetings to be there, the likely cause is that a calendar isn't connected.
I can list your calendar layers to confirm, or check a different date range.

13.3s · 1 tool · 0 approvals

A real turn on our own install (CLI 0.5.0, 8 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 8 Nov 2026 · test report mw7uhy

Quox merged every visible layer into one week and said how complete each layer was. An empty layer that reports complete is a real empty week, not missing data, and Quox kept the two apart. The clash check skips workflow cron, because a machine schedule never blocks your time. Both asks only read, so nothing was created or changed.

layers
quox calendar layersLayer              Kind               Name              Visible    Scopeinternal_events    internal_events    My events         yes        userteam_schedules     team_schedules     Team schedules    yes        orgworkflow_cron      workflow_cron      Workflow cron     yes        org
From a real run on our own install.

quox calendar status shows the connected provider calendars and their sync watermark. With a provider connected, quox calendar agenda --connection <id> shows that calendar’s agenda and how complete it is, and quox calendar coverage --connection <id> shows just the freshness.

The merged week and the clash check are asks today: the CLI reads the layers and each connection, and Quox puts them together.