Skip to content
☰
Documentation navigation +
implemented

Import and review a WorldSpec

Use this path when your evaluation plan recommends a synthetic simulation. You need an app session and a project. For a local example, use fixtures/worlds/rural-clinic.json from a repository checkout. A concept-only evaluation can finish without a world.

Prepare the JSON

Open your project and choose Build a world. Copy advanced WorldSpec prompt includes the public model catalog, with real model references, ports and parameters. Paste it into your own assistant and authorize which materials it may read. Review its output before sharing it; your chosen provider may process those materials under its terms. The prompt is a drafting aid; Alive's compiler determines whether the world can run.

You can also edit a reference fixture directly. This local command performs the same full compiler validation used by the app:

uv run alive world validate fixtures/worlds/rural-clinic.json
OK  rural-navigation-demo: 4 components, 2 variants, 16 assumption parameters.

Import and review

  1. Under Import a WorldSpec, paste JSON or select a .json file (at most 1 MiB).
  2. Choose Validate and review import. The app sends the candidate to POST /v1/world-specs/validate. Errors appear in the import panel; failed candidates cannot be accepted. A successful candidate shows assumptions, warnings and a change table.
  3. Review the JSON and changes, then choose Accept reviewed import. This loads the advanced editor and graph. It does not save a revision or start a run.
  4. Review any additional edits in Review before saving, check the review checkbox and choose Save and estimate. Saving stores an immutable world revision; estimation checks account limits and the available credit balance.
  5. Review the estimate and credit budget, then choose Run to authorize execution of that saved revision. Results appear on the run page, with a downloadable ZIP.

The change table compares an import against the currently loaded world, or an empty document if there is no starting world. Later edits compare against the selected starting world or the world replaced by your import. JSON Pointer paths escape / as ~1 and ~ as ~0; arrays compare by index, preserving their order. Object key ordering alone produces no change. A large diff shows its first 200 entries and asks you to review the full JSON.

Every edit clears prior validation, estimates and review acceptance. Fix invalid JSON before opening Configure. Importing does not infer a model, integration, provenance or unknown cost.

Errors and limits

The browser checks the input size, a maximum nesting depth of 64, and the structure needed for a safe preview. The API compiler checks the full schema, model versions, ports, provenance, units, variant definitions, staging permissions and execution limits. Passing the preview checks alone is insufficient. See errors and limits.

Registered external connections remain unavailable until the staging adapter ships in M13. An AI-prepared world cannot bypass this rule or the account's run budget. The change table is a review aid, not a scientific assessment. Model results remain conditional on supplied assumptions.

Next: conditional resource costs, WorldSpec reference, or reproduce a run.