Open design document

The .slosla System format

A portable, self-contained availability System that can be inspected, edited, reported, and simulated on another device.

What the file contains

Each document carries one complete System: its ordered Stages, topology and Handoffs, embedded Block and Component snapshots, modeled switches, explicit Ideal Paths, and calculation metadata. It does not depend on the sender's Blocks library.

Safe by construction

SLO/SLA Calc does not trust the cached result in an imported document. Before saving, the app validates the schema, topology, counts, text, and availability values, then recalculates the complete System and presents an import preview.

A successful import receives new internal identifiers and becomes an independent System. It does not overwrite a same-named local design, create hidden links to the sender's Blocks, or add embedded snapshots to the receiver's Blocks library.

Share the result or the model

Document envelope

{
  "documentType": "app.sloslacalc.system-design",
  "schemaVersion": 1,
  "representation": "staged-v1",
  "exportedAt": "2026-08-07T12:00:00Z",
  "exportedBy": {
    "product": "SLO/SLA Calc",
    "version": "1.5"
  },
  "system": { }
}

The abbreviated envelope above is for orientation. An empty System is not importable.

Interoperability

The versioned JSON structure makes the model understandable outside the app and creates a foundation for future tooling. Third-party or AI-generated files should still be treated as proposed designs: import them through SLO/SLA Calc, review the topology preview, confirm every availability assumption, and verify the recalculated result before relying on them.

Try the format

Download the two reference Systems, import them from Files, and compare the effect of a Direct handoff with a Fully Cross-Connected handoff.