DSL examples

One minimal, valid example per notation Transitrix Studio ships — copy the shape directly instead of guessing at it.

The shape, in one line

Every Transitrix source file is plain YAML with two fixed anchors: a notation: key naming the format, and a *.<notation>.transitrix.yaml filename suffix. There is no type:/version: wrapper, no single-key flow: array, no next:-based sequencing — those shapes are not, and have never been, a Transitrix or pre-rename Cervin format, however plausible they look.

Every example on this page is copy-paste-ready and validates clean with transitrix validate (zero errors) against the notation's schema.

Want the full worked examples — realistic size, comments, edge cases? Browse notations/examples/ in the methodology repo. This page trades completeness for something narrower: the smallest version of each shape that still validates, all in one place.

13 notations

Strategy

Goals tree

Hierarchical goal decomposition. Filename: *.goals.transitrix.yaml

notation: goals

id: GOALS-STRATEGY-2026
name: "Strategy 2026 — Goals Tree"

goal_types:
  - { name: "Strategy",       level: 0 }
  - { name: "Strategic Goal", level: 1 }
  - { name: "Project Goal",   level: 2 }

goals:
  - id: GOAL-REVENUE-1
    name: "Triple revenue in 3 years"
    type: "Strategy"
    level: 0

  - id: GOAL-EU-1
    name: "Launch in 3 EU markets"
    type: "Strategic Goal"
    level: 1
    parent: GOAL-REVENUE-1

  - id: GOAL-BERLIN-1
    name: "Open Berlin office"
    type: "Project Goal"
    level: 2
    parent: GOAL-EU-1

Full worked example & spec →

DGCA / DGA

Drivers → goals → (changes →) activities chains. Filename: *.dgca.transitrix.yaml

notation: dgca

id: DGCA-STARTUP-1
name: "Product launch — strategy chain"
period: "2026"

factors:
  - id: DRIVER-MARKET-1
    name: "Growing demand for automated reporting"
    type: external
    category: technological

goals:
  - id: GOAL-1
    name: "Launch our analytics product to market"
    factors: [DRIVER-MARKET-1]

changes:
  - id: CHANGE-1
    name: "Build and release the core reporting feature set"
    goals: [GOAL-1]

actions:
  - id: ACTION-1
    name: "Analytics MVP"
    type: Project
    changes: [CHANGE-1]

Same file, four layers (driver → goal → change → action). Add view_config: { layers: { changes: off } } and it renders as the 3-layer DGA view instead — drivers straight to actions, no change layer.

Full worked example & spec →

Capability

Capability map

Current vs target maturity per capability. Filename: *.capability-map.transitrix.yaml

notation: capability-map
name: "Business Capabilities Map"

capability_map:
  id: CAPABILITY_MAP-BUSINESS-1
  name: Business Capabilities Map
  assessment_date: "2026-05-08"

  capabilities:
    - id: CAPABILITY-V1
      name: Order Management
      type: domain
      current_maturity: 2
      target_maturity: 3
      children:
        - id: CAPABILITY-V1.1
          name: Order Intake
          type: domain
          current_maturity: 3
          target_maturity: 3

    - id: CAPABILITY-V2
      name: Customer Relationship Management
      type: domain
      current_maturity: 3
      target_maturity: 4

Full worked example & spec →

Process

Process map

Operating / supporting / management process landscape. Filename: *.process-map.transitrix.yaml

notation: process-map
name: "Enterprise Process Landscape"

process_map:
  id: PM-ENT-001
  name: Enterprise Process Landscape
  updated_at: "2026-05-08"

  groups:
    - id: GRP-OPERATING
      name: Operating Processes
      type: operating
      processes:
        - process_id: PROC-ORD-FULFILL-001
          name: Order Fulfilment
          owner_role: ROLE-OPS-001
          status: Active
        - process_id: PROC-CUST-ONBOARD-001
          name: Customer Onboarding
          owner_role: ROLE-SALES-001
          status: Active

Full worked example & spec →

Process blueprint

Stage-by-stage design with systems, actors, equipment, information. Filename: *.process-blueprint.transitrix.yaml

notation: process-blueprint
name: "Order fulfilment — operational blueprint"

process_blueprint:
  id: PROCESS_BLUEPRINT-FULFIL-1
  name: "Order fulfilment — operational blueprint"
  process: PROCESS-ORD-FULFIL-1

  stages:
    - id: STAGE-1
      name: "Receive order"
      goal: "Capture a validated customer order."
      result: "Validated order record in OMS with payment pre-authorised."
    - id: STAGE-2
      name: "Pick & pack"
      goal: "Assemble the physical order from the reserved inventory."
      result: "Packed shipment ready for carrier handover."

  systems:
    - id: APPLICATION-OMS-1
      name: "Order Management System"
      stages: [STAGE-1, STAGE-2]

  actors:
    - id: ROLE-WAREHOUSE-OP-1
      name: "Warehouse operator"
      stages: [STAGE-2]

Full worked example & spec →

BPMN

Full BPMN 2.0 — YAML-authored, BPMN-rendered. Filename: *.bpmn.transitrix.yaml

notation: bpmn

process:
  id: order-fulfillment
  name: Order Fulfillment
  pools:
    - id: pool-main
      name: Main
      lanes:
        - id: lane-sales
          name: Sales
          elements:
            - id: start
              type: startEvent
              name: Start
            - id: receiveOrder
              type: task
              name: Receive order
            - id: end
              type: endEvent
              name: End

  flows:
    - id: flow-1
      from: start
      to: receiveOrder
    - id: flow-2
      from: receiveOrder
      to: end

The whole shape is four nesting levels: process.pools[].lanes[].elements[], plus a flat process.flows[] of { from, to } pairs. No type:/version: top-level, no single-key flow: array, no next: references on elements.

Full worked examples & spec →

Schedule

Activity network

PSND / AoN diagrams + Gantt + critical path. Filename: *.action.transitrix.yaml

notation: action

name: "Platform Launch 2026"

actions:
  - id: A-001
    name: Requirements analysis
    duration: 5
  - id: A-002
    name: Architecture design
    duration: 8
    predecessors: [A-001]
  - id: A-003
    name: Backend implementation
    duration: 15
    predecessors: [A-002]

Full worked examples & spec →

Activity card

Single-project narrative: scope, motivation chain, milestones. Filename: *.action-card.transitrix.yaml

notation: action-card
name: "EU MDR Conformity Programme"

action_card:
  id: ACTION_CARD-EU-PROGRAMME-1
  project: ACTION-EU-PROGRAMME-1

  description: >
    Programme of work bringing the company's first product line into
    compliance with the EU Medical Device Regulation.

  milestones:
    - id: MILESTONE-EU-CONFORMITY-CERT-1
      name: "EU MDR conformity-assessment certification obtained"
      date: "2027-01-31"

Full worked example & spec →

Risk

Scenarios

Scenario planning across factors. Filename: *.scenarios.transitrix.yaml

notation: scenarios
name: "Optimistic Growth 2027"

scenario:
  id: SCN-001
  name: Optimistic Growth 2027
  status: Active

  vision: |
    By 2027 the organisation has expanded into three new markets
    and doubled its digital product portfolio.

  goals:
    - goal_id: GOAL-REV-001
    - goal_id: GOAL-MARKET-001

  activities:
    - activity_id: ACT-EXPAND-CEE-001

Full worked examples & spec →

Catalogue

Applications

Applications, integrations, platforms, data stores. Filename: *.applications.transitrix.yaml

notation: applications
name: "Enterprise Applications Portfolio 2026"

applications_catalogue:
  id: APP-CAT-ENTERPRISE-001
  name: Enterprise Applications Portfolio 2026
  updated_at: "2026-05-14"

  applications:
    - app_id: APP-OMS-001
      name: Order Management System
      type: application
      status: Active
      domain: Operations
      integrations:
        - target: APP-CRM-001
          direction: outbound
          protocol: REST
          description: Sends order events to CRM on state change

    - app_id: APP-CRM-001
      name: CRM System
      type: application
      status: Active
      domain: Sales

Full worked example & spec →

Products

Digital products, services, bundles. Filename: *.products.transitrix.yaml

notation: products
name: "Digital Products Portfolio 2026"

products_catalogue:
  id: portfolio-2026
  name: Digital Products Portfolio 2026
  updated_at: "2026-05-13"

  products:
    - product_id: prod-data-platform
      name: Analytics Platform
      type: platform
      status: Active
      domain: Data & Analytics

    - product_id: prod-mobile-app
      name: Customer Mobile App
      type: digital_product
      status: Active
      domain: Customer

Full worked example & spec →

Decomposition

Nested blocks

Recursive block tree. Filename: *.blocks.transitrix.yaml

notation: blocks
name: "Software architecture"

nested_blocks:
  id: BLOCKS-ARCH-1
  name: "Software architecture"

  blocks:
    - id: FRONTEND
      name: "Frontend"
      children:
        - id: REACT_APP
          name: "React App"
        - id: REDUX_STORE
          name: "Redux Store"
    - id: BACKEND
      name: "Backend"
      children:
        - id: REST_API
          name: "REST API"
        - id: BUSINESS_LOGIC
          name: "Business Logic"

Full worked example & spec →

Compliance

Compliance impact

Obligation × subject impact matrix. Filename: *.compliance-impact.transitrix.yaml

notation: compliance-impact
name: "Retail product — GDPR obligations"

view:
  id: COMPLIANCE_IMPACT-RETAIL-GDPR-1
  name: "Retail product — GDPR obligations"
  report_type: product

  subjects:
    products: [PRODUCT-RETAIL-1]

  obligations:
    filter:
      derived_from_codex: [REGULATION-EU-GDPR-1]

  grouping:
    rows: "obligation"
    columns: "product-stage-task"

Compliance matrix, coverage metric, and gap dashboard are report views computed over this data plus assertion/requirement records — not separate authored file formats.

Full worked example & spec →

Next