ZDX CONFIG FORMAT · VERSION 1.0

One export. Two distinct configuration domains.

The unified public Axiomatic Universe full suite exports axiomatic-runtime-config.json. It captures the simulation parameters you adjusted and includes a conservative Axiomatic Runtime policy profile for further testing.

Bundle structure

{
  "format": "zdx.axiomatic.runtime-config",
  "formatVersion": "1.0",
  "simulation": {
    "engine": "axiomatic-universe-full",
    "engineVersion": 3,
    "seed": 1337,
    "particleCount": 500,
    "logicalSize": 1000,
    "timeStep": 0.05,
    "parameters": {
      "gravity": 1.2,
      "repulsion": 8,
      "damping": 0.985,
      "threshold": 0.5,
      "alignAmp": 0.02,
      "misalignDecay": 0.02,
      "collapseX": 500,
      "collapseY": 500,
      "collapseRadius": 45,
      "collapseStrength": 2.5,
      "collapseEnergy": 0.1
    }
  },
  "runtimeProfile": {
    "schemaVersion": "1.0",
    "name": "Customer Modified — exported from Axiomatic Universe",
    "origin": "customer-modified",
    "policy": {
      "allowedCommands": [
        "./help",
        "./commands",
        "./status",
        "./get"
      ],
      "allowedTools": [],
      "mutatingTools": [],
      "nonMutatingCommands": [
        "./help",
        "./commands",
        "./status",
        "./get"
      ]
    }
  }
}

Values in the example illustrate the format; the downloaded file contains the values from your current simulation controls.

How to use the export

1. Open the Axiomatic Universe page and tune the simulation controls.
2. Select Export Runtime Config to download the JSON bundle.
3. To restore the physics settings, open Axiomatic Universe, choose Import Runtime Config, and select the exported bundle. The importer validates the bundle format, engine version, and every parameter range before applying the settings.
4. Use the simulation section and matching engine version/seed to document or reproduce the experiment.
5. Import the bundle into the configuration lab to validate and test the included runtimeProfile against built-in and custom proposals. Export your edited profile separately with Export Runtime Profile; this downloads a profile JSON matching the native runtime profile schema.
6. Before deploying, validate the extracted runtimeProfile with the native Axiomatic Runtime and review the policy for your integration.

Simulation parameters

• gravity / repulsion: attraction and close-range separation strengths.
• damping: velocity damping factor.
• threshold: alignment threshold for the truth-field energy behavior.
• alignAmp / misalignDecay: energy gain for aligned particles and energy decay for misaligned particles.
• collapseX / collapseY / collapseRadius: collapse target and capture radius in logical simulation coordinates.
• collapseStrength / collapseEnergy: attraction strength and energy gate for collapse eligibility.

Runtime profile fields

The runtime profile follows schema version "1.0". Its origin is always "customer-modified" for this export. It includes allowedCommands, allowedTools, mutatingTools, and nonMutatingCommands. Mutating tools must be a subset of allowed tools; non-mutating commands must be a subset of allowed commands.

The policy profile governs action classification. Simulation physics values do not grant permissions, override approval requirements, or change immutable runtime invariants. The full bundle is a settings package, not a raw profile object; endpoints expecting a profile must receive the runtimeProfile object.