Connect · your calendars, on your terms
One list over both calendars.
Excluded means never asked.
LumenQube merges Google Calendar and Outlook into a single fortnight and stops there — the providers keep the schedule, because they are better at holding it. What LumenQube owns is the part they cannot give you: which calendars, and which events, the rest of your workspace is allowed to read.
A view, not a second calendar
Google Calendar and Outlook already do scheduling well, and they hold the record. Rebuilding them here would make LumenQube responsible for a schedule it does not own, so it does not try — and the screen is smaller and clearer for it.
What it does
- Merges Google Calendar and Outlook into one list, ordered by when things actually start.
- Shows the next fourteen days, grouped by day, in your own time zone — including all-day events, which the two providers describe differently.
- Names the account on every row. Two calendars merge here, and a row you cannot place is a row you cannot act on.
- Opens any event in the calendar it came from, where changing it actually changes something.
- Lets you take a calendar — or one event — out of context. That is the rest of this page.
What it deliberately does not
- No month grid. A fortnight is the window that answers what is coming; a month is a filing cabinet.
- No drag‑to‑reschedule. Moving a meeting belongs where the invitations are sent from.
- No create‑event form on this screen. You can still ask the assistant to book something.
- It does not claim your provider forgets anything. Excluding a calendar changes what LumenQube may read; Google and Microsoft still hold the event.
Where “excluded” actually happens
Most software spells exclusion as a display filter: fetch everything, then hide the row. That is a preference, not a privacy control — the data still arrived. Here is the order LumenQube runs in, and the two points where a control cuts into it.
-
Something needs your schedule
You open Today, or ask the assistant about your week, or an automation comes due. All three arrive at the same place, because there is only one path to a calendar in this app.
-
Per‑calendar exclusion
LumenQube works out which calendars this call may touch
An excluded calendar is removed here — before a token is spent, before a request exists. Naming one explicitly does not get it back: an account hint can narrow what a call may touch and can never widen it, so asking about “my Outlook calendar” while Outlook is excluded returns nothing from Outlook rather than quietly re‑admitting it.
-
The request goes out
Only to whatever survived the step above. If nothing did, no request is made at all — and the assistant is told your calendars are excluded, rather than telling you to connect a calendar you can see is already connected.
-
Per‑event exclusion
Events come back, and excluded ones are dropped
This one is a filter, and we would rather say so than round it up. A single event can only be recognised once the list has arrived, so an excluded event is fetched and then discarded. A whole calendar can be stopped before the request; one event inside it cannot. They are two controls because they act at two different moments, and collapsing them into one word would misdescribe both.
-
What is left is what anything can see
Today, this screen, search and the assistant all read the same filtered list. There is no second route that reaches a calendar without passing through the two cuts above.
What exclusion reaches
The standard the screen is built to: an excluded calendar must be invisible to Today, to search, and to every calendar tool the assistant has. If it only hides the row, it is a lie.
| An excluded calendar | An excluded event | |
|---|---|---|
| Today | Never requested | Dropped before display |
| This calendar screen | Listed, so you can include it again | Listed by id, so you can include it again |
| Asking the assistant about your week | Never requested | Dropped before the model sees it |
| Checking whether you are free | Never requested | Free/busy carries no event list |
| Booking a new event | Refused — excluded is not writable either | Not applicable |
| Replying to an invitation | Never requested | Refused, by id, even from an old link |
A control you can see, and undo
A control whose result is invisible is a control nobody can reverse. Four small decisions on this screen exist for that reason alone.
- Excluded, in words
Each calendar says what its state means for the app, not for the screen: “LumenQube does not read this calendar, and the assistant cannot see it” — rather than a switch position you have to interpret.
- Excluded events stay listed
Underneath your fortnight, by id. The title was never stored — keeping one would mean keeping a copy of the thing you hid — so the id is all there is to show, and it is enough to put the event back.
- “Nothing on” and “all excluded” are different screens
Exclude every calendar and the page says so. Being told your fortnight is clear, seconds after hiding it yourself, reads as a broken control rather than a quiet week.
- Including it again re‑fetches
Because nothing was kept. While a calendar is excluded its events are never requested, so putting it back has to go and get them — there is no cached copy sitting behind the control.
What is being built next
Calendar is one surface of a longer plan. The honest state of the rest, so you can decide whether to wait.
- NextMeetings that produce work
A meeting the workspace understands as one object — prep before it, notes beside the transcript, and decisions that carry the point in the recording they came from. Today a recording and its transcript attach to a note, and the calendar event beside them is a separate thing.
- ThenMemory & Context you can govern
One screen for everything the workspace remembers, not just calendars: what is stored, where, what the AI may touch — and a Forget that removes it rather than hiding it. The per‑calendar control on this page is the shape the rest will take.
- ThenA preview of what is about to be sent
Before a cloud request runs, the exact context pack it would carry — itemised, and refusable. The privacy receipt on the homepage shows this after the fact; the goal is to show it first.
No dates, deliberately. We would rather tell you the order than a quarter we would have to quietly change.
Questions
Which calendars can I connect?
Google Calendar and Outlook. Both are connected with your own account, you see the scope you grant, and either can be disconnected without touching the other. There is no LumenQube calendar behind them — the events you see are the ones sitting in your provider right now.
Does excluding a calendar delete anything?
No. It changes what LumenQube may read. The events stay exactly where they are, in Google or Microsoft, and the exclusion can be lifted at any time — at which point the events are fetched again, because none were kept while it was off.
How far ahead does it look?
Fourteen days. Today renders only the current day, and both screens are served by the same fetch — a second request for the same fortnight is how two views end up disagreeing about the same meeting.
Can the assistant read my calendar without being asked?
It reads the calendar when your request needs it — asking about your week is a request that needs it. What it can never do is reach a calendar you have excluded: that decision is applied when the call is being planned, not when the answer is being written. Anything that leaves your machine passes an approval gate first.
What happens if one of my calendars is unreachable?
You see the one that answered, with the failure named beside it — the provider, and the way to fix it. One calendar being down is a degraded day, not a broken app, so it is not styled as one and it does not blank the events that did arrive. A refresh that fails leaves the last good answer on screen rather than replacing it with an error.
The rest of the day surface
Today — what the day needs from youConnect — 108 apps, on your termsKnow — find your own pastHow the connections are secured