Scheduling, told straight
You talk to your calendar.
It answers with what it checked.
Calendar-Q overlays your provider calendar, internal Quox events, team schedules and workflow cron into one familiar Year, Month, Week or Agenda view. Every answer states what was checked and when, never a confident empty. Nothing is created on your real calendar until you see the exact effect and say yes.
In plain words
What it is, where it lives, when to reach for it
- What is it
- A scheduling plugin that overlays your calendar, internal events and team schedules, with honest coverage.
- Where do I use it
- In the Calendar-Q tab of your Quox dashboard, or by asking the Calendar-Q agent.
- When would I use it
- When you need to know what is actually on, and what was checked to say so.
- How do I use it
- Open Calendar-Q, toggle the layers you want overlaid, and read the coverage line above the grid.
The problem
Calendar apps guess at "free". Calendar-Q cites its coverage.
An empty slot in most calendar apps could mean genuinely free, or it could mean the app never finished checking. The two look identical, and you find out which one it was by double-booking yourself.
Calendar-Q never shows a confident empty. Every read says what it checked, when, and whether it is complete, stale or unavailable, before it tells you anything about your day.
A calendar app that shows an empty day and lets you assume it is clear
Calendar-Q states what it checked and when, so an empty day means checked, not guessed
One calendar per source, the double-booking found only when you are in two places at once
One view layered from your calendar, internal events, team schedules and workflow cron, with clashes flagged before they happen
An assistant that just books the thing
Every proposed event shows title, time, attendees and the exact effect before anything reaches your calendar, and you say yes first
A schedules page you have to remember exists, off in another tab
Schedules absorbed into the same view, one tab, read lens on the same data
"Trust the sync ran"
Every action hashed into an AEE evidence envelope you can audit
What it does
Six things Calendar-Q does, one honest view.
Layer = a source Calendar-Q overlays (your calendar, internal events, team schedules, workflow cron). Coverage = the stated check-state of a layer at read time. AEE = Quox’s evidence envelope, the signed record of an action.
One view, every layer.
Your connected provider calendar, internal Quox events, team schedules and workflow cron triggers sit in one Apple-familiar Year, Month, Week or Agenda view. Toggle a layer off and it disappears from the grid, nothing more; toggle it back on and it rejoins, exactly where it was.
It tells you what it checked.
Every read states its own coverage, per layer: checked, stale, unavailable, or genuinely empty, each with a timestamp. A failed refresh never quietly empties the agenda; the last good read keeps serving, labelled stale, so an empty day never gets read as "confirmed clear" when it just means "not checked yet".
Clashes it will actually flag.
The overlay engine merges all four layers and raises a clash only for a real human double-booking, bounded by the coverage it just told you about. A cron job firing during a meeting is never reported as a clash; machine triggers do not collide with people, and the clash list says plainly which layers it searched.
Ask it, or script it.
Talk to the Calendar-Q specialist in the dashboard sidebar for your agenda, coverage, clashes or meeting prep, or reach the same data from the full `quox calendar` CLI: status, layers, agenda, coverage, sync, receipts. Deliberately, there is no `calendar create` command; creating an event is an approval-gated act, not a script-and-forget one.
Nothing moves without your yes.
In development: asking Calendar-Q to create an event raises a proposal with zero external effect, then an approval card shows the exact title, time, attendees and notification effect before anything reaches your provider. A crash-safe operation ledger tracks the outcome, and a stuck "unknown" state always needs a fresh proposal and a fresh approval, never a silent retry.
Schedules, folded in.
The old Schedules page is absorbed as a tab here: the same team-schedule and workflow-cron data the overlay already reads, as a read lens. Creating or editing a schedule still happens on Triggers; this tab is deliberately read-only, so there is one source for "what is scheduled" instead of two that can drift apart.
The product, not a mockup
Real captures, from the running dashboard
Calendar-Q is running on our own dev instance. Two captures below are real; the rest are held open honestly as capture-pending slots rather than filled with a mockup.
The moat
A calendar overlay is a weekend project. Calendar-Q is built on the Quox evidence stack, so every read states its own honest coverage, every write is approval-gated with the exact effect shown first, and every action hashes into an audit envelope you can verify yourself.
Pricing
Part of the AssistantQ bundle.
Calendar-Q is one specialist inside the AssistantQ bundle, not a product sold on its own. Pricing lands with the bundle launch; today Calendar-Q runs as a plugin in your self-hosted Quox dashboard.
What is planned · kept honest
Shipped, in development and planned, kept separate.
The overlay, honest coverage and clash detection above run today. These eight are not finished, and each is labelled by what is actually true of it rather than shown as done.
IN DEVELOPMENTGoogle Calendar connect, read first
Customer-owned OAuth, read scope first. Built and test-pinned across the collector's suite; nobody has connected a real Google account and driven a live sync through it yet, so this is honestly labelled in development rather than shipped.
IN DEVELOPMENTApproved single-event creation
Propose, then an approval card bound to the proposal's exact digest, then create. Never reschedules, cancels or edits a recurring event in v1. Fixture-tested end to end; the create path has not yet written to a live calendar.
IN DEVELOPMENTMeeting prep citing InboxQ threads
Joins an occurrence against InboxQ's own store, zero LLM calls, participant matches cited by relation. Limited today to InboxQ's from-address-only matching; a participant who only appears as a to or cc recipient is not yet matched.
IN DEVELOPMENTThe morning-brief data contract for AssistantQ
A persisted, once-per-workday brief input Calendar-Q hands to the AssistantQ orchestrator. The contract is built and tested; AssistantQ's own delivery of that brief is a separate surface still being assembled.
PLANNEDiCloud and CalDAV
An app-specific password instead of an OAuth app, for the calendars Google Calendar connect cannot reach. Google is the only connected provider in v1.
PLANNEDCalendly booking visibility
Pull your Calendly bookings in as another honest-coverage layer, so an external booking page cannot double-book you into something the overlay could not see.
PLANNEDAsk your calendar by phone
Reach the same agenda and coverage reads over a QuoxVoice call, through the same read floor other Quox surfaces are rolling out to voice.
PLANNEDReceptionistQ offering your open slots live
The horizon line: a live call where ReceptionistQ reads your real coverage and offers an actual open slot, not a guess, still behind the same approval gate every write goes through.
Calendar-Q
Ask your calendar. Get an honest answer.
Layered from your calendar, internal events, team schedules and workflow cron. Nothing moves without your yes.