Symbol Docs
Features

Dependency review

How Symbol flags the capsules that link to a capsule that changed, and how you clear them.

When you link one capsule to another, the first one relies on the second. If the capsule you link to changes, Symbol flags yours as Needs review, so a change in one place is never left silently contradicting another. The flag stays until you update the capsule or confirm it is still valid.

This works the same in the web app, the mobile and desktop apps, your AI assistant through MCP, Symbol Bridge and the Symbol CLI.

There is nothing to set up. Any way you link a capsule makes it something yours relies on:

  • a mention in the body, by number or by alias (@notes/3 or @notes/launch-plan),
  • a pointer mention (~@notes/3),
  • a value in a reference field,
  • a mention inside a paragraph field, when the Type shows paragraphs as markdown,
  • a reference in a log entry: the log it belongs to is the capsule that relies on it.

Linking to the same capsule several times counts once. A capsule that mentions itself does not flag itself.

What counts as a change

A capsule changes, and flags the capsules that link to it, when what it says changes:

  • its title, its body, its field values or the values its body fills in,
  • its files: adding, removing, renaming or rotating one,
  • for a log, adding, editing, deleting or restoring an entry,
  • for a capsule whose body comes from its Type's template, an edit to that template, and for a capsule with field values, an edit to its Type's fields,
  • moving it to another Type, and turning end-to-end encryption on or off.

The rule is exact: any change to the text counts, even one space. These do not count, so they never flag anything: editing only the summary, the alias, the tags or the project, archiving or restoring, how it looks when shared, saving without changing anything, and reviewing it.

One step at a time

Only the capsules that link directly to the one that changed are flagged. If B links to A and C links to B, a change to A flags B, not C. When you then update B, its own change flags C. Confirming B still valid changes nothing in B, so it flags nothing further.

Why a capsule is stale

A capsule can be stale for more than one reason at once, and it always says which:

  • Not updated in a while: its Type marks capsules stale after a number of days, and it has not been updated in that time. This works exactly as before.
  • A capsule it links to changed: it names each capsule that changed since this one was last reviewed or updated. A capsule that changed but that you cannot read is counted, never named.
  • Linked code changed: for a skill, a file it relies on in a folder linked from GitHub changed since the skill was last published or confirmed. See GitHub linked code.

A capsule whose summary is older than its body keeps its own separate notice; that is not a reason to be stale.

In lists you can show capsules that are stale for any reason, or only those that need review because something they link to changed. A capsule stays flagged across sessions and devices until it is cleared, so unfinished reviews are easy to pick up later.

Clearing a review

There are two ways to clear it.

  • Update the capsule. An edit that changes what it says clears every change it was saved against. Editing only its summary or tags, or saving it unchanged, does not.
  • Confirm it is still valid. Choose Still valid and write a short note on what you checked (up to 500 characters). The note is kept with who confirmed it and when.

Clearing a review is not an edit: it does not change the capsule, make a revision, or reset how long ago it was updated. If it was also stale for its age, it stays stale for its age until you update it.

If the capsule it links to changes again later, it is flagged again.

Read it before you confirm

Still valid is accepted only after you have read the current version of the capsule in full, after the change that flagged it. Opening the capsule is that read. A list, a search result, a preview or a summary is not.

  • Each full read gives your account a receipt for that exact version. Confirming sends it back.
  • A receipt works once, for 24 hours, for your account on the device or connection that read it.
  • If the capsule or anything it links to changes after your read, the receipt no longer works: read it again, then confirm.
  • The receipt shows that the current text was delivered to you, the same as any read. It cannot show that it was understood.

AI assistants follow the same rule: your assistant gets a receipt only from a full read of the capsule, and passes it with its note when it confirms the capsule still valid (the confirm_capsule_validity tool).

What your AI sees when it edits

When your AI assistant updates a capsule, the result says what changed (the fields, and a short summary of the body changes when it can be read) and lists the capsules that link to it, so it can check them next. It lists only the capsules you can read.

Who can do what

  • Anyone who can read a capsule sees why it is stale. Only the capsules they can read are named.
  • Confirming it still valid needs edit access to the capsule, the same as editing it.
  • A shared public page may show that a capsule might be out of date, but never which capsules it links to, nor any review note.
  • Your review notes and the record of what you confirmed are included when you export your data.

Turning it off

Dependency review is on for every account. You can turn it off with the Dependency review switch in your account settings, or ask your AI assistant (the manage_dependency_review_setting tool), or run symbol settings dependency-review off in the CLI.

Turning it off affects only your account, everywhere you use Symbol: your capsules are no longer shown as needing review, and edits no longer list who relies on them. Staleness for age and the summary notice keep working. Nobody else's reviews change, and Symbol keeps track of what still needs review, so when you turn it back on your outstanding reviews come back.

Local copies and offline use

Symbol Bridge and the desktop app can answer reads from a local copy. A read from a local copy that is up to date gets a receipt from Symbol, so you can confirm from it. A copy that has not yet synced the change still opens, but it cannot confirm until it is current. Offline, you can read every capsule as usual, and confirming waits until you are back online.

Encrypted capsules

Symbol cannot read the links inside an end-to-end encrypted capsule, so an encrypted capsule is never flagged for review. An encrypted capsule that changes still flags the plain capsules that link to it.

On this page