Skip to content
Lemma

Lemma Help Center

Find the next step

Enter at least two characters

Search by the job or state you see.

Results are grouped by guide, so each article is one keyboard stop.

Truth and recovery

Execution evidence

Use the product layer and proof grade that describe what actually happened.

In this collection
On this page

Do not turn a Mission phase, approval, queue entry, or internal completion into a claim about LinkedIn.

Layer 1: Mission lifecycle

Public labels such as Needs input, Draft, Active or Live, Paused, Finishing, Completed, and Failed describe the Mission as a whole. A Mission can be Active or Live while some Sequences wait, fail, or finish.

Layer 2: Outbox Sequence

The public Sequence summary uses:

  • views: Open, Needs you, Finished;
  • Open facets: Ready, Scheduled, Waiting, Paused, Problems;
  • Finished outcomes: Completed, Replied, Opted out, Stopped.

These states summarize the Sequence. They are not direct evidence that each LinkedIn touch was sent.

Layer 3: Individual touch

Inside Planned touches, each touch has its own state, schedule or condition, Sender, message, and history.

  • A scheduled time is intent.
  • A sending or unresolved attempt is not safe to repeat blindly.
  • A failed task does not prove that LinkedIn accepted nothing.
  • A stopped or canceled future touch remains in history.

Layer 4: Provider confirmation

Use one of these for a past-tense delivery claim:

  • Provider confirmed in the Sequence touch history;
  • a Provider confirmed entry in the Audit log with a provider receipt.

The UI can explicitly say Marked complete without provider confirmation. Treat that as unconfirmed, not sent.

Approval evidence

Approval permits a specific scope to progress. It is not an external action.

  • Lemma-led Mission approval is a choice and request in the Mission conversation.
  • Validate sequence in Outbox approves and freezes the current bodies of one eligible Lemma-authored Sequence; Batch validate applies the same boundary to eligible selections or a Mission.
  • Manual Launch commits the exact wizard Review and queues approved work.
  • A later material change may produce a new revision or require a new decision.

Safe language

Use:

  • “prepared” for content or a plan;
  • “approved” for the reviewed permission;
  • “scheduled” for a future time;
  • “waiting” for a condition;
  • “problem” for a blocked or failed Sequence;
  • “provider-confirmed” when the receipt exists.
When evidence conflicts

Preserve the most specific external evidence. Do not retry or rewrite history while provider confirmation is unresolved. Escalate with the Sequence and Audit entries.

Next action

Open Use the Audit log or Resolve a Sequence problem.