lucix — Email renders · the notification floor

1 · Ask-arrival

Render of T7. Provenance as the chain (noun-free), the exact ask, a way in, and the one-tap defer.

lucix <notify@lucix.app>now

An ask on APAC Launch — from Maya Chen

An ask

APAC Launch — a goal to get committed
owned by D. Okafor · run by Maya Chen
she's asking you — you own Data migration

Can Data migration commit to finishing by Mar 31?

Before you answer: Platform v2, which this depends on, is still open. If a real date isn't there yet, the honest move is a condition — not a guess.

Answer →

Not now — remind me Thu

This email is a copy of the ask — your answer lives on the record at lucix. You're getting it because you own a slice of APAC Launch. No one is chasing you; silence is a valid answer.

2 · Reminder

Class-3, chosen. Anchored to your own choice or the plan's date — never "someone is waiting on you." One-tap off.

lucix <notify@lucix.app>Mar 28

Your reminder — the APAC Launch ask

A reminder you set

You asked to be reminded about this near Mar 28 — and it's still open.

The ask
Can Data migration commit to finishing by Mar 31?

Answer →

Turn this reminder off

This is the one reminder you chose, on the date you chose. lucix never escalates and never chases — this won't come again unless a person writes to you.

3 · Event

Class-1, "something happened to your stuff." A record event on an object you own or authored.

lucix <notify@lucix.app>Yesterday

Something you named is now in the plan

On the record

The risk you named in October is now part of the committed plan.

“Platform v2 slips APAC to April.”

— your words, Oct 14

APAC Launch committed on Mar 31, and the thing you flagged is carried in it — visible to everyone who sees the plan.

See it on lucix →

You're getting this because you named this risk. It's a record event — nothing here needs doing.

What makes these the notification floor

Email-safe by construction. Table layout, inline styles on every element, a system font stack, and bulletproof (table-cell) buttons — no web fonts, no CSS classes, no JS. Signature Ledger colors are carried inline; the verbatim quote uses Georgia as the email-safe stand-in for Newsreader. Max ~600px.
Register is tightest here (§8.2). Zero internal vocabulary — no convening, cast, seal, reconcile. The ask-arrival is often a stranger's first-ever contact, so it shows the provenance chain ("run by Maya Chen · you own Data migration") without ever naming it "provenance".
The laws hold across the seam. The reminder is anchored to your own choice and the date — never "M. Chen is waiting on you" — and carries a one-tap off. Nothing escalates; every footer says silence is fine and no one is chasing you. Class-5 (auto-escalation, "3 items need attention") has no envelope to render.
Email is a copy, never the record. Every render says so — answers live on lucix; the email is the designed I/O, not the state (threads never become the record).
Class-2 forwardability: the runner's own clock email deliberately omits the seen-breakdown ("3 seen, 1 never opened") so a forwarded email can't leak engagement telemetry past the runner (§6.2 / DP-8).