Inspect a World
Read what the app changed, check which World is running, or open its dashboard and vendor screens. For an existing World, start with its status and log. The complete example below creates a small World from scratch; use Node 22.6 or newer and npm, with registry access for installation.
Make a change to inspect
In an empty directory, save package.json:
{
"name": "inspect-app",
"private": true,
"type": "module",
"dependencies": {
"stripe": "17.7.0"
},
"devDependencies": {
"@volter/world": "3.0.169",
"@volter/twin-stripe": "3.0.2",
"@volter/world-console": "3.0.152",
"@volter/world-core": "3.0.156",
"@volter/world-runtime": "3.0.166",
"@volter/world-ui": "1.0.156"
}
}Save .env.example:
STRIPE_SECRET_KEY=Save signup.mjs:
import Stripe from 'stripe';
const stripe = new Stripe(process.env.STRIPE_SECRET_KEY);
await stripe.customers.create({ email: 'ada@example.com', name: 'Ada' });
console.log('customer created');npm install
./node_modules/.bin/volter world init --name inspect-app
./node_modules/.bin/volter world up
./node_modules/.bin/volter world run -- node signup.mjs
./node_modules/.bin/volter world status
./node_modules/.bin/volter world log
./node_modules/.bin/volter world diffcustomer.createstatus names the checked-out branch and running services. log lists stored mutations in
each vendor's position order; positions from different vendors are independent. diff groups changes since the branch's base. A read-only SDK call need not add a log entry.
Your SDK can read back stored records, as getting started demonstrates.
The dashboard's changed-record view shows kernel-supplied before and after values. An unavailable historical value is labeled as unavailable. Record tables resolve declared relationships to names while retaining the full record.
Events starts with business activity. Include provisioning also shows initial default data and writes explicitly tagged as provisioning; default-data entries identify their origin instead of attributing them to the app. The counts state the loaded scope. Include internal records exposes bookkeeping types without making them the default vendor table. These filters keep full history and state intact. The combined event timeline uses clock instants and stable ties; it is not evidence of cross-vendor causality.
Open the dashboard
The dashboard needs @volter/world-console installed in the app; a global CLI installation
alone does not supply that dependency. The manifest above includes it.
Stop the compute started by up before opening the World through view. Ordinary down
retains the customer you just created:
./node_modules/.bin/volter world downIn your terminal, run:
$ ./node_modules/.bin/volter world view --no-openKeep that command running. Open the URL on the printed console line in your normal browser.
view owns the World it starts and its server; it is not a command that prints a URL and exits.
At the World's own *.localhost address, the dashboard opens a local session without a copied key.
If the command prints a read-only view link, open that entire link, including its #token=…
fragment, to inspect the World. If you opened the plain console URL and see a World-key form,
enter the value on this same command's read line. These are keys for the local World; no
platform or vendor sign-in is needed.
Inspect the branch and log, then open the vendor's available screens. A vendor screen is a twin interface, not a live vendor account; screen availability is separate from API coverage. If a screen is absent, use the SDK read and recorded changes instead.
In Board, select a vendor frame, then choose Use screen beside its name. Use the vendor's links and forms inside that frame. Done (or Esc) returns to panning and zooming the Board. Double-clicking a frame also enters its screen.
Stop view with Ctrl-C when finished. Stop application consumers first. Ordinary shutdown
retains state; do not forward the local dashboard port to other people. Share a World
owns the team workflow and its access controls.
When a result looks wrong
Check the selected package/version, current branch, seed and clock. Confirm that the app command
ran through volter world run. Read the publisher's README for the failing operation and
inspect its /twin manifest and scenario matches when applicable. Distinguish an app bug,
unsupported operation, scripted answer and routing problem before changing the app.
The operator diagnostic commands add doctor, tail and
covers for an explicitly named World. Run your test suite shows
assertions on application behavior, and shape the World for a test
explains scripted responses and faults.