RFCs and postmortems that read like they matter

A postmortem is an act of care. It should look like one.

# Gravity helps the medicine go down

Dense engineering documents earn trust through restraint. A postmortem set in a quiet serif, at a measured line length, with no chrome shouting for attention, gets read to the end. One that arrives as an unformatted wall gets skimmed — and skimming is how the same incident happens twice.

lucid.page gives these documents the weight they carry: headings with anchors your reviewers can link to, tables that stay legible, and block quotes that let a timeline speak for itself:

14:32 — Connection pool saturation begins. Retries amplify load.

14:41 — Failover initiated. Service restored at 14:47.

# Diagrams where the argument happens

Incidents and designs are structural; prose alone can’t carry them. Mermaid fences render as diagrams inline, next to the paragraph that argues about them:

sequenceDiagram
  participant Client
  participant API
  Client->>API: POST /orders
  API-->>Client: 502 Bad Gateway
  Note over API: Pool exhausted, retries amplify

# Share exactly as widely as you mean to

Not every document is for everyone. Pages are unlisted by default — visible to whoever holds the link, invisible to everyone else. With an account, a page can be fully private, gated to your session. And when a draft is only meant to be true until Friday, you can set it to expire.

# Decide, revise, restore

An RFC is a record of a decision, and decisions evolve. Every revision is kept: you can restore any earlier version, and links into specific sections keep working as long as the headings do.

# Common questions

# Who can see a page I publish?

Unlisted pages are reachable only by people you give the link to — they are not indexed anywhere public. With an account you can also mark a page private, so reading it requires your session.

# Can a page expire automatically?

Yes. Set an expiry when publishing and the page takes itself down on schedule — useful for time-boxed drafts and review copies.

# What happens to older versions when I edit?

Every update is stored as a revision. You can browse the history and restore any earlier version; nothing is silently overwritten.