How it works — the daily cycle and the session loop

ONCE A DAY

Verified before anyone builds.

Work arrives from everywhere — a Slack thread, a meeting, a ticket, an error spike — gathered through your agent's own MCP connections. Before any of it reaches a human, read-only verification goes and looks at the actual code and answers one question: is this still true, and is it actually not done?

The SF Recall daily cycle, drawn end to end: a Slack thread, a Linear ticket and a Sentry spike are fetched by your own agent over your own MCP connections — no vendor credential exists inside SF Recall — gathered into one de-duplicated queue, then verified against your actual code, read-only, with verdicts DONE, PARTIAL, MISSING or DISCUSSION, before any of it reaches the board a human decides from. Approved work is dispatched as a packet (the item, its verify evidence, the relevant memories) to your own agent, the outcome is recorded, and a shipped outcome closes the attention item that carried the work. Footer evidence from one real morning: 42 items gathered — 11 DONE, 15 PARTIAL, 14 MISSING, 2 DISCUSSION. The 11 were already live; verify stopped a second build.

The verdict grammar — DONE, PARTIAL, MISSING, DISCUSSION — is lifted verbatim from the runs SaaS Factory does on itself. And a MISSING claimed while part of the workspace was unreachable is downgraded to DISCUSSION at the door: an admitted gap, never a confident guess.

EVERY SESSION

The loop, four moves.

01 — STANDUP
Open by reading, not guessing
The session starts with what still governs: standing decisions, open attention items, the last handover — ranked by the files you are about to touch.
02 — DEPOSIT
Write it down when it happens
Decisions are deposited the moment they are made — because the end of a session often never arrives. A near-duplicate is refused: supersede the old answer instead of stacking a new one on it.
03 — DIARY
The diary is written during
A running narrative of the session, written as it unfolds, so a session that dies mid-thought has already told the next one what it was doing.
04 — HANDOVER
Leave the next session its start
The close names what was finished, what was not, and what to watch — and every unfinished thing becomes an attention item that reappears at every standup until someone closes it.

> standup { focus: branch + changed paths }

3 standing decisions govern this area

1 open attention item: refresh path never ran live

> saveMemory { room: "decisions", summary, why }

stored — one live answer per question

> diary { narrative, keyFindings }

diary saved — findings: 2

> handoff { done, notDone, watchOut }

attention item opened: migration not yet applied

WHEN A SESSION DIES

Died mid-thought? Nothing's lost.

The conversation itself is gone — a dead session is not resumable, and we do not pretend it is. But the diary was written during the session, the unfinished business is already an attention item, and the raw transcript synced as it went. The next standup opens with all of it.

THE WIPED LAPTOP

Wipe it. Re-clone. Log in.

The workspace binding is a small file committed to the repository, so a fresh clone already knows where its memory lives. Reinstall, log in, and the new machine answers from the server: every conversation including subagents, every memory with its provenance, every diary, every attention item, the knowledge graph — even the sync watermark, so months of history are never re-uploaded or skipped.

What a wipe really destroys Uncommitted work — it was never anywhere but that disk. SF Recall is not a backup tool, and we will not describe it as one.
The local install: recovery is really wipe, re-clone, reinstall, log in — the credential is the one thing a wipe legitimately revokes.
Third-party content past its retention window — the work items and decisions derived from it persist; the source text ages out.

The next session already knows.

Create your workspace

Verify first. Remember everything.

Verified before anyone builds.

The loop, four moves.

Open by reading, not guessing

Write it down when it happens

The diary is written during

Leave the next session its start

Died mid-thought? Nothing's lost.

Wipe it. Re-clone. Log in.

The next session already knows.

Verify first. Remember everything.

Verified before anyone builds.

The loop, four moves.

Open by reading, not guessing

Write it down when it happens

The diary is written during

Leave the next session its start

Died mid-thought? Nothing's lost.

The next session already knows.

Wipe it. Re-clone. Log in.