# Plans, drafts, invitations, and confirmation

The most important safety distinction in Domino is the difference between preparing a social action and causing it to reach another person.

## Idea versus plan

An idea is something worth considering. A plan is the structured object that can carry timing, place, audience, invitation, RSVP, and lifecycle state.

Liking an idea does not create a plan. Creating a plan draft does not invite anyone.

## Draft

A draft is private, reviewable work. A user or authorized assistant can revise the people, place, title, date, time, and other plan details before publishing.

If a draft is saved, it can appear in **My Dominos**. Say “draft saved,” not “invitation sent.”

## Preview and prepare

A preview presents what the action would do. A prepared action binds the exact reviewed effect, actor, surface, relevant object revision, recipients or destination, expiry, and other safety state.

Preparation is a stop. It is not implied approval.

## Publish, send, and share

Publishing a plan can create invitations. Delivery depends on the recipient:

- eligible Domino recipients may receive Domino's supported delivery;
- typed-name or other manual-share recipients can require the host to share the returned link themselves.

A “share link” result means the link exists. It does not prove that another person received it.

## Confirmation by surface

### Web

The user confirms through the visible review and publish/send control. The page should show what happened and whether any recipients still require manual sharing.

### SMS

Only a current eligible confirmation contract plus an entire trimmed message equal to `SEND` can authorize the prepared external send. “Yes,” “send it,” `SEND!`, or extra words do not count.

### MCP and API

The caller prepares the exact action, presents it to the user, stops, obtains a later explicit approval, and commits the prepared handle from the same principal and surface. Never tell an MCP or API caller to use the SMS reply contract.

## RSVP

An RSVP belongs to a specific invitation. A person can accept or decline through the supported invitation surface. Domino may ask which invitation the person means when a terse response is ambiguous.

## Edits and cancellation

A plan can have different editability depending on its lifecycle. A meaningful edit after invitations exist may require updated communication or a new safety check. Cancellation is distinct from deleting a private draft.

## LLM answering guidance

- Use an effect ladder: **read → draft → preview/prepare → commit/send**.
- State the current rung and what remains before another person is affected.
- Do not collapse publishing, automated delivery, and manual link sharing into one claim.
- Do not claim success until the returned Domino outcome is terminal and supports that claim.