SysML v2

In build

The safety node of your digital thread.

SysML v2, KerML and the Systems Modeling API made the system model the authoritative system definition. SPARC is being built to consume that definition and hold the safety analysis attached to it — this page describes that build in the future tense, with what exists today stated first.

What's built today

  • An ingestion engine that reads the SysML v2 standard JSON serialisation end to end, from a file export — no network required. Library-level today: the import screen and API are part of the build.
  • Full-accounting ingestion: a run that cannot account for every element is refused, and unknown constructs are counted and reported, never dropped.
  • Not yet written: the table that lets analyses reference model elements. Nothing in SPARC anchors to a model yet.

The build plan.

No dates. Each stage ships together with its gates.

  1. 01

    Consume

    Functions, components and their allocations will arrive from the model. Hand-entering the functional architecture becomes optional.

  2. 02

    Trace

    Hazards, fault trees and GSN claims will anchor to model elements at a pinned commit — the as-analysed snapshot, retained.

  3. 03

    Detect drift

    When the model moves, SPARC will name the linked safety artefacts whose anchors changed. It reports the references; the engineer records the assessment. Nothing propagates on its own.

  4. 04

    Publish back

    Roadmap

    Derived safety requirements and classifications written back as model artefacts, on their own branch, through your review gate.

The gate this feature ships behind

Imported functions arrive unassessed by construction — so model import ships together with the completeness checks that catch never-assessed imported functions and orphaned source references. Until those checks exist, FHA completeness over an imported architecture could read green while functions were never assessed.

Which tools it will connect to

Two transports are designed: file import of the standard JSON serialisation, and a live pull over the Systems Modeling API. The engine has not yet met a real customer export, and no conformance certification exists — so no tool names appear on this page. When a repository's export has been read end to end, it will be named here.

Stated non-goals

SPARC will not derive STPA control structures from part and connection usages, will not edit your model, and will not propagate model changes into analyses without an explicit, audited re-sync.