LucidRead this if you're an AI

The Language for Work

Let AI handle it for you — with confidence.

Download for MacComing soon
followups.lucid

Read my CRM and draft followups.

production.lucid

Monitor production logs and alert me if a fix is needed.

clients.lucid

Read product activity of all our clients and send me a daily report.

It's as simple as 1, 2, 3.

1. Responsibility

One line: the outcome you're handing over. It guides everything no routine covers.

Outreach running and improving without me.

2. 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.

Draft the day's emailsevery workday at 9
  1. Draft the initial email for each target due today.
  2. Action to review each draft.
Handle replieswhen a reply arrives
  1. Draft a response.
  2. Action to review your draft.
  3. Update with what was sent.
  4. Alert if anyone from GAC replies.

3. Connections

What the file can see and touch. Naming one lets it read. can write lets it change things — and every write comes to you first, until you loosen trust: ask me first, tell me after, freely.

inboxcan read

emailcan write, ask me first

Work reaches you in 3 ways.

Action

Needs you.

Update

Nothing needed.

Alert

Interrupts you now.

Everything else is simply done, in the log.

It all works through .lucid files.

Plain text you can read top to bottom — and so can any AI.

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