“King Aldric died at Greywatch in 614 AR.”
This statement is explicitly established in the available world entries.
Grounded in your canon
The answer starts with your world.
Vitus finds the lore relevant to the task instead of sending your whole world with every question.
Retrieval can consider the current entry, linked entries, relevant lore found elsewhere in the world and the question being asked. Focused mode keeps the entry you started from in the foreground while still allowing connected material to be found.
The model is only one part of the feature. Vitus's structure, relationships, retrieval, context selection and citations shape the answer before it reaches you.
- Current or focused entry
- Connected and retrieved lore
- The current question or operation
- Evidence that can be traced back to entries
Make a quick entry from your own lore. Ask Vitus can also draft a minor character, item or place, using only what your world already holds. If something is missing, it tells you what to add first. Nothing is saved until you say yes. It uses credits on every plan.
Grounded answerGreywatch became impossible to hold after the northern supply road fell. Aldric's decree ordered House Vael to preserve its remaining forces rather than defend the fortress. The current canon does not establish whether the order was welcomed or resisted.
Select a source to illuminate its support in the answer.
Know what is known
Knowing the answer means knowing when there isn't one.
Vitus is designed to distinguish established canon from supported inference and information the world simply does not contain.
Conceptual response states
Question: Who killed King Aldric?
“House Vael may have benefited from Aldric's death, but the current canon does not confirm their involvement.”
The conclusion is plausible from available material, but it is not a canonical fact.
“The current world does not specify who delivered the killing blow.”
There is not enough supported material to answer. The honest response is to leave the gap visible.
Lore Consistency Review · Worldsmith+
Find contradictions before your audience does.
Review meaning-level contradictions across prose and connected entries, with evidence the creator can judge. It also checks the Rule entries in your world against each other and against the entries they govern.
Deterministic validation
Checks structural constraints and reference integrity with explainable rules.
- Broken references
- Required data
- Naming rules
Lore Consistency Review
Looks for contradictions that require understanding prose and connected context.
- Conflicting dates
- Incompatible claims
- Prose versus structured data
Conceptual review workflow
Two entries. One conflict.
Lady Elara · character“Elara left Edrin in exile in 603 AR and never returned.”
Defence of Edrin · event“Elara personally commanded Edrin's defence in 606 AR.”
Possible direct contradiction
Elara appears in Edrin after an entry says she never returned.
Both claims may be intentional, but they cannot be treated as simultaneously literal without further explanation.
The finding is ready for the creator to judge.
These controls demonstrate the review decision, but do not edit a world from this website.
AvailableWorldsmith+
Lore Consistency Review consumes Vitus AI credits according to the scope of the review.
Language & context
Choose the material. Preserve the rules.
Focused context and authored language systems give creators explicit control over advanced AI work.
AvailableWorld briefs · Core
Take a deliberate slice of the world with you.
A World brief turns all your entries, or a saved filter, into one readable Markdown file for another AI tool, at the spoiler level you choose. It is built on your computer and costs no credits. It is separate from what Ask Vitus reads.
A focused bundle keeps unrelated lore out of the task. Choose an era, culture, campaign, region or faction, then retain control over the wrapper instructions and where the file goes.
Conceptual bundle scopes
The Northern War
Kingdom of EdrinHouse VaelGreywatchNorthern Campaign timelineCommander Arlen
Useful for questions about the campaign without including every unrelated era.
Vael culture
House VaelVaelic oathsMarriage customsGrey banner ritual
Useful for a culture-focused task with its customs and terminology together.
Greywatch region
GreywatchNorthern roadThree border villagesRegional map notes
Useful when a task needs one place and its immediate surroundings.
Illustrative world names; these are not built-in Vitus content.
AvailableTranslator · every plan, with credits
Your language should remember its own rules.
The user defines the vocabulary, grammar, registers, cultural bias, calibration phrases and writing system. Vitus applies that material to the translation. Any word it has to invent is added to your vocabulary and listed under the translation, so you can regenerate or reject it. Words you keep are never swapped for a synonym.
This is not generic phrase substitution. Register, idiom and accepted vocabulary can shape each result.
Illustrative language example
EnglishWelcome home, old friend.
The fictional outputs are illustrative website copy, not a built-in language or a live translation.
Your world, your control
AI is optional. Ownership isn't.
Use Vitus's local worldbuilding foundation without constant AI usage. Ask for higher-level assistance when it is useful.
Higher plans let Vitus read more of your world for one question: Core reads up to about 4,000 tokens of relevant material, Apprentice 8,000, and Worldsmith and Loremaster 16,000. This is how much Vitus considers at once, never a limit on the size of your world.
Build without AI. Ask for help when you want it.
World files, entries, relationships, trees, maps, timelines, editors and other local tools remain the product. If the network is unavailable or credits run out, local work does not disappear.
Readable filesRelationshipsTreesMapsTimelinesEditors
Only when an online operation needs it.
On your deviceLocal worldCreating, editing, browsing and mapping do not send Shieldwall a copy merely by being used.
→Deliberate AI actionRequired instructions + contextSent through Shieldwall's broker to an AI API provider for that operation.
Shieldwall does not claim ownership of private worlds or use private world content to train its own public generative-AI model. Final production subprocessors and retention settings will be published before public AI billing opens.
Read the current Privacy PolicyHow Vitus AI credits work
Credits reflect the work, not provider tokens.
Customers use Vitus AI. Provider selection and routing remain an internal implementation detail.
A focused factual question needs less context and synthesis.
Combining several relevant entries requires more work than a narrow lookup.
Broad context and repeated analysis naturally require more work. Materially large operations should show an estimate where practical.
Every account starts with 200 credits.
The welcome grant is given once. Paid plans then add a monthly allowance that resets each month and does not roll over: 400 on Apprentice, 1,200 on Worldsmith and 3,000 on Loremaster. These are planning figures and may change before checkout opens.
Bought credits never expire.
Credit bundles (500 for £4.99, 1,500 for £12.99, 4,000 for £29.99) stay on your account after a cancellation or downgrade. Monthly credits are used first.
Local work keeps working.
If credits are exhausted or Vitus AI cannot connect, AI-backed operations pause; local world data and local tools remain available.
Vitus is a worldbuilding platform
Structure first. Intelligence when you need it.
Explore every part of the connected workspace, or join the beta and help shape how Vitus AI handles real worlds.