WORKFLOW SPEC (YAML) • ASPICE/ISO-INSPIRED

Workflow Specification

A pragmatic YAML spec for defining evidence-grade work: units, controls (gates), interfaces, architecture views, and traceability. Structured definitions that can be validated and executed.

Request a sample pack

What is it?

This is the definition format behind Compliance Engine and Operating Packs: a set of YAML schemas/templates that describe how work runs and what must be produced. It’s shaped by standards-driven thinking (ASPICE/ISO-style), but designed to stay usable outside automotive too.

Artifact-first schemas

Define real artifacts (architecture, interface specs, unit design, CM bindings) with stable IDs, versioning, and structured fields.

Controls and gates

Treat validations, reviews, and sign-offs as first-class objects.

System structure

Capture units, connectors, scenarios, deployment allocations, and traceability references in a consistent shape.

Traceability hooks

Every artifact has traceability fields so linking requirements ↔ design ↔ tests becomes systematic instead of manual.

Executable path (in progress)

The spec is designed to be executed by a runtime. Execution tooling is under active development.

Reusable packs (in progress)

Definitions can be grouped into operating packs so teams start from proven patterns instead of blank pages within your toolchain.

Real YAML (excerpted)

Examples below are shortened excerpts from real templates. The goal is readability plus structure.

Configuration management binding

Bind units/components to configuration items and storage locations (CM bindings).

yaml

artifact_kind: cm_binding
schema_version: "0.1"

card:
  id: ""
  name: ""
  project_id: ""
  domain: ""

unit:
  unit_id: ""
  unit_name: ""

cm_reference:
  cm_domain_catalogue_id: ""
  ci_id: ""
  ci_name: ""

location:
  repo_id: ""
  repo_url: ""
  path: ""

Interface specification

Define a contract: interaction style, payload semantics, error model, observability, traceability.

yaml

artifact_kind: interface_spec
schema_version: "0.1"

card:
  id: ""
  name: ""
  domain: ""
  interface_id: ""

interaction:
  style: ""
  direction: ""
  contract:
    preconditions: ""
    effects: ""
    timing: ""

data_semantics:
  payloads:
    - id: ""
      name: ""
      fields:
        - id: ""
          name: ""
          type: ""
          required: false

traceability:
  requirements_ref: ""
  concerns_ref: []

Architecture description

Capture stakeholders, concerns, constraints, and multiple views (structural/dynamic/deployment).

yaml

artifact_kind: architecture_description
schema_version: "0.1"

card:
  id: ""
  name: ""
  system_of_interest: ""
  scope: ""
  domain: ""

views:
  structural:
    elements:
      units:
        - unit_id: ""
          unit_name: ""
      connectors:
        - interface_id: ""
          purpose: ""
          units:
            - unit_id: ""
              interaction_type: "inbound|outbound"

traceability:
  requirements_ref: ""
  integration_plan_ref: ""

Tooling (in progress)

We’re building the supporting tooling around the spec. Today, access is by collaboration/pilot — there is no public download page yet.

COMING SOON

Schema validator

Free

Validate YAML against schema versions and catch broken references early.

Schema validation
Reference integrity checks
Versioning consistency
CI-friendly output

Request access

COMING SOON

Linter / formatter

Free

Keep definitions readable and consistent across a repo.

Formatting rules
Style and naming conventions
Useful diffs for reviews

Request access

COMING SOON

Doc export (templates)

Enterprise

Generate docs from structured definitions (where it makes sense).

Markdown export
Consistent headings/sections
Traceability tables (when available)

Discuss

View all tools & APIs

Access & pricing

No public pricing yet. Early use happens through scoped pilots and partnered work while the system matures.

Pilot

A small, defined slice: one workflow + artifacts + validation rules, with clear success criteria.

Custom

Contact for pricing

Sample pack provided
Scoped workflow slice
Validation + review gates
Handover of definitions
Self-serve SaaS

Request a pilot

Samples

We can share a small sample pack (templates + example artifacts) on request. Public downloads are not available yet.

📄

Sample pack (YAML templates + examples)

REQUEST•—

beginner

A compact set: interface spec + architecture description + CM binding + unit design skeleton.

Request Sample

Why this approach works

Makes documentation and evidence a byproduct of work

Improves consistency across teams without heavy bureaucracy

Stabilizes interfaces and architecture boundaries over time

Replaces ad-hoc prompting with versioned, reviewable definitions

Creates a path from templates → packs → executable workflows

Ready to Transform Your Process Management?

Agree on standardized, repeatable workflows that scale with your team and projects.

Get Started Today Download Free Samples