Skip to content
On this pageWithin a Matter

One piece of work, with room to keep thinking.

Ask your question and talk it through. Explore other directions when that helps, and keep only what you choose. Keeping nothing is a complete result too.

  • One Matter can hold several independent conversations. A new conversation does not read earlier chats unless you choose material from them.
  • Current holds only what you confirm: a judgment, a condition, an open question, or possibilities that are still competing.
  • There is no structure to set up or maintain before you start.

Product preview with synthetic examples. Rodspan is not open to the public yet.

Show how conversations, Current and originals fit together (figure)

Matter

First-release scope

One piece of work

Conversations

Room to explore. Nothing in them becomes Current on its own.

CSV and OFX release scope

Launch messaging for import support

Revising the release condition

Current

Chosen by you for future conversations.

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

Do the support instructions cover import failures?

Original material and history

Separate and inspectable within supported coverage.

Release validation note · version 1, version 2

History · conversations and key changes

Earlier version of the launch condition

A Matter keeps related work together. Conversations give you room to explore. Current is the material you have chosen for future conversations. Original material and history remain separate and inspectable within their supported coverage.

Think in more than one direction.

A tentative idea is allowed to stay tentative. Explore two launch scopes, compare two drafts, or keep a question open. You decide whether anything is worth carrying forward.

OutcomeUseful discussion, even with nothing kept.

Show the figure: exploring two directions without committing

Conversation

CSV and OFX release scope

Should the first release support CSV only, or CSV and OFX?

CSV first

CSV first keeps the initial validation scope smaller.

AI wording · illustrative

CSV and OFX

CSV and OFX together covers more import cases, but the OFX path still needs validation.

AI wording · illustrative
Current0

Nothing is Current yet. Neither direction is Current.

Two directions inside one conversation. Nothing has been made Current.

Continue from what you chose.

Keep a condition, a working decision or an unresolved question when it will help the next conversation. Start a new conversation with those chosen inputs, rather than treating every earlier suggestion as settled.

OutcomeA clear starting point, with room for a new line of thought.

See the work across conversations.

Keep development and launch messaging in separate conversations within the same Matter. History brings their entries and confirmed changes into one place, including conversations where nothing was kept. Open the original conversation when you need it.

History records the work; Current contains what you chose to carry forward. Filing a conversation does not adopt its content or automatically feed its transcript into another one.

Show the figure: a new conversation starting from chosen material

Matter

First-release scope

History

All · Conversations · Key changes

Conversation

CSV and OFX release scope

Started Oct 9 · Last activity Oct 9

Open

Conversation

Launch messaging for import support

Started Oct 13 · Last activity Oct 13

Open

Made current · version 1 · Oct 9

Wording at that change

Start with CSV. Reconsider OFX after its validation is complete.

Current2

Start with CSV. Reconsider OFX after its validation is complete.

Your words

Do the support instructions cover import failures?

Open questionYour words

New conversation

Starts from Current · 2 chosen items. The other conversation is not an input.

History lists both conversations and the confirmed change. Current holds what was chosen for the next discussion.

Return to the material behind an idea.

Inspect the original passage and its exact version. Keep a quotation, your own wording and an AI interpretation distinguishable—even if you decide to use the interpretation.

OutcomeA way to inspect what a statement came from.

Show the figure: the original passage and its exact version

Find

In this Matter, by meaning

why did we leave OFX out?Find by meaning

Matched message · CSV and OFX release scope · turn 2 · reply · revision 1

AI wording · illustrative

CSV and OFX together covers more import cases, but the OFX path still needs validation.

OpenUse as input
A found passage keeps its conversation, turn, author and revision. Using it as input is a separate choice.

Let a judgment evolve without losing its history.

A condition may change while the broader question stays the same. Revisit the earlier reasoning, correct the part that no longer holds, and leave the unresolved parts open. Source changes and AI suggestions do not silently rewrite what you chose.

OutcomeA revised starting point and a visible route back to the earlier one.

Show the figure: revising a judgment while its history stays

Release validation note

Version 1 → Version 2 · synthetic source

Version 1

CSV validation is complete. OFX validation is incomplete. The import failure guide is still incomplete.

Version 2

CSV and OFX validation are complete. The import failure guide is still incomplete.

Current2version 2

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

Corrected · version 2Confirmed by you

Earlier version · version 1

Start with CSV. Reconsider OFX after its validation is complete.

Do the support instructions cover import failures?

Open question · unchanged
Version 2 of the source changes one condition. The correction is confirmed by you; the earlier version stays readable.

Inspect the relationship between Matters.

Ask This Matter inspects one chosen Matter. Ask Vault lets eligible users review an explicitly selected scope across Matters. The answer is read-only; changing something returns to a concrete Matter and requires your confirmation.

OutcomeA view across related work without merging it or silently propagating changes.

Review, a possible impact proposal and an accepted change are different things. Availability depends on the product capability and plan actually enabled.

Show the figure: the relationship between two Matters

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.

Two selected Matters, one read-only answer, and the snapshots it read.

Two levels of control

Matter Control and Vault Control

Both include the complete way of working inside your Matters. Vault Control adds work across Matters, always within a scope you select.

In short: Pro includes complete work within each Matter. Power includes that same foundation, plus Vault Control across the Matters you select.

Planned product, shown with synthetic examples. Plans and limits are described on Pricing.

In both: complete work in a Matter

  • Several Matters, and several independent conversations in one Matter.
  • Free exploration, keeping all, some or none of it.
  • A Current that changes only when you confirm or revise it, with History and the basis each answer used.
  • Finding original passages by meaning in supported material, and locating them across your Vault where you allow it.
  • Ask and Update within a Matter.
  • Sources kept as originals with their versions, updated when you choose.
  • Basic notices about dependencies you have recorded, and a few well-founded suggestions.
  • The same privacy, exact citations, human confirmation, data rights and answer quality.

Finding, tracing sources, sharing, export and security are not held back for Vault Control.

Vault Control adds work across Matters

Ask Vault

Ask across the scope you select: one Matter, several, or all the Matters you allow. “All” is a scope you choose. It does not read your whole chat history, scan in the background or merge Matters. Matter Control still includes Ask within a Matter.

Vault Review

A review you start, over a scope you set. It looks at what changed, what still applies, conflicts, basis that may be out of date, and conditions or open items that are still pending. Connections you had not recorded are found only inside a review like this.

Cross-Matter Impact

When a dependency you recorded is affected, Rodspan points you back to the specific Matter. It does not add links on its own or pass changes along. You decide there whether Current changes.

More sustained work

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

Findings and suggestions are read-only. A change to Current always happens in the specific Matter, with your confirmation.

The four Power additions, in the launch example

Illustrative and synthetic. Each part shows only what it says: an Ask answer is not a completed review, and a suggested relationship is not an accepted dependency.

See the four additions in the launch example

  1. 1 · Ask Vault

    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.

    Read: First-release scope, Current version 2, and Support readiness, Current s1. Sources: none chosen. Asking with one selected Matter is still Ask Vault, separate from Ask within a Matter.

    Select the Matters and ask in the example

  2. 2 · Vault Review

    Illustrative result · a review you start over the scope you choose

    Changed
    Release validation note, version 2: CSV and OFX validation are complete.
    Still applies
    Include CSV and OFX in the first release, provided the support instructions are completed first.
    Still open
    Do the support instructions cover import failures?
    Possibly outdated basis
    An earlier saved answer used version 1 of the note.
    Conflicts and coverage
    Conflicts are listed with both sides when a review finds them. The result states which Matters it covered and any partial or unavailable material.

  3. 3 · Cross-Matter Impact

    An explanatory sequence, not a live record

    1. Suggested relationship. A review suggests that the launch condition depends on support preparation. It stays a suggestion until you accept it.
    2. Accepted dependency. If you accept it, it is recorded as a dependency.
    3. After a change you accept to the support guide, Rodspan points to the exact target: First-release scope, the condition.
    4. You decide there whether Current changes. Nothing is adopted, passed along or changed automatically.

  4. 4 · More sustained capacity

    For keeping this kind of work going: reviewing a changing set of Matters again, asking across larger selections, and following up after changes.

    Limits are not published yet.

    See how the plans differ

Pro keeps complete work in each Matter, including Ask within a Matter and basic notices for dependencies you recorded.

Optional delivery

Share a selected snapshot as a frozen brief.

Illustrative result · synthetic content · First-release import scope · Brief v1

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

Open question, still open. Do the support instructions cover import failures?

Release validation note · version 2. “CSV and OFX validation are complete. The import failure guide is still incomplete.”

A selected snapshot can include work that is still open.

Read the complete example brief

A Published Brief is optional. No conversation has to end with one, and it is not limited to Vault Control. You choose and confirm what to share, and the recipient reads a fixed copy without an account.

  1. 1 · You choose what to share

    Select positions, open questions and sources, then confirm them.

  2. 2 · Preview, then create a frozen version

    Set the title, the publisher name and an optional note, then check the preview. Creating the brief freezes it as a version, such as Brief v1. Later changes to your work do not change it.

  3. 3 · The recipient reads it

    No account is needed. They see only what you selected.

  4. 4 · They can try Rodspan

    The brief ends with a short note and a link to the example, if they want it.

Open the complete example brief, as the recipient sees it

Example brief · synthetic content · what the recipient sees

Published Brief

First-release import scope

Brief v1 · Published Oct 17, 2026

Shared by Dana Okafor

Publisher’s note

For discussion of launch preparation.

Positions

Condition

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

Publisher’s wording · approved Oct 16, 2026

Source: Release validation note, version 2

Open

Open question

Do the support instructions cover import failures?

Publisher’s wording · recorded as open Oct 9, 2026

Sources

Release validation note · version 2

CSV and OFX validation are complete. The import failure guide is still incomplete.

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

About this brief

This is Brief v1, a fixed copy published Oct 17, 2026. It contains only what the publisher selected, and later changes to their work do not change it. A new version would have a new link.

The positions come from version 2 of the publisher’s current positions. Approval records the publisher’s choice. It does not mean the work is done or that a position has been independently checked.

The name Dana Okafor was added by the publisher. Rodspan does not verify it.

Made with Rodspan

Keep important work moving across AI conversations.

Try an example

Ways to deliver it

  • A web page, like the example here.
  • Page images: PNG pages laid out for reading on a phone.
  • Copy text: the same content as plain text.
  • Print, from the browser.

Versions and links

  • Brief v1 was made from Current version 2. If Current changes later, this brief stays as it is. A new brief version would get its own link.
  • One brief version can have more than one link, and each link can be revoked. Existing links stay valid unless you revoke them.
  • Revoking a link cannot recall a copy someone has already downloaded.
  • Making page images does not create or publish a new version.

What is shared, and what is not

  • Only the sources and quotations you allow, with their names and versions.
  • No whole chats, private links or private identities. The publisher name is shown as you wrote it.
  • The default link preview shows no private title or text.
  • Claims, conditions, both sides of a conflict, source names, versions and quotations are kept whole in every format.
  • Copy text has no ads.
  • A revoked link cannot come back.
  • Exporting a web page, page images, copy text or a print does not create a new brief version or sharing link.

This is a read-only example. Publishing is not available in this preview.

Six examples

One way of working, six kinds of work.

Each example is synthetic and has its own state. Open one to explore, then return to all six. Nothing is saved or sent.

Choose an example to explore

Try it yourself

The short guided example takes three steps: discuss, choose if useful, and continue. Learn also has eight separate task examples you can open in any order. None of them is required.

Prepared demo · not live AI · no account needed