Pro
Matter Control. The complete way to work within each of your Matters. The default way to start.
$29 per month
Founding price: $25 per month
Annual, not open yet: $290 per year · Founding $250
Pro is the complete way to work within your Matters. Power adds work across Matters and more capacity to keep that work going.
Pre-release plan preview. Public access and purchasing are not open yet. These are current working prices, not an offer you can buy today.
Matter Control. The complete way to work within each of your Matters. The default way to start.
$29 per month
Founding price: $25 per month
Annual, not open yet: $290 per year · Founding $250
Everything in Pro, plus Vault Control across Matters and more sustained capacity. Not a smarter or safer model.
$99 per month
Founding price: $79 per month
Annual, not open yet: $990 per year · Founding $790
Prices in USD. These are working prices for the pre-release plan. The final offer, including Founding terms, will be published before anything can be bought.
When one piece of work depends on another. In the example, the launch scope depends on support preparation:
Work in Matters and conversations
Several Matters, and several independent conversations in a Matter. A useful discussion can end with nothing kept and no change to Current.
Pro
Included
Power
Included
Current, confirmed by you
Judgments, conditions, open questions and competing possibilities. You select, edit, confirm, correct, withdraw and restore them, with their origin. AI and source updates never change Current silently.
Pro
Included
Power
Included
Exploration
Explore other directions and keep all, some or none. Suggestions can be checked and edited, and become Current only when you confirm.
Pro
Included
Power
Included
History and continuing
Independent conversations with their originals and versions. Old answers keep their old basis. A new conversation starts from Current and the inputs you choose, not from every earlier chat.
Pro
Included
Power
Included
Find originals
Find original passages by meaning, with context and version, and locate originals across your Vault where you allow it.
Pro
Included
Power
Included
Ask and Update in a Matter
Complete work inside a Matter. This is separate from Ask Vault.
Pro
Included
Power
Included
Sources
Originals with versions, refreshed when you choose. Supported formats and limits are those open at launch; not every format, file size, scan or link is supported.
Pro
Included
Power
Included
Dependency notices and suggestions
Basic notices about dependencies you recorded, and a few suggestions you can adopt. Not an automatic cleanup queue.
Pro
Included
Power
Included
Published Brief
Web page, page images, copy text and browser print, read without an account. Opening it publicly has its own conditions.
Pro
Included
Power
Included
Quality, privacy and rights
The same standards for quality, privacy, security, sources and data rights. Deeper reply modes follow their own conditions and appear only when they are ready. Power does not buy a smarter or safer model.
Pro
Same
Power
Same
Ask Vault
A read-only answer with its basis, over a scope you choose: one Matter, several, or all you allow. It does not scan all your chats.
Pro
Ask within a Matter
Power
Included
Vault Review
A bounded review you start: what changed, what still applies, conditions and open questions, conflicts, basis that may be out of date, source versions, and how much it covered. An old date alone does not mean out of date.
Pro
Not included
Power
Included
Cross-Matter Impact
Bounded impact analysis across Matters. Possible links found in a review are suggestions with source, target, version, reason and uncertainty. Follow-up after an accepted change uses only dependencies you accepted before it. You decide in the target Matter.
Pro
Basic notices for recorded dependencies
Power
Included
Sustained capacity
More frequent and larger-scope work over time. No multiplier or message count has been set.
Pro
Complete, with a finite included amount
Power
Higher
Monthly price
USD, pre-release working prices. Not on sale yet.
Pro
$29 · Founding $25
Power
$99 · Founding $79
Annual price
Working prices. Annual billing is not open yet.
Pro
$290 · Founding $250
Power
$990 · Founding $790
Included usage and capacity
Exact included amounts, and capacity for Matters, files, storage and brief delivery, are not published yet. Large operations show their scope first. There are no automatic overage charges.
Pro
To be confirmed before purchase
Power
To be confirmed before purchase
Trial
Planned: 14 days, limited. No card and no automatic charge. One total allowance that does not refill daily, for features that are actually open. When the time or the allowance runs out, new AI work pauses and your work stays readable. Browsing the synthetic example does not start it, and paying is a separate, explicit purchase.
Pro
Planned
Power
Planned
Cancel, downgrade and data
If you cancel, downgrade or run out of allowance, your content, History, read-only inspection, export, deletion and other controls stay available. Your data is never held back to make you pay.
Pro
Same
Power
Same
Founding prices of $25 for Pro and $79 for Power per month are part of the pre-release plan. Who qualifies, how long the price continues, what happens if you cancel and subscribe again, and annual eligibility will be published with the final offer. The number of Founding places has not been set.
An optional way to share a selected, frozen snapshot of your work, which can include open questions. You select and confirm what to share, and Rodspan freezes it as a brief version. The recipient reads it without an account, sees its positions, conditions, open questions and sources, and can try the example to learn what Rodspan is.
A workspace for ongoing work with AI
Talk a problem through with AI. If part of the discussion will matter later, you choose it. Next time, a new conversation starts from what you chose, not from everything that was said.
The guide is a prepared demo in three short steps, with no account needed. The film shows a different example.
Discuss
Should the first release support CSV only, or CSV and OFX?
AI wording · illustrative
CSV first keeps the initial validation scope smaller.
CSV and OFX together covers more import cases, but the OFX path still needs validation.
Nothing is Current yet.
Choose, if useful
Start with CSV. Reconsider OFX after its validation is complete.
Condition · confirmed by you
Do the support instructions cover import failures?
Open question · confirmed by you
Only what you confirm is carried forward. Keeping nothing is fine too.
Continue
Later · a new conversation starts from Current · 2 chosen items
How should we describe import support at launch?
It starts from what you chose, not from the whole earlier chat.
Explore more than one direction. Keep only what you want to carry forward. Then begin a new conversation with that chosen starting point.
An illustrative example of the way of working. The film follows a writing project; the interactive example follows a product launch.
1 · Explore
Try another approach, question an assumption, or leave something unresolved. A conversation can be useful even when you keep nothing from it.
Matter · First-release scope
ConversationCSV and OFX release scope
Illustrative example · synthetic content
Should the first release support CSV only, or CSV and OFX?
CSV first
CSV first keeps the initial validation scope smaller.
CSV and OFX
CSV and OFX together covers more import cases, but the OFX path still needs validation.
Nothing is Current yet. Neither direction is Current.
2 · Return
One project, different conversations, a history you can return to.
Bring the decisions, conditions and open questions you chose into a new conversation. Spend less time piecing together what you meant to carry forward.
Matter
First-release scope
Illustrative example · synthetic content
History
Conversations
CSV and OFX release scope
Started Oct 9 · Last activity Oct 9
Launch messaging for import support
Started Oct 13 · Last activity Oct 13
Key change
Made current · version 1 · Oct 9
Wording at that change
Start with CSV. Reconsider OFX after its validation is complete.
Start with CSV. Reconsider OFX after its validation is complete.
Condition · version 1
Do the support instructions cover import failures?
Open question
New conversation
Starts from Current · 2 chosen items
The other conversation is not an input.
3 · Change
When the situation changes, revisit the condition behind your earlier choice. Update what you want to use now, while keeping the earlier wording and its source available to inspect.
Matter
First-release scope
Illustrative example · synthetic content
Current · version 1
Start with CSV. Reconsider OFX after its validation is complete.
Release validation note · version 2
Version 1
OFX validation is incomplete.
Version 2Changed
CSV and OFX validation are complete.
Reading version 2 does not change Current.
Version 1 · synthetic source
CSV validation is complete. OFX validation is incomplete. The import failure guide is still incomplete.
Version 2 · synthetic source
CSV and OFX validation are complete. The import failure guide is still incomplete.
Current · version 2 · 2 items
Include CSV and OFX in the first release, provided the support instructions are completed first.
Made current · version 1 · Oct 9
Start with CSV. Reconsider OFX after its validation is complete.
Corrected · version 2 · Oct 16 · Confirmed by you
Include CSV and OFX in the first release, provided the support instructions are completed first.
Earlier versions remain distinguishable.
Unchanged in both versions
Do the support instructions cover import failures?
Release validation note · version 1 and version 2Unchanged
The import failure guide is still incomplete.
Look for a passage, inspect its exact wording and version, and decide whether to use it in your next question. Finding something does not automatically make it part of the answer.
When a question spans more than one Matter, choose which ones to review together. Inspect the answer and its basis before deciding whether anything should change.
What was discussed. What you chose. What remains open. What a source actually said. Rodspan keeps these distinctions visible as the work develops.
Work through one launch project across a few conversations.
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.
Product preview with synthetic examples. Rodspan is not open to the public yet.
Matter
First-release scope
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 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.
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.
CSV and OFX
CSV and OFX together covers more import cases, but the OFX path still needs validation.
Nothing is Current yet. Neither direction is Current.
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.
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.
Matter
First-release scope
History
All · Conversations · Key changes
Conversation
CSV and OFX release scope
Started Oct 9 · Last activity Oct 9
Conversation
Launch messaging for import support
Started Oct 13 · Last activity Oct 13
Made current · version 1 · Oct 9
Wording at that change
Start with CSV. Reconsider OFX after its validation is complete.
Start with CSV. Reconsider OFX after its validation is complete.
Do the support instructions cover import failures?
New conversation
Starts from Current · 2 chosen items. The other conversation is not an input.
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.
Find
In this Matter, by meaning
Matched message · CSV and OFX release scope · turn 2 · reply · revision 1
CSV and OFX together covers more import cases, but the OFX path still needs validation.
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.
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.
Include CSV and OFX in the first release, provided the support instructions are completed first.
Earlier version · version 1
Start with CSV. Reconsider OFX after its validation is complete.
Do the support instructions cover import failures?
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.
Ask Vault
Selected Matters · 2
What still needs to happen before this release scope is ready?
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 levels of 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.
Finding, tracing sources, sharing, export and security are not held back for Vault Control.
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.
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.
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 example2 · Vault Review
Illustrative result · a review you start over the scope you choose
3 · Cross-Matter Impact
An explanatory sequence, not a live record
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 differPro keeps complete work in each Matter, including Ask within a Matter and basic notices for dependencies you recorded.
Optional delivery
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 briefA 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 · You choose what to share
Select positions, open questions and sources, then confirm them.
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 · The recipient reads it
No account is needed. They see only what you selected.
4 · They can try Rodspan
The brief ends with a short note and a link to the example, if they want it.
Example brief · synthetic content · what the recipient sees
This is a read-only example. Publishing is not available in this preview.
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
Explore freely now, carry forward what matters, and revise it when the situation changes.
One piece of work, over time
Start by asking. No import, categories or structure are needed first, and nothing has to be Current. Explore freely, choose what to carry forward if anything, come back to it later, and revise it when something changes.
Situation
You have two plausible ways forward and want to understand both before committing.
Open another line of thought, question an assumption or leave the outcome unresolved. Keeping nothing is a valid result. The discussion is not automatically promoted into Current.
ResultYou have learned more without having to turn the conversation into a decision log.
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.
CSV and OFX
CSV and OFX together covers more import cases, but the OFX path still needs validation.
Nothing is Current yet. Neither direction is Current.
Situation
The discussion helped, and part of it may matter next time.
You choose all, some or none of what was discussed. A suggested wording is a draft you can edit. It becomes Current only when you confirm it. Keeping nothing is a complete result.
ResultNext time starts from what you chose, not from everything that was said.
Situation
You return after a few days and need to get back to the work.
The question, chosen conditions and unresolved items provide a starting point for a new conversation. Add an exact source or passage when you need it. Other discussion stays separate unless you explicitly choose it as an input.
ResultLess work reconstructing what you meant to carry forward.
Matter
First-release scope
History
All · Conversations · Key changes
Conversation
CSV and OFX release scope
Started Oct 9 · Last activity Oct 9
Conversation
Launch messaging for import support
Started Oct 13 · Last activity Oct 13
Made current · version 1 · Oct 9
Wording at that change
Start with CSV. Reconsider OFX after its validation is complete.
Start with CSV. Reconsider OFX after its validation is complete.
Do the support instructions cover import failures?
New conversation
Starts from Current · 2 chosen items. The other conversation is not an input.
Use the conversation’s association control or Add an existing conversation in History. Review its title, original-question excerpt, date and present Matter before choosing it. You can preview the original conversation. Titles need not be unique; the actual conversation identity determines what is added.
Add a conversation to First-release scope
CloseChoose a conversation to file here. Open shows the original and changes nothing.
Conversation
Launch messaging for import support
“How should we describe import support at launch?” · Started Oct 12 · Not in a Matter
Conversation
Launch messaging for import support
“What should the release note say about OFX?” · Started Oct 11 · In Support readiness
Two conversations can share a title. Each row is a separate conversation.
Moving a conversation from another Matter is shown as an explicit move, with both Matters named. Its past answers and what they were based on stay as they were.
Situation
A condition behind your earlier choice is no longer the same.
Inspect what changed, compare it with the earlier basis, and confirm the correction you want. Keep the remaining conditions and open questions visible. The earlier version remains a separate part of the record.
ResultA current view you can use, with a route back to why it changed.
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.
Include CSV and OFX in the first release, provided the support instructions are completed first.
Earlier version · version 1
Start with CSV. Reconsider OFX after its validation is complete.
Do the support instructions cover import failures?
Current and History stay separate, so you can tell what you think now from how you got there.
A judgment, a condition, an open question, or possibilities that are still competing. It changes only when you confirm.
Current version 1
Condition: Start with CSV. Reconsider OFX after its validation is complete.
Open question: Do the support instructions cover import failures?
Current version 2, after a confirmed revision
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?
Every conversation in the Matter, including ones where nothing was kept, and every confirmed change.
Conversations
CSV and OFX release scope · Oct 9
Launch messaging for import support · Oct 13
Revising the release condition · Oct 16
Key changes
Made current · Condition · version 1 · Oct 9
Corrected · Condition · version 2 · Oct 16
Source
Release validation note · version 1 and version 2
This is designed to support your work, not make you maintain structure after every chat. A normal discussion can end with no changes to Current.
Search by what you remember, inspect the exact passage and version, then decide whether to use it.
The situation. You remember why a choice mattered, but not where you discussed it—or whether a later summary kept the condition intact.
Step 1
Use a phrase or a meaning-based question to look through supported, available material. The example searches for the reason OFX was left out of an earlier launch scope.
Find
In this Matter, by meaning
Matched message · CSV and OFX release scope · turn 2 · reply · revision 1
CSV and OFX together covers more import cases, but the OFX path still needs validation.
Step 2
Open the identified passage and its version. See nearby context where it is available, and distinguish the source’s words from an AI interpretation.
Where this came from
CSV and OFX release scope · turn 2 · reply · revision 1
Before
We can compare the launch scopes without committing to either.
Matched
CSV and OFX together covers more import cases, but the OFX path still needs validation.
After
We can explore either option without choosing a launch scope yet.
Step 3
Reading a result does not add it to a conversation. Use an exact passage as input only when you choose to do so; it does not become Current by being found.
Conversation
New conversation · First-release scope
Inputs for this message
How should we describe import support at launch?
The passage is an input for this draft only. It has not become Current.
In the example
You do not need to import, sort or structure anything before asking. Find is there when you need to get back to material, not a step every conversation has to take.
Your query
why did we leave OFX out?
Where it is
CSV and OFX release scope · turn 2 · reply · revision 1
Who wrote it
AI wording · illustrative
CSV and OFX together covers more import cases, but the OFX path still needs validation.
This is an AI reply in an earlier conversation. It is not a judgment you confirmed, and it is not a sentence from the Release validation note.
Revision 1 of that reply stays as it was written. Later, version 2 of the Release validation note says CSV and OFX validation are complete. Both are true for their own time and source.
Release validation note · version 1
CSV validation is complete. OFX validation is incomplete. The import failure guide is still incomplete.
Release validation note · version 2
CSV and OFX validation are complete. The import failure guide is still incomplete.
Find
Results are places to look. Nothing is added anywhere.
Open and read
Read only. Close leaves your draft, its inputs and Current as they were.
Use as input
You choose one exact passage and revision for the next message. The message is still a draft.
Send
Only Send sends it. A passage never becomes Current by being found or used.
New conversation
Draft · not sent
Input for this message
CSV and OFX release scope · turn 2 · reply · revision 1
“CSV and OFX together covers more import cases, but the OFX path still needs validation.”
How should we describe import support at launch?
Earlier answers keep the basis they had when they were sent, including any passage chosen as input. Today’s Current is not applied to them.
Coverage
Search coverage depends on the material, its availability and the enabled search path. It is not a promise to search every saved message or document. Partial or unavailable evidence is identified rather than filled in.
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
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
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
The review changes neither Matter. If a change is needed, return to the relevant Matter and confirm it there.
Ask Vault
Selected Matters · 2
What still needs to happen before this release scope is ready?
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.
Power · Vault Control
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
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.
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.
Start with one short experience. Come back for a particular task when it becomes useful.
Three short steps, separate from the task examples below. Prepared demo · not live AI · nothing is saved or sent.
Each task opens its own prepared example at the matching point. It does not continue your guided example. Open any of them, in any order; none is required.
When your work spans Matters. Power adds four things: Ask Vault over the Matters you select (even one), Vault Review that you start, bounded Cross-Matter Impact, and more sustained capacity. Pro keeps Ask within a Matter and basic notices for dependencies you recorded.
Need help with a real request or a pending result?
This is a separate prepared example. Your guide is kept.
Return to your guidePro is the complete way to work within your Matters. Power adds work across Matters and more capacity to keep that work going.
Pre-release plan preview. Public access and purchasing are not open yet. These are current working prices, not an offer you can buy today.
Matter Control. The complete way to work within each of your Matters. The default way to start.
$29 per month
Founding price: $25 per month
Annual, not open yet: $290 per year · Founding $250
Everything in Pro, plus Vault Control across Matters and more sustained capacity. Not a smarter or safer model.
$99 per month
Founding price: $79 per month
Annual, not open yet: $990 per year · Founding $790
Prices in USD. These are working prices for the pre-release plan. The final offer, including Founding terms, will be published before anything can be bought.
When one piece of work depends on another. In the example, the launch scope depends on support preparation:
Work in Matters and conversations
Several Matters, and several independent conversations in a Matter. A useful discussion can end with nothing kept and no change to Current.
Pro
Included
Power
Included
Current, confirmed by you
Judgments, conditions, open questions and competing possibilities. You select, edit, confirm, correct, withdraw and restore them, with their origin. AI and source updates never change Current silently.
Pro
Included
Power
Included
Exploration
Explore other directions and keep all, some or none. Suggestions can be checked and edited, and become Current only when you confirm.
Pro
Included
Power
Included
History and continuing
Independent conversations with their originals and versions. Old answers keep their old basis. A new conversation starts from Current and the inputs you choose, not from every earlier chat.
Pro
Included
Power
Included
Find originals
Find original passages by meaning, with context and version, and locate originals across your Vault where you allow it.
Pro
Included
Power
Included
Ask and Update in a Matter
Complete work inside a Matter. This is separate from Ask Vault.
Pro
Included
Power
Included
Sources
Originals with versions, refreshed when you choose. Supported formats and limits are those open at launch; not every format, file size, scan or link is supported.
Pro
Included
Power
Included
Dependency notices and suggestions
Basic notices about dependencies you recorded, and a few suggestions you can adopt. Not an automatic cleanup queue.
Pro
Included
Power
Included
Published Brief
Web page, page images, copy text and browser print, read without an account. Opening it publicly has its own conditions.
Pro
Included
Power
Included
Quality, privacy and rights
The same standards for quality, privacy, security, sources and data rights. Deeper reply modes follow their own conditions and appear only when they are ready. Power does not buy a smarter or safer model.
Pro
Same
Power
Same
Ask Vault
A read-only answer with its basis, over a scope you choose: one Matter, several, or all you allow. It does not scan all your chats.
Pro
Ask within a Matter
Power
Included
Vault Review
A bounded review you start: what changed, what still applies, conditions and open questions, conflicts, basis that may be out of date, source versions, and how much it covered. An old date alone does not mean out of date.
Pro
Not included
Power
Included
Cross-Matter Impact
Bounded impact analysis across Matters. Possible links found in a review are suggestions with source, target, version, reason and uncertainty. Follow-up after an accepted change uses only dependencies you accepted before it. You decide in the target Matter.
Pro
Basic notices for recorded dependencies
Power
Included
Sustained capacity
More frequent and larger-scope work over time. No multiplier or message count has been set.
Pro
Complete, with a finite included amount
Power
Higher
Monthly price
USD, pre-release working prices. Not on sale yet.
Pro
$29 · Founding $25
Power
$99 · Founding $79
Annual price
Working prices. Annual billing is not open yet.
Pro
$290 · Founding $250
Power
$990 · Founding $790
Included usage and capacity
Exact included amounts, and capacity for Matters, files, storage and brief delivery, are not published yet. Large operations show their scope first. There are no automatic overage charges.
Pro
To be confirmed before purchase
Power
To be confirmed before purchase
Trial
Planned: 14 days, limited. No card and no automatic charge. One total allowance that does not refill daily, for features that are actually open. When the time or the allowance runs out, new AI work pauses and your work stays readable. Browsing the synthetic example does not start it, and paying is a separate, explicit purchase.
Pro
Planned
Power
Planned
Cancel, downgrade and data
If you cancel, downgrade or run out of allowance, your content, History, read-only inspection, export, deletion and other controls stay available. Your data is never held back to make you pay.
Pro
Same
Power
Same
Founding prices of $25 for Pro and $79 for Power per month are part of the pre-release plan. Who qualifies, how long the price continues, what happens if you cancel and subscribe again, and annual eligibility will be published with the final offer. The number of Founding places has not been set.
An optional way to share a selected, frozen snapshot of your work, which can include open questions. You select and confirm what to share, and Rodspan freezes it as a brief version. The recipient reads it without an account, sees its positions, conditions, open questions and sources, and can try the example to learn what Rodspan is.
How the product keeps your work distinguishable and under your control. Rodspan is in pre-release; its data policies will be published before public access opens.
Your own text, exact quotations from sources, and AI wording are kept apart.
Current holds judgments, conditions, open questions and competing possibilities. A new conversation starts from Current and the inputs you choose. Earlier conversations are not fed in silently.
A refresh adds a new version. It does not replace an earlier input or the frozen basis of past answers. An old date alone does not make something out of date.
A review covers the Matters you select, or all you allow, and says how much it covered and what was partial. Findings are read only, and you decide in the exact Matter. A review does not run constantly over your Vault or change other Matters. Unknown connections are suggestions. A follow-up uses the exact change you accepted, a dependency you accepted before it, and an exact target.
A Published Brief contains the frozen text you chose and the source versions and quotations you allow. It does not include whole chats, private identities or private links; a publisher name you choose to show is your choice. The default link preview shows no private title or text. Downloaded copies cannot be recalled. The example on this website cannot publish.
Data handling, service providers, retention, export, deletion and accounts will be described in full, from real facts, before public access opens.
Find the next step for what you are doing. Public access is not open yet, so this page covers the example and how the product is designed to behave.
You can start by asking a question. Sources and organising are optional. A useful discussion can end with nothing kept: no change to Current, no suggestion taken and no brief.
A search by meaning gives you results. Open reads the exact original. Use adds it as an input to your next message. Inspect basis shows the versions an answer used when it was sent, not today’s.
Go to the specific Matter and choose, review and confirm the change there. A read-only review, a source refresh or AI wording never changes Current by itself.
Keep the original request and use the Check or recovery option the product shows for it. Unknown does not mean nothing happened, so do not send the same request again just because no answer appeared. Not every state can be retried or cancelled. This website cannot look up your real requests.
Keep your unsent text before you leave, and follow the recovery or sign-in steps the product shows. The example on this website does not read your account or real drafts. Never share passwords, API keys, sharing tokens or whole private conversations when you ask for help.
A Published Brief is optional and part of both plans. A frozen version and its sharing links are separate. Revoking a link affects only that link and cannot recall downloaded copies. The web page, page images, copy text and print come from the same version and never create a new version or link.
Public access is not open yet. For product support, email support@rodspan.app. It helps to describe what you did, the state you saw and any error text that is not sensitive. You will not need to upload private material.
Public access is not open yet. The policy for public use will be published here before it opens.
The illustrative examples on this website do not submit their prepared questions to an AI model or create a product account.
For privacy questions or requests, email privacy@rodspan.app.
Public access and purchasing are not open yet. Terms for public use will be published here before they open.
The questions behind Rodspan, and what this website can and cannot show.
Can important work keep moving across many AI conversations — with free discussion, optional keeping, finding originals and deliberate changes of view — without asking people to maintain structure after every exchange?
Prepared, synthetic examples you can operate to understand the design and its boundaries. They do not show the quality of a real AI, whether people understand the design without help, better decisions, retention, willingness to pay or market demand. Engineering checks confirm that specific behaviour works; they are not research with people.
We keep apart what was observed, how it was interpreted, judgments we have adopted, and results that have been shown.
Do people understand which material, and which version, they chose?
Can they come back, continue and find the original?
Can they tell a suggestion from something they confirmed?
Can a recipient understand a brief on its own?
There is no public research material yet. Nothing on this page reports a study with people.