Jared
Holds authority.
Nothing enters his diary without his say-so — including anything a company asks for.
Digiful · J.E Wallace Ltd · Unified Distributed Calendar
Who decides.
Who renders.
One calendar holds the truth. One database interprets it. Google Calendar decides what is real; Supabase works out what it means and shows each company only their own part of it. Nothing enters Jared's diary without his say-so.
Admin
Holds authority. Says yes or no. Jared.
Requester
Proposes only. Never writes. Company bookers.
Decide
Rules on what's booked and what's free. Google Calendar.
Render
Interprets and distributes. Decides nothing. Supabase.
01
Actions
How a commitment gets made — the write pathenters
Google Calendar app
He picks the company from a colour-coded calendar list — a choice, not a typed code. Works offline, on any device, in three taps.
Every other company's work is already on screen, in a different colour. The clash is visible before he taps save.
writes
Google Calendar
Single write-authority. The source of truth.
- Every commitment lands here first — Jared's and, later, the bookers'
- Rules on availability live, at the moment someone asks
- Six calendars, one account, colour-coded by company
If Google Calendar and Supabase ever disagree, Google Calendar wins.
Company bookers
ENWL · IES · IUS
They propose. They never write.
requests
Booking form
Asks Google Calendar live whether he's free, then offers the slot. No detail of anyone else's work is ever revealed — just yes or no.
proposes
One-tap approve
Jared's decision. Kept deliberately.
The admin is handed off. The judgement is not.
on approval
Why the approval tap stays. Being technically free is not the same as should say yes — and the gap between those two is the whole problem. The form removes the chasing, the phone calls and the diary admin. It does not remove Jared.
02
Reading
What each company sees — the read pathGoogle Calendar
The event now exists. It is real.
pushes
in seconds One way
in seconds One way
Supabase
Downstream. Reactive. Decides nothing.
- Holds the meaning — which company, which job, on site or paperwork
- Filters what each recipient is allowed to see
- Spots clashes and wrong-company entries, then tells Jared
- Keeps the history. Cancellations are marked, never destroyed
A mirror, not a master. It never writes back.
serves
Company calendar feed
Each company subscribes once, by secret link. Their own jobs appear in full. Everything else is a blank wall marked Busy.
Availability page
One link in his email signature. Live, always current, and completely blank — every busy block looks identical, whatever the reason.
Alerts to Jared
Two jobs clash. Wrong company picked. He gets told, and he decides. The system never blocks him.
The same week, seen three ways
This is the whole point. One diary — but no company can see another company's work.| What's in Jared's diary | ENWL sees | IES sees | IUS sees |
|---|---|---|---|
| Penrith 33kV switchingENWL · Tue 08:00–18:00 | Full detail | Busy | Busy |
| Carlisle site worksIES · Wed 09:00–17:00 | Busy | Full detail | Busy |
| Switch programme checkIUS · Thu 10:00–14:00 | Busy | Busy | Full detail |
| Family commitmentPrivate · Sat, all day | Busy | Busy | Busy |
↰
The loop closes back at Jared. Alerts return to him, not to a company — a clash, or a job filed against the wrong client. He gets a message and one tap to put it right. The system tells him. He decides. It never decides for him, and it never stops him.
- Drawing
- Calendar — Decide / Render
- Client
- J.E Wallace Ltd
- Revision
- A — 12 Jul 2026
- Status
- For review
- Phase 1
- Read-only distribution