Skip to content

Review related work together.

Choose the Matters a question depends on, inspect their relationship, and keep control of what changes.

The situation. Your launch scope and support preparation are separate pieces of work, but a decision in one raises a question for the other.

Step 1

Choose the scope.

Select which Matters to include. Add sources explicitly when the supported workflow allows them. The scope is visible before the question is sent.

Step 2

Read an answer with its basis.

Inspect the included Matter snapshots and source versions. The answer reflects those inputs at the time of the request; it is not a silent update of their current state.

Step 3

Decide what to do next.

The review changes neither Matter. If a change is needed, return to the relevant Matter and confirm it there.

Ask Vault

Selected Matters · 2

First-release scopeCurrent version 2
Support readinessCurrent s1

What still needs to happen before this release scope is ready?

Read-only answerAI wording · illustrative

The launch scope includes CSV and OFX, conditional on completed support instructions. Support readiness still records the import failure guide as incomplete. That support condition remains open.

This answer read: First-release scope · Current version 2; Support readiness · s1. No sources chosen. Neither Matter changed.

The answer names the two snapshots it read. Neither Matter has changed.

Power · Vault Control

Four kinds of work across Matters

Asking across Matters is one way in. You can also review a set of Matters, follow a known impact back to the Matter it affects, and keep doing this work over time. You always choose the scope.

Pre-release, shown with a synthetic example. Availability will be shown before it can be used.

Ask Vault

Ask a question over the Matters you select — one, several, or all you allow. Asking with a single selected Matter is still Ask Vault. Ask inside one Matter is part of both plans.

Vault Review

A review you start over a scope you set: what changed, what still applies, conditions and open questions, conflicts, and basis that may be out of date. An old date alone does not make something out of date.

Cross-Matter Impact

When a change you accepted touches a dependency you accepted earlier, Rodspan points to the exact Matter it may affect. A short list of possible impacts is not a search of everything.

More sustained work

More capacity to keep doing this work over time. Pricing describes the plans.

What every result tells you

The scope it covered, when it ran, and how much material it could use. Partly searched or unavailable material, too little to go on, or a cancelled review is stated as such. Nothing runs in the background over your chats or your Vault, and no relationships are invented.

In the example

One question, two Matters, and exactly what it read

Scope you selected · First-release scope and Support readiness

What still needs to happen before this release scope is ready?

Read-only answer · AI wording · illustrative

The launch scope includes CSV and OFX, conditional on completed support instructions. Support readiness still records the import failure guide as incomplete. That support condition remains open.

What this answer read when it was asked

First-release scope · Current version 2 · 2 items

Condition: Include CSV and OFX in the first release, provided the support instructions are completed first.

Open question: Do the support instructions cover import failures?

Support readiness · Current s1 · 1 item

Open item: The import failure guide is still incomplete.

Sources: none chosen, so the Release validation note was not read. History passages: none selected. Neither Matter was changed, and a later Current does not change this record.

From a finding to a change you confirm

  1. The review is read only. It finds that the support condition in First-release scope is still unmet.
  2. A possible impact names its exact target. It rests on a change you accepted and on the dependency you accepted before it: the condition “provided the support instructions are completed first.” Nothing is linked because it merely sounds similar.
  3. You decide in that Matter. A suggested change becomes Current only when you confirm it there. A new source version is not a Current change, and unknown owners or deadlines stay unknown.

A useful review can end with nothing kept. Sharing the result as a Published Brief is optional.

Plan context

Cross-Matter review and higher sustained intensity belong to Power. Pro remains a complete way to work within each of your Matters.

A read-only answer, a possible impact proposal and an accepted change are distinct. Only capabilities actually enabled and verified can be sold as available.