Lucid

The Language for Work

AI can do real work now. The hard part is trusting it with responsibility. Lucid files are how humans and AI agents collaborate on real work — written down, in plain language, on the record. And it takes minutes to learn: a handful of concepts, that's it.

Responsibility

One line: the outcome the file owns. It guides everything no routine covers.

Routines

The work that repeats: a name and numbered steps, in plain sentences. Say when it runs with a Schedule or a Trigger — or neither, and it runs when you ask.

A step opening with a keyword is a message to you — its own numbered step, every time. Action waits for you. Update arrives quietly. Alert interrupts you now. Everything else is simply done, in the log.

One owner per step: no mention means the Lucid bot; @Henry pauses the step for Henry.

Connections

What the file can see and touch. Naming one grants reading. can write grants changing — and every write comes to you first, until you loosen trust: ask me first, tell me after, freely. A routine with a Trigger watches its connections by itself.

Variables

Anything in brackets — the initial email — is a variable: its own little file holding exactly how that thing should be done, sitting next to the lucid file. Write one into a step, click it to edit it, and every run follows your version. If it doesn't exist yet, Lucid drafts it and asks you the questions that make it yours.

Two come built in:

Feedback

Your corrections, kept with the thing each one is about.

Taste

How you do everything, workspace-wide — everything outward-facing must fit it.

Entities

Lucid remembers the things it works with — a Ticket, a Client, an Invoice. Each gets a shared record, read before anything is raised: the same still-true thing never nags twice, and "what happened with SH31043289?" has an answer.

Off as a file's first line: defined, not running, until you switch it on.

Examples

Responsible for: outreach running and improving without me.

Routines:
  Draft the day's emails
    Schedule: every workday at 9
    1. Draft [the initial email] for each target due today.
    2. Action to review each draft.
  Handle replies
    Trigger: when a reply arrives
    1. Read the reply.
    2. Draft a response.
    3. @Henry decides whether it goes.
  Watch for replies
    1. Alert if a reply comes from anyone at GAC.

Connections:
  inbox
  email — can write, ask me first

Responsible for: knowing how bookings are going, without asking.

Routines:
  Daily bookings report
    Schedule: every day at 8
    1. Check the bookings table for bookings made today.
    2. Update me with how many and which clients.

Connections:
  supabase