Schematex

/ GALLERY

153 examples45 diagram types14 clusters

The diagrams doctors, engineers, and lawyers actually use.

All 45 diagram types, grouped by cluster — each follows a published standard, shows the version it shipped, and renders every example form we test.

Relationships

5
Genogramsince v0.1.0 · upd v0.2.4, v0.3.1§ McGoldrick, Gerson & Petry (2020) + GenoPro emotional taxonomyDocs →

Family diagram with emotional, medical, and generational notation.

Genogram: Smith Family Genogram diagram with 3 individuals across 2 generations Smith Family John (1975) Mary (1977) Alice (2005) John (b. 1975) Mary (b. 1977) Alice (b. 2005) m. 2002 MARKERS Index person (focal subject)
Nuclear family (minimal template)
Genogram: BRCA1 Family Genogram diagram with 8 individuals across 3 generations BRCA1 Family I_1 (1930-1995) 65 I_2 (1932-1990) 58 II_4 (1954) II_1 (1955) II_2 (1958) II_3 (1960) III_1 (1985) III_2 (1988) I_1 (1930–1995) I_2 (1932–1990) II_4 (b. 1954) II_1 (b. 1955) II_2 (b. 1958) II_3 (b. 1960) III_1 (b. 1985) III_2 (b. 1988) SYMBOLS Deceased CONDITIONS Ovarian Cancer Breast Cancer MARKERS Index person (focal subject)
Hereditary cancer (BRCA1) family
Genogram: Familia Isaías Genogram diagram with 9 individuals across 2 generations Familia Isaías Víctor Seguel Mónica Barrientos Tío materno Don Pablo Doña Priscila Isaías (2020) 6 ? ? Pablo (jr) Alanis Víctor Seguel Mónica Barrientos Tío materno Don Pablo Doña Priscila Isaías (b. 2020) ? Pablo (jr) Alanis SYMBOLS Unknown STRUCTURAL Cohabiting (ended) Foster RELATIONSHIPS Nevermet Physical Abuse MARKERS Index person (focal subject) Sibling(s) — unknown count
Foster care / child protection
Genogram: Medical History Genogram diagram with 7 individuals across 3 generations Medical History Grandfather (1930-1990) 60 Grandmother (1935) Father (1960) Mother (1962) Uncle (1963) Patient (1988) Sister (1991) Grandfather (1930–1990) Grandmother (b. 1935) Father (b. 1960) Mother (b. 1962) Uncle (b. 1963) Patient (b. 1988) Sister (b. 1991) SYMBOLS Deceased CONDITIONS Heart Disease Diabetes Cancer Hypertension MARKERS Index person (focal subject)
Multi-generation medical history
Genogram: The Potter Family Genogram diagram with 10 individuals across 3 generations The Potter Family Fleamont (1909-1979) 70 Euphemia (1920-1979) 59 Mr_evans (1925) Mrs_evans (1928) James (1960-1981) 21 Lily (1960-1981) 21 Vernon (1951) Petunia (1958) Harry (1980) Dudley (1980) Fleamont (1909–1979) Euphemia (1920–1979) Mr_evans (b. 1925) Mrs_evans (b. 1928) James (1960–1981) Lily (1960–1981) Vernon (b. 1951) Petunia (b. 1958) Harry (b. 1980) Dudley (b. 1980) m. 1978 SYMBOLS Deceased RELATIONSHIPS Close Hostile Cutoff MARKERS Index person (focal subject)
The Potter family
Ecomapsince v0.1.0 · upd v0.3.0§ Hartman (1978) + NSGCDocs →

Radial diagram of a client's connections to external systems.

Ecomap Ecomap diagram with 6 external systems Marcus Mother Father (divorced) East High School Soccer Coach Soccer team Ms. Chen primary caregiver EOW weekends mentor weekly SYSTEMS Community Education Family Mental Health TIES Strong
Teen client intake
Ecomap Ecomap diagram with 9 external systems Nguyen Family IRC Office Lincoln Elementary Adult ESL Class Community Clinic Ms. Patel Vietnamese Temple Sponsor Family Warehouse Job Cousins (CA) active case twice weekly vaccinations weekly anchor housing host new, part-time phone support SYSTEMS Community Cultural Education Family Government Health Mental Health Work TIES Strong Moderate
Refugee family resettlement
Ecomap Ecomap diagram with 9 external systems James Age 28 AA Group Bill (Sponsor) Warehouse Job Mom Ex-wife Children (2) Old Friends P.O. Johnson CBT Therapist new, probationary supportive custody conflict supervised visits trying to cut off weekly SYSTEMS Family Legal Mental Health Substance Work TIES Strong Moderate Weak Stressful Broken
Substance abuse recovery
Pedigree chartsince v0.1.0 · upd v0.3.1§ NSGC Pedigree Standardization (Bennett 2008)Docs →

Clinical genetic-counselling pedigree with affected/carrier states.

CF family — autosomal recessive Pedigree chart with 8 individuals across 3 generations I II III I-1 (carrier) I-2 (carrier) II-4 (carrier) II-2 (carrier) II-1 (affected) P II-3 III-1 (affected) III-2 I-1 I-2 II-4 II-2 II-1 II-3 III-1 III-2 GENETIC STATUS Affected Carrier SYMBOLS P Proband (P) — first affected case identified
Cystic fibrosis (autosomal recessive)
Hemophilia A Pedigree chart with 10 individuals across 3 generations I II III I-1 I-2 (carrier-x) II-5 II-2 (carrier-x) II-1 (affected) II-3 II-4 III-1 (affected) III-2 (carrier-x) III-3 I-1 I-2 II-5 II-2 II-1 II-3 II-4 III-1 III-2 III-3 GENETIC STATUS Affected X-linked carrier
Hemophilia A (X-linked recessive)
Assisted Reproduction Family Pedigree chart with 6 individuals across 2 generations I II Intended_father Egg_donor E Intended_mother Surrogate E Embryo Child P I-1 I-2 I-3 I-4 II-1 II-2 SYMBOLS Unknown sex P Proband (P) — first affected case identified
Assisted reproduction pedigree
BRCA1 Family — Hereditary Breast/Ovarian Cancer Pedigree chart with 12 individuals across 3 generations I II III I-1 I-2 (affected) II-4 II-1 (affected) II-6 II-3 (carrier) II-2 III-1 (affected) P III-2 III-3 (presymptomatic) III-6 (carrier) III-7 I-1 I-2 II-4 II-1 II-6 II-3 II-2 III-1 III-2 III-3 III-6 III-7 GENETIC STATUS Affected Carrier Presymptomatic SYMBOLS Deceased P Proband (P) — first affected case identified
BRCA1 hereditary cancer (four-generation)
Phylogenetic treesince v0.1.0§ Newick + NHX extensionsDocs →

Rectangular cladogram from a Newick/NHX tree string.

Dendrogram: Sample clustering Dendrogram with 5 taxa, dendrogram mode, rectangular layout Sample clustering A B C D E 0 1 2 3 4 5 cluster distance
Sample clustering dendrogram (no cut)
Dendrogram: Gene expression clusters Dendrogram with 5 taxa, dendrogram mode, rectangular layout, cut at 4 into 2 clusters Gene expression clusters A B C D E 0 1 2 3 4 5 cluster distance cut = 4
Gene expression clusters (cut into flat groups)
Phylogenetic Tree: Bacterial Diversity Phylogenetic tree with 10 taxa, phylogram mode, rectangular layout Bacterial Diversity Ecoli Salmonella Vibrio Bacillus Staph Listeria Myco_tb Myco_leprae Strepto Lactobacillus 98 85 92 100 78 0.2 substitutions/site
Bacterial diversity (ten-taxon tree)
Phylogenetic Tree: SARS-CoV-2 Variants Phylogenetic tree with 7 taxa, chronogram mode, rectangular layout SARS-CoV-2 Variants Omicron lineages Alpha Beta Gamma Delta BA1 BA2 XBB 0.2 years before 2023
SARS-CoV-2 variant chronogram
Sociogramsince v0.1.0§ Moreno (1934) sociometryDocs →

Force-directed social network graph with edge types and weights.

Sociogram: Operation Sunset - Communication Network Sociogram with 9 members and 10 connections Operation Sunset - Communication Network supplier distributor Subject Alpha Lieutenant 1 Lieutenant 2 Courier A Courier B External Contact 1 External Contact 2 Associate 1 Associate 2 TIES Positive tie Neutral tie
Criminal communication network
Sociogram: Playground Dynamics Sociogram with 8 members and 10 connections Playground Dynamics conflict tom jack mike leo anna beth chloe diana GROUPS Boys Girls TIES Positive tie Negative tie Neutral tie
Playground dynamics
Sociogram: Engineering team — informal influence Sociogram with 10 members and 10 connections Engineering team — informal influence alex sam priya jordan kim tao lee ravi nina dev GROUPS Tech leads Senior ICs Junior TIES Positive tie Neutral tie
Engineering team influence mapping

Electrical & Industrial

11
Timing / waveform diagramsince v0.1.0§ WaveDrom-compatible signal descriptionDocs →

Digital signal timing diagram with clocks, buses, and annotations.

Synchronous Bus Read Digital timing diagram with 4 signals D0D1D2D3 CLK RST EN DATA Synchronous Bus Read
Timing diagram with clock and run-length shorthands
I2C Read Burst Digital timing diagram with 4 signals ADDR+WACKREGACKREP STARTADDR+RACKDATA0ACKDATA1 Control SCL START Bus SDA Status BUSY I2C Read Burst
I2C read burst timing
SPI Transaction Digital timing diagram with 4 signals 0xAB0xCD0xEF0x010x020x030x04 CLK CS_N MOSI MISO SPI Transaction
SPI transaction timing diagram
Logic gate netlistsince v0.1.0 · upd v0.6.3§ IEEE Std 91/91a-1991symbolsDocs →

IEEE 91 logic-gate diagram from a gate-list DSL.

IEC Gate Gallery Logic gate diagram with 7 gates, 4 inputs, 7 outputs & ≥1 =1 & ≥1 1 1 EN A B C EN Y_and Y_or Y_xor Y_nand Y_nor Y_not Y_tri IEC Gate Gallery
IEC logic gate gallery
1-bit Full Adder Logic gate diagram with 5 gates, 3 inputs, 2 outputs XOR AND XOR AND OR A B Cin Sum Cout 1-bit Full Adder
1-bit full adder
Circuit schematicsince v0.1.0 · upd v0.3.0, v0.3.1, v0.6.7, v0.6.9§ IEEE Std 315 / ANSI Y32.2symbolsDocs →

Positional circuit schematic with resistors, sources, transistors.

Pull-up + push button Circuit schematic with 5 components Pull-up + push button +V15VR110k?switchC1100n
Pull-up resistor circuit with dir= orientation hint
Bridge Rectifier Supply Circuit schematic with 8 components Bridge Rectifier Supply +V112VacD11N4007D21N4007D31N4007D41N4007C1470uRload1k
Bridge rectifier power supply
CE Amp (netlist) Circuit schematic with 6 components CE Amp (netlist) +V19VRc2.2kRb100kQ1Re1k
NPN common-emitter amplifier
Inverting Op-Amp (netlist) Circuit schematic with 8 components Inverting Op-Amp (netlist) +VinAC1V+Vp+12V+Vn-12VRin10kRf100k+U1 TL072Rbias10k
Inverting op-amp amplifier
Control-systems block diagramsince v0.1.0 · upd v0.6.8§ Ogata / standard controls textbook conventionDocs →

Transfer-function block diagram with summing junctions and feedback.

PID control loop Block diagram with 3 blocks, 1 summing junctions, 5 signals PID control loop r (setpoint) + y (output) + PID C(s) Plant G(s) in in
PID control loop
Nested Feedback Loops Block diagram with 7 blocks, 2 summing junctions, 10 signals Nested Feedback Loops R(s) + + Y(s) + + G1(s) G2(s) G3(s) H1(s) H2(s) in out in out
Nested feedback loops
Ladder logicsince v0.1.0§ IEC 61131-3 Ladder DiagramDocs →

IEC 61131-3 ladder-logic program with rungs, contacts, coils.

Motor Start/Stop PLC ladder logic diagram with 1 rung Motor Start/Stop Rung 001 — Seal-in circuit — Start Button START_PB IN 1.0 Aux Contact MOTOR_AUX BIT 3.0 Stop Button STOP_PB IN 1.1 Motor Command MOTOR_CMD OUT 2.0
Motor start/stop seal-in circuit
Conveyor Interlock Chain PLC ladder logic diagram with 3 rungs Conveyor Interlock Chain Rung 001 — Run downstream conveyor first — Rung 002 — Start upstream only when downstream is running — Rung 003 — Latch jam alarm — Auto mode AUTO_MODE BIT 1.0 E-stop not tripped ESTOP_OK BIT 1.1 Downstream jam clear CV2_JAM IN 2.2 Conveyor 2 run CV2_RUN OUT 4.1 Auto mode AUTO_MODE BIT 1.0 CV2 running CV2_RUN OUT 4.1 Upstream jam clear CV1_JAM IN 2.1 Conveyor 1 run CV1_RUN OUT 4.0 CV1 jam CV1_JAM IN 2.1 CV2 jam CV2_JAM IN 2.2 S Jam alarm JAM_ALARM BIT 3.0
Conveyor interlock chain
System Mode Selection PLC ladder logic diagram with 2 rungs System Mode Selection Rung 001 — Set system Auto mode, reset Manual — Rung 002 — Set Manual, reset Auto (with Home seal-in) — Auto Mode HMI Pushbutton AUTO_HMIPB BIT 5.10 Manual Mode HMI Pushbutton MANL_HMIPB BIT 5.11 System Fault SYS_FAULT BIT 3.0 S System Auto Mode SYS_AUTO BIT 3.1 R System Manual Mode SYS_MANUAL BIT 3.2 Manual Mode HMI Pushbutton MANL_HMIPB BIT 5.11 System Home Command SYS_HOMECMD BIT 3.5 Auto Mode HMI Pushbutton AUTO_HMIPB BIT 5.10 System Fault SYS_FAULT BIT 3.0 S System Manual Mode SYS_MANUAL BIT 3.2 R System Auto Mode SYS_AUTO BIT 3.1
System mode selection (Set/Reset)
Tank Level Pump Control PLC ladder logic diagram with 3 rungs Tank Level Pump Control Rung 001 — Fill pump seal-in — Rung 002 — Run delay proves flow — Rung 003 — No-flow alarm after delay — Low level LOW_LEVEL IN 1.0 Pump running PUMP_RUN OUT 2.0 High level HIGH_LEVEL IN 1.1 Fault clear FAULT BIT 3.0 Fill pump PUMP_RUN OUT 2.0 Pump running PUMP_RUN OUT 2.0 TON IN=PUMP_RUN PT=5000 name=Flow prove delay FLOW_DELAY Delay done FLOW_DELAY TMR 1.0 Flow switch FLOW_OK IN 1.2 S No flow alarm FLOW_ALARM BIT 3.1
Tank level pump control
Function Block Diagram (FBD)since v0.4.0§ IEC 61131-3:2013 §6.4 + §2.5 standard FB library; see 23-FBD-STANDARD.mdDocs →

IEC 61131-3 §6.4 function blocks wired through named ports.

FBD: Motor Control FBD with 2 network(s). 0 — Start latch Start Latch Stop EmergencyStop Latch OR ≥1 IN1 IN2 OUT AND & IN1 IN2 IN3 OUT 1 — Drive output Latch MotorOut MOVE IN OUT
Motor start/stop latch (FBD)
FBD: Tank Level Setpoint Limiter FBD with 2 network(s). 0 — Clamp setpoint to safe range DesiredSetpoint SafeSetpoint LIMIT MN 0.0 IN MX 95.0 OUT 1 — Alarm on out-of-range request DesiredSetpoint Alarm OR ≥1 IN1 IN2 OUT LT IN1 IN2 0.0 OUT GT IN1 IN2 95.0 OUT MOVE IN OUT
Tank setpoint limiter + alarm (FBD)
FBD: Bottle Counter FBD with 3 network(s). 0 — Debounce sensor with 50ms dwell BottleSensor TON IN PT T#50ms Q ET 1 — Count one bottle on rising edge of debounced signal BatchDone BatchSize R_TRIG CLK Q CTU CU R PV 24 Q CV 2 — Latch batch done BatchDone MOVE IN OUT
Bottle counter — debounce → edge → count (FBD)
Sequential Function Chart (SFC)since v0.4.0§ IEC 61131-3:2013 §6.5 + IEC 60848 GRAFCET visual subset; see 24-SFC-STANDARD.mdDocs →

IEC 61131-3 §6.5 step + transition state machine for cyclic PLC sequences.

SFC: Bottle Filling SFC with 3 step(s), 2 transition(s). Bottle Filling T0 StartBtn T1 TankLevel >= 80.0 S0 Filling Done N FillValve_Closed N FillValve_Open N Confirm_Done DoneBtn → S0
Bottle filling sequence (SFC)
SFC: Order routing SFC with 5 step(s), 5 transition(s). Order routing IsExpressShipping TRUE IsStandardShipping TRUE T0 ProductOrdered S0 S_Pick S_Express S_Standard S_Ship N PickFromBin N PrepExpressBox N PrepStandardBox N CarrierPickup Shipped → S0
Order routing — express vs standard shipping (SFC)
SFC: Bake and cool concurrently SFC with 5 step(s), 3 transition(s). Bake and cool concurrently TRUE Bake_Done AND Cool_Done T0 BakeReady S0 S_Heat S_Bake S_Cool S_Done N Heater_On D Oven_Run T#15m L Cooler_On T#5m N AnnounceDone NOT BakeReady → S0
Bake & cool concurrent batch (SFC)
Single-line diagramsince v0.1.0 · upd v0.6.3§ IEEE Std 315 + ANSI device numberingsymbolsDocs →

Electrical power distribution single-line (one-line) diagram.

Commercial PV Interconnection Single-line diagram with 8 nodes and 7 connections Commercial PV Interconnection 480V 480V PV string conductors PV Array 250 kWdc Utility 480V DC Combiner 600 Vdc DC Disconnect 600 Vdc Grid-tie Inverter 200 kWac AC Disconnect 480V 400A Wh Production Meter 480V · Main Switchboard
Commercial solar PV interconnection
Utility + Generator Backup Single-line diagram with 8 nodes and 7 connections Utility + Generator Backup 480V 480V Utility 480V G Emergency Gen 500 kW 480V ATS ATS-1 800A 480V · Critical Load Bus CB1 200A CB2 200A Critical Load 1 100A Critical Load 2 100A
Generator + ATS backup power
Residential Consumer Unit — IEC 60364 Single-line diagram with 19 nodes and 18 connections Residential Consumer Unit — IEC 60364 230V 230V 1.5 mm² Cu PVC 2.5 mm² Cu PVC 2.5 mm² Cu PVC 4 mm² Cu PVC 4 mm² Cu PVC 6 mm² Cu XLPE 2.5 mm² Cu XLPE Service head 230V/63A 230V Wh kWh meter Main isolator 63A 6kA GFI Main RCD 63A / 30mA Type AC 230V · Consumer-unit busbar MCB lighting 6A B-curve MCB sockets ground floor 16A B-curve MCB sockets first floor 16A B-curve MCB kitchen ring 20A C-curve MCB water heater 20A C-curve GFI RCBO EV charger 32A / 30mA Type B MCB outdoor 10A B-curve Lighting circuit Sockets — ground floor Sockets — first floor Kitchen ring final Water heater 4.5 kW EV charger 7.4 kW Mode 3 Outdoor / garden
Residential consumer unit — generic IEC 60364
Vivienda — CGMP REBT ITC-BT-17 Single-line diagram with 17 nodes and 16 connections Vivienda — CGMP REBT ITC-BT-17 230V 230V 1.5 mm² Cu H07V-K 2.5 mm² Cu H07V-K 6 mm² Cu H07V-K 4 mm² Cu H07V-K 2.5 mm² Cu H07V-K 6 mm² Cu H07V-K Acometida 230V mono 230V Wh Contador + ICP 25A IGA 40A curva C, 6kA GFI Diferencial general 40A / 30mA Tipo A 230V · Embarrado CGMP PIA C1 10A curva C PIA C2 16A curva C PIA C3 25A curva C PIA C4 20A curva C PIA C5 16A curva C PIA C6 25A curva C C1 Iluminación C2 Tomas uso general C3 Cocina + horno C4 Lavadora / lavavajillas C5 Tomas baño y cocina C6 Aerotermia / climatización
Residential CGMP — Spanish REBT vivienda
Data Center 2N UPS Single-line diagram with 12 nodes and 12 connections Data Center 2N UPS 13.8kV 13.8kV/480V 480V Utility A 13.8kV Utility B 13.8kV TX-A 2500 kVA 13.8kV/480V TX-B 2500 kVA 13.8kV/480V 480V · Switchgear A 480V · Switchgear B UPS UPS A 1 MW UPS UPS B 1 MW ATS Static Transfer Switch 1600A PDU A PDU B Critical IT Load
Data center 2N UPS single-line
13.8 kV Substation Single-line diagram with 10 nodes and 9 connections 13.8 kV Substation 138 13.8 Grid 138 kV 138 · bus_hv xfmr1 kva: 15000 primary: 138 secondary: 13.8 13.8 · bus_mv brk1 brk2 brk3 Feeder 1 Feeder 2 Feeder 3
13.8 kV utility substation
P&ID (Piping & Instrumentation)since v0.3.0 · upd v0.6.3, v0.6.10§ ANSI/ISA-5.1-2009 + ISO 10628-1:2014symbolsDocs →

ISA-5.1 process equipment, valves, and instrument bubbles.

P&ID — Water Pump Flow Control ISA-5.1 / ISO 10628 P&ID rendered by Schematex Water Pump Flow Control Feed Tank Feed Pump V-101 Isolation FT 101 FIC 101
Pump with flow control loop (P&ID)
P&ID — Distillation Column T-201 ISA-5.1 / ISO 10628 P&ID rendered by Schematex Distillation Column T-201 T-201 Overhead Condenser Reflux Drum Reflux Pump Reboiler PSV-201 PT 201 LIC 201 TIC 201
Distillation column with reboiler and condenser
P&ID — High-Pressure Reactor Feed ISA-5.1 / ISO 10628 P&ID rendered by Schematex High-Pressure Reactor Feed Raw Material Tank Feed Pump P-201A/B Feed Pre-heater Reactor R-201 V-201 V-202 V-203 FT 201 FIC 201 TT 201 TIC 201 PT 201 PSHH 201
Reactor feed with multi-loop control and pressure safety (P&ID)
Breadboard / Physical wiringsince v0.4.0§ Fritzing visual conventions + Wokwi DSL precedent (no ISO standard exists for this view; see 26-BREADBOARD-STANDARD.md)Docs →

Fritzing-style breadboard view — physical wiring of Arduino / ESP32 / Pi prototypes.

Blink LED — Arduino Uno hello-world Breadboard wiring diagram generated by Schematex Blink LED — Arduino Uno hello-world 5 10 15 20 25 30 5 10 15 20 25 30 a a f f b b g g c c h h d d i i e e j j D13D12D11D10D9D8D7D6D5D4D3D2TXRXRST3V35VGNDVINA0A1A2A3A4A5Arduino Uno R1 220Ω D1 (red)
Blink LED on Arduino Uno
ESP32 + SSD1306 OLED I²C Breadboard wiring diagram generated by Schematex ESP32 + SSD1306 OLED I²C 5 10 15 20 25 30 5 10 15 20 25 30 a a f f b b g g c c h h d d i i e e j j 3V3GNDGPIO15GPIO2GPIO4GPIO5GPIO18GPIO19GPIO21GPIO22VINGNDGPIO13GPIO12GPIO14GPIO27GPIO26GPIO25GPIO33GPIO32ESP32 DevKit GNDVCCSCLSDAOLED 128×64
ESP32 + SSD1306 OLED I²C
HC-SR04 distance sensor + Arduino Uno Breadboard wiring diagram generated by Schematex HC-SR04 distance sensor + Arduino Uno 5 10 15 20 25 30 5 10 15 20 25 30 a a f f b b g g c c h h d d i i e e j j D13D12D11D10D9D8D7D6D5D4D3D2TXRXRST3V35VGNDVINA0A1A2A3A4A5Arduino Uno VCCTRIGECHOGNDHC-SR04
HC-SR04 distance sensor + Arduino Uno
Welding symbolssince v0.8.1§ AWS A2.4:2020 · ISO 2553:2019; see 47-WELDING-SYMBOL-STANDARD.mdDocs →

AWS A2.4 / ISO 2553 welding callouts — the reference-line skeleton with weld glyphs, dimensions, and supplementary symbols placed correct-by-construction.

Welding symbols — Bracket assembly Welding-symbol diagram (AWS) — 2 joint(s): gusset to column — arrow side: fillet weld size 8; other side: fillet weld; all-around; field weld; tail GMAW · splice plate (butt) — arrow side: V-groove weld; other side: backing weld; tail SMAW; E7018 Bracket assembly gusset to column — arrow side: fillet weld size 8; other side: fillet weld; all-around; field weld; tail GMAW 8 50-150 6 GMAW gusset to column splice plate (butt) — arrow side: V-groove weld; other side: backing weld; tail SMAW; E7018 (12) 60° root 3 G SMAW; E7018 splice plate (butt)
Welded bracket — fillet + V-groove callouts

Behavior Modeling

5
State diagramsince v0.3.0§ OMG UML 2.5.1 §14 + Harel (1987) statechartDocs →

UML 2.5 / Harel statechart with composite states and pseudo-states.

State Diagram — Traffic Light UML 2.5 / Harel statechart rendered by Schematex Traffic Light Red Green Yellow timer timer timer power_off
Traffic light (state diagram)
State Diagram — E-Commerce Order Lifecycle UML 2.5 / Harel statechart rendered by Schematex E-Commerce Order Lifecycle Processing AwaitingTransfer Picking Packing Shipped Delivered Failed Refunded Pending Cancelled Confirmed place_order [items_in_stock] / reserveInventory() cancel pay [method == "card"] [method == "wallet"] [method == "bank_transfer"] transfer_received [amount_correct] transfer_timeout picked / updateWarehouse() label_printed carrier_confirmed delivered / notifyCustomer() fulfillment_error return_request [within_30_days] / initiateRefund() retry [attempt < 3] retry [attempt >= 3] SLA: 48 h before timeout.
E-commerce order lifecycle (state diagram)
State Diagram UML 2.5 / Harel statechart rendered by Schematex Payment entry / startPaymentTimer() exit / stopPaymentTimer() Cart Checkout Authorizing Capturing Failed Captured Confirmed Cancelled begin_checkout submit_shipping [addressValid] / createIntent() edit_cart captured / sendReceipt() failed [retries < 3] / showError() failed [retries >= 3] authorized declined capture_ok capture_error
Checkout session with composite state and history
State Diagram — Subscription Lifecycle UML 2.5 / Harel statechart rendered by Schematex Subscription Lifecycle Active entry / provisionWorkspace() exit / syncEntitlements() GracePeriod Paused Trialing PastDue Incomplete Cancelled Current trial_end [payment_method_valid] / startBilling() trial_end [payment_method_missing] / requestPaymentMethod() cancel invoice_failed payment_succeeded / restoreAccess() grace_expired payment_succeeded / clearDunning() cancel_at_period_end pause [plan_allows_pause] / suspendBilling() resume / resumeBilling() cancel_now / revokeAccess() payment_method_added / retryInvoice() expires period_end reactivate [within_retention_window] / restoreSubscription() purge_after_retention
SaaS subscription lifecycle
UML use case diagramsince v0.4.3 · upd v0.5.0§ OMG UML 2.5.1 §18 visual subset; see 29-USECASE-STANDARD.mdDocs →

UML 2.5.1 use case diagram — captures what a system does and for whom: actors, use cases, a subject boundary, and include/extend/generalization.

Use Case Diagram — ATM Subject: ATM System. 2 actors, 4 use cases, 0 include, 0 extend. ATM ATM System Customer «actor» Bank Withdraw Cash Deposit Funds Check Balance Transfer Funds
ATM use case diagram (UML)
Use Case Diagram — Online Bookstore — Checkout Subject: Bookstore System. 3 actors, 7 use cases, 3 include, 1 extend. Online Bookstore — Checkout Bookstore System Customer «actor» Payment Gateway Warehouse Staff Browse Catalog Add to Cart Checkout extension points payment failed stock depleted Pay Cancel Order Ship Order Validate Card «include» «include» «extend» [payment failed] (extension point: payment failed) «include»
Online bookstore use case diagram (include + extend)
UML sequence diagramsince v0.5.1 · upd v0.6.2§ OMG UML 2.5.1 §17 (Interactions); see 33-SEQUENCE-STANDARD.mdDocs →

UML 2.5.1 §17 interaction diagram — shows how participants exchange messages over time (who calls whom, in what order): lifelines, activations, and all twelve combined fragments.

Sequence Diagram 2 participants, 3 messages, 0 combined fragments. Factory Worker «create» external trigger fire-and-forget
Object lifecycle — create, found, lost, destroy
Sequence Diagram — Login flow 4 participants, 8 messages, 1 combined fragments. Login flow User Web App Auth DB alt [credentials valid] [invalid] submit(credentials) verify(credentials) SELECT user row token 200 OK 401 error session cookie set
Login flow with an alt fragment
Sequence Diagram — OAuth 2.0 Authorization Code 5 participants, 16 messages, 1 combined fragments. OAuth 2.0 Authorization Code User Browser Web App Auth Server User Store alt [token exchange ok] [exchange failed] click "Sign in" GET /login 302 → Auth Server GET /authorize consent screen approve 302 + auth code GET /callback?code POST /token (code) load user profile access + refresh token Set-Cookie: session signed in 401 Unauthorized retry
OAuth 2.0 authorization-code login
Sequence Diagram — API request with combined fragments 6 participants, 12 messages, 5 combined fragments. API request with combined fragments Client API Gateway Auth Orders DB «queue» Events opt [idempotency key present] loop [1,3] par critical alt [token valid] [token invalid] ref Validate token 1. POST /orders 2. checkScopes() 3. scopes 4. lookupRequest(key) 5. previous result? 6. reserveInventory() 7. reservation result 8. OrderRequested 9. persistOrder() 10. commit ok 11. 201 Created 12. 401 Unauthorized
Combined fragments gallery
Sequence Diagram — Order processing (saga) 6 participants, 13 messages, 2 combined fragments. Order processing (saga) Customer API Gateway Order Service Payment Service Inventory Service «queue» Event Bus par alt [payment captured && stock reserved] [payment failed] ref Validate cart & price POST /orders createOrder() charge(card) reserve(items) paid reserved OrderConfirmed 201 Created confirmation release(items) OrderCancelled 402 Payment Required declined
Microservices order saga
Sequence Diagram — Checkout payment resilience 5 participants, 12 messages, 4 combined fragments. Checkout payment resilience Client Checkout API Circuit Breaker Payment Provider «queue» Fallback Queue break [authorized] alt [response before timeout] [timeout] loop [1,3] alt [breaker closed] [breaker open] 1. POST /checkout/pay 2. allowRequest() 3. permit 4. authorize(amount) 5. auth result 6. 200 Authorized 7. recordFailure(timeout) 8. enqueue retry context 9. 202 Pending verification 10. reject 11. enqueue deferred payment 12. 503 Retry later
Retry, timeout, and circuit breaker
Markov chainsince v0.8.0§ Norris, Markov Chains (1997) · Kemeny & Snell, Finite Markov Chains; see 42-MARKOV-CHAIN-STANDARD.mdDocs →

Discrete-time Markov chain — circles + probability arcs, with the stationary distribution and recurrent/transient/absorbing classification computed for you.

Markov chain — Customer lifecycle 3 states, 8 transitions. Classification: 3 recurrent, 0 transient, 0 absorbing. Stationary π: { Trial=0.197, Active=0.492, Churned=0.311 }. Customer lifecycle 0.4 0.5 0.1 0.8 0.05 0.15 0.7 0.3 Trial π=0.197 Active π=0.492 Churned π=0.311
Customer lifecycle (ergodic chain, stationary π)
Markov chain — Gambler's ruin 5 states, 8 transitions. Classification: 0 recurrent, 3 transient, 2 absorbing. Absorbing: Broke, Rich. Expected steps to absorption t: { S1=3, S2=4, S3=3 }. Absorption probabilities B: S1→(Broke=0.75, Rich=0.25); S2→(Broke=0.5, Rich=0.5); S3→(Broke=0.25, Rich=0.75). Gambler's ruin 1 1 0.5 0.5 0.5 0.5 0.5 0.5 $0 $4 S1 S2 S3
Gambler's ruin (absorbing chain)

Software / UML

2
UML Class Diagramsince v0.6.4§ OMG UML 2.5.1 §9–§11 (Classification / Classifiers / Associations) + ISO/IEC 19505-2:2012; see 36-UMLCLASS-STANDARD.mdDocs →

OMG UML 2.5.1 class diagram — classifiers (class / abstract / interface / enum / datatype / primitive) joined by the six relationship kinds, with visibility, multiplicity, and stereotypes.

Shape hierarchy UML class diagram: 1 interface, 1 abstract, 2 class; 1 realization, 2 generalization; 1 merged inheritance tree. Shape hierarchy «interface» Shape + area(): double + perimeter(): double AbstractShape # name: String + area(): double + perimeter(): double + describe(): String Circle + radius: double + area(): double + perimeter(): double Square + side: double + area(): double + perimeter(): double
Shape class hierarchy with an interface
UML class diagram UML class diagram: 2 class; 1 realization (1 warning). Repository<T> + cache: Map<String,List<int>> + count + findAll(): List<T> + findById(id: ID): Optional<T> + flush() «service» CrudService + repo: Repository<User> + save(e: User): User T
Generics and Mermaid-compatible syntax
Layered packages UML class diagram: 3 class; 2 directed. Layered packages Platform Auth Data UserService + login() + logout() Repository + find() + save() Gateway + route() delegates delegates delegates delegates
Packages and namespaces
Order model UML class diagram: 5 class; 1 composition, 1 aggregation, 1 association, 1 dependency. Order model Order - id: String + total: Money {readOnly} + count: int + place(): void LineItem + qty: int + subtotal(): Money Customer + name: String Address + city: String TaxPolicy + rate(c: Country): Percent 1..* contains contains 0..* has has 1 * places places uses uses
Order model — aggregation, composition, and dependency
Payment strategy UML class diagram: 1 enum, 1 interface, 4 class; 3 realization, 2 dependency; 1 merged inheritance tree. Payment strategy «enumeration» PaymentMethod CARD BANK_TRANSFER WALLET «interface» PaymentStrategy + authorize(amount: Money): AuthResult + capture(auth: AuthResult): Receipt «service» CheckoutService - strategies: Map<PaymentMethod, PaymentStr… + pay(method: PaymentMethod, amount: Money)… CardStrategy + authorize(amount: Money): AuthResult + capture(auth: AuthResult): Receipt BankStrategy + authorize(amount: Money): AuthResult + capture(auth: AuthResult): Receipt WalletStrategy + authorize(amount: Money): AuthResult + capture(auth: AuthResult): Receipt delegates to delegates to selects by selects by
Payment strategy pattern with enum + custom stereotype
Git commit graphsince v0.8.0§ Mermaid gitGraph syntax · git DAG model; see 43-GIT-GRAPH-STANDARD.mdDocs →

Branch-and-merge commit history on per-branch swimlanes — Mermaid gitGraph compatible.

Git commit graph Git commit graph: 11 commits across 4 branches, 4 merges, orientation LR. main develop feature/login hotfix init scaffold feature scaffold login UI login API 1-49dec0f polish v1.0 2-2cadf25 patch CVE v1.0.1 3-2b38c3a 4-885cbfb
Git Flow release history

Causality & Analysis

4
Fishbone (Ishikawa)since v0.1.0§ Ishikawa (1968) cause-and-effectDocs →

Ishikawa cause-and-effect diagram with categorised root causes.

Solder Joint Defect Spike — Fishbone diagram Ishikawa cause-and-effect diagram. Effect: 3.2% solder joint rejects. 6 categories. Solder Joint Defect Spike 3.2% solder joint rejects Man New operators on night shift Training checklist not signed Handover notes incomplete Material Solder paste past floor life PCB pads oxidized after storage Measurement AOI false accept rate rising X-ray sampling reduced Machine Reflow oven zone 4 drift Thermocouple calibration overdue Stencil printer squeegee worn Method Stencil aperture undersized Pick-and-place speed raised Environment Humidity above process window ESD straps failing audit
Manufacturing defect 6M fishbone
Fishbone diagram — Website traffic drop — Fishbone diagram Ishikawa cause-and-effect diagram. Effect: Traffic decline. 6 categories. Fishbone diagram — Website traffic drop Traffic decline Content Publishing frequency down Content too generic Keyword gaps Low-quality AI content Backlinks High-quality backlinks lost High ratio of low-quality links Referring domain growth stalled Low anchor text diversity Competition New competitors entering AI tools replacing search Weakening brand recall Competitors publishing faster Technical Core Web Vitals failing Crawl coverage drop Crawler blocked by WAF Missing structured data UX Bounce rate rising Poor mobile experience Slow above-fold load Excessive popup ads Algorithm Core Update penalty Weak E-E-A-T signals AI Overviews / SGE cutoff Search intent drift
Website traffic drop root-cause analysis
Venn / Eulersince v0.1.1§ Venn (1880) / Euler diagramsDocs →

Set-theoretic Venn / Euler diagram with 2, 3, or 4 sets.

Customer Segments — Q3 2025 Venn/Euler diagram "Customer Segments — Q3 2025": 3 sets, 7 regions. Customer Segments — Q3 2025 Set Email subscribers Set Paid users Set Mobile app users Email subscribers Paid users Mobile app users 1840 920 2100 650 12400 3200 8700
Customer segment overlap
Programming Paradigms Venn/Euler diagram "Programming Paradigms": 3 sets, 7 regions. Programming Paradigms Set Object-Oriented Set Functional Set Logic Object-Oriented Functional Logic 180 45 90 12 620 340 95
Programming paradigm overlap
Decision treesince v0.2.0§ Howard-Raiffa / CART-sklearn / taxonomyDocs →

Decision/classification tree with splits, probabilities, leaves.

Market Entry Influence diagram with 4 nodes and 4 arcs Market Entry Market demand Competitor response Enter market? Profit U=120
Market entry (influence diagram)
Oil Wildcatter Influence diagram with 4 nodes and 4 arcs Oil Wildcatter Seismic test Drill? Oil present Net profit U=42
Oil wildcatter (influence diagram)
Platform Vendor Choice Decision tree (decision mode) with 8 nodes and 7 edges Platform Vendor Choice Build in-house Managed SaaS vendor Hybrid approach p=60% p=40% p=50% p=50% Which vendor? EV=600,000 Project outcome EV=600,000 On-time delivery $900,000 Over budget / delayed $150,000 Predictable cost $500,000 Integration complexity EV=500,000 Smooth integration $700,000 Integration rework $300,000
Investment decision analysis
Iris CART Classifier Decision tree (ml mode) with 7 nodes and 6 edges Iris CART Classifier True False True False True False petal_length 2.45 gini = 0.67 samples = 150 Setosa gini = 0 samples = 50 value = 50 class = setosa petal_width 1.75 gini = 0.50 samples = 100 petal_length 4.95 gini = 0.17 samples = 54 Versicolor gini = 0.04 samples = 49 value = 49 class = versicolor Virginica gini = 0.32 samples = 5 value = 5 class = virginica Virginica gini = 0 samples = 45 value = 45 class = virginica
Iris CART decision tree
Customer Support Triage Decision tree (taxonomy mode) with 9 nodes and 8 edges Customer Support Triage yes no yes no yes no yes no Is the service completely down? Outage confirmed on status page? Follow incident protocol — page Check monitoring — open severity-1 ticket Is the issue affecting billing? Escalate to billing team — SLA breach risk Can user reproduce consistently? Collect HAR trace — file bug report Ask for screenshot — watch for recurrence
Support ticket triage
Causal Loop Diagramsince v0.8.0§ Sterman, Business Dynamics (2000) · Meadows, Thinking in Systems; see 41-CAUSAL-LOOP-STANDARD.mdDocs →

System-dynamics feedback map — signed causal links the engine reads to classify each loop as reinforcing (R) or balancing (B).

Urban traffic congestion Causal loop diagram "Urban traffic congestion": 6 variables, 7 causal links. 2 feedback loops: 0 reinforcing (R), 2 balancing (B). B1 "Congestion brake" (balancing, 1 negative link): Travel speed → Driving attractiveness → Number of cars → Congestion → Travel speed. B2 "Transit substitution" (balancing, 1 negative link): Number of cars → Congestion → Public transit use → Number of cars. Not in any loop: Road capacity. Urban traffic congestion + + + + + B1 Congestion brake B2 Transit substitution Road capacity Travel speed Driving attractiveness Number of cars Congestion Public transit use
Urban traffic congestion (two balancing loops)
Startup growth engine Causal loop diagram "Startup growth engine": 7 variables, 9 causal links. 3 feedback loops: 2 reinforcing (R), 1 balancing (B). R1 "Viral flywheel" (reinforcing, 0 negative links): Active users → Word of mouth → New signups → Active users. B1 "Scaling strain" (balancing, 1 negative link): Active users → Server load → App performance → Active users. R2 (reinforcing, 0 negative links): Active users → Revenue → Infra investment → App performance → Active users. Startup growth engine + + + + + + + + R1 Viral flywheel B1 Scaling strain R2 Active users Word of mouth New signups Server load App performance Revenue Infra investment
Startup growth engine (R and B loops)

Strategy

1
Matrix / quadrantsince v0.1.1 · upd v0.4.1, v0.8.1§ 2×2 / N×M quadrant conventionDocs →

2×2 / 3×3 / N×M matrix diagrams (Eisenhower, BCG, heatmap).

Matrix — This Week Matrix diagram (eisenhower template), quadrant mode, 0 point(s) This Week Do First • Ship hotfix • Customer demo prep Schedule • Write Q3 OKRs • Refactor auth layer Delegate • LinkedIn updates • Inbox zero Delete • Reorganize Slack channels
Eisenhower week prioritization
Matrix — Sprint Planning — Q2 Backlog Matrix diagram (impact-effort template), quadrant mode, 0 point(s) Sprint Planning — Q2 Backlog Quick Wins • Add bulk-delete to inbox • Surface error message inline • Fix mobile menu z-index bug Major Projects • Rebuild billing on new stripe API • Multi-tenant workspace support Fill-ins • Brand color audit • Update tooltip copy Thankless • Animated empty-state illustrations • Internal admin dashboard polish
Impact-effort feature prioritization
Matrix — Self vs. Team — Q2 Reflection Matrix diagram (johari template), quadrant mode, 0 point(s) Self vs. Team — Q2 Reflection Open / Arena • Strong technical instincts • Direct in code review • Patient with juniors Blind • Interrupts in meetings • Hard to read when stressed Hidden / Façade • Imposter syndrome about leadership • Anxiety about cross-team politics Unknown • Capacity for difficult conversations under pressure
Johari window — manager self-assessment
Punnett square — Eye color (Bb × Bb) Punnett square — monohybrid cross Bb × Bb; phenotype ratio 3:1 Eye color (Bb × Bb) Bb Bb B b B b BB Bb Bb bb Phenotype ratio 3:1 3 × Brown eyes 1 × Blue eyes Genotype ratio 2:1:1 — 2 Bb, 1 bb, 1 BB
Monohybrid cross Punnett square (3:1)
Matrix — Engineering — H1 Talent Review Matrix diagram (9-box template), quadrant mode, 0 point(s) Engineering — H1 Talent Review • Enigma • Samir K. (sr. eng) • Growth Employee • Priya R. (eng II) • Tomás L. (eng II) • Future Leader • Maya O. (sr. eng) • Dilemma • David C. (eng II) • Core Player • Lin H. (sr. eng) • Kofi A. (eng II) • High Impact • Reina S. (staff) • Under-performer • — PIP candidate — • Effective • Jordan P. (eng I) • Trusted Pro • Elena V. (staff)
9-box talent grid
Punnett square — Test cross (Bb × bb) Punnett square — monohybrid cross Bb × bb; phenotype ratio 1:1 Test cross (Bb × bb) Bb bb B b b b Bb bb Bb bb Phenotype ratio 1:1 2 × Blue 2 × Brown Genotype ratio 1:1 — 2 bb, 2 Bb
Test cross Punnett square (1:1)
SIPOC — Order fulfilment SIPOC scoping table — 2 supplier(s), 2 input(s), 4 process step(s), 2 output(s), 2 customer(s) Order fulfilment Suppliers Suppliers: Vendor, Warehouse Vendor Warehouse Inputs Inputs: PO, Stock levels PO Stock levels Process Process: Receive order, Pick, Pack, Ship 1. Receive order 2. Pick 3. Pack 4. Ship Outputs Outputs: Shipped package, Invoice Shipped package Invoice Customers Customers: End customer, Finance End customer Finance
Order fulfilment SIPOC
Matrix — Product Portfolio — FY26 Matrix diagram (bcg template), quadrant mode, 5 point(s) Product Portfolio — FY26 Question Marks Stars Cash Cows Dogs High Market Share Low Market Share Low Growth High Growth Platform SDK · (0.80, 0.80) · size 5 Platform SDK Legacy API · (0.85, 0.15) · size 4 Legacy API Mobile SDK · (0.25, 0.85) · size 3 Mobile SDK Self-serve billing · (0.35, 0.75) · size 2 Self-serve billing On-prem installer · (0.20, 0.15) · size 1 On-prem installer star cashcow question dog
BCG product portfolio
Punnett square — Seed shape &amp; colour (RrYy × RrYy) Punnett square — dihybrid cross RrYy × RrYy; phenotype ratio 9:3:3:1 Seed shape & colour (RrYy × RrYy) RrYy RrYy RY Ry rY ry RY Ry rY ry RRYY RRYy RrYY RrYy RRYy RRyy RrYy Rryy RrYY RrYy rrYY rrYy RrYy Rryy rrYy rryy Phenotype ratio 9:3:3:1 9 × Round, Yellow 3 × Wrinkled, Yellow 3 × Round, Green 1 × Wrinkled, Green Genotype ratio 4:2:2:2:2:1:1:1:1 — 9 distinct genotypes
Dihybrid cross Punnett square (9:3:3:1)
QFD House of Quality — Coffee maker QFD House of Quality — 3 customer requirement(s), 3 engineering characteristic(s), 5 relationship(s); technical importance computed per column Coffee maker Roof: engineering correlation matrix Fan RPM ↔ Heater watts: strong negative Fan RPM ↔ Insulation: no correlation Heater watts ↔ Insulation: positive Fan RPM Heater watts Insulation Wt Quiet operation (weight 5) Quiet operation 5 Brews fast (weight 3) Brews fast 3 Energy efficient (weight 4) Energy efficient 4 Quiet operation × Fan RPM = 9 Quiet operation × Insulation = 3 Brews fast × Heater watts = 9 Energy efficient × Heater watts = 3 Energy efficient × Insulation = 9 Computed technical importance per engineering characteristic Technical importance Σ(wt×rel) 45 39 51
Coffee maker House of Quality

Knowledge

1
Mindmapsince v0.1.1 · upd v0.2.2, v0.6.7§ Buzan radial + markmap-compat treeDocs →

Radial or markmap-style mindmap from markdown headings.

Reduce 30-day readmissions logic-right mindmap with 7 nodes Teach-back at bedside Med reconciliation Reliable discharge process Appointment within 7 days Post-discharge phone call Timely follow-up Reduce 30-day readmissions
Driver diagram — reduce 30-day readmissions
Remote work becomes default futures-wheel mindmap with 10 nodes Remote work becomes default Less commuting Lower carbon emissions Cheaper city living Distributed teams Async communication norms Global hiring pools Empty offices Commercial real estate slump Repurposed to housing
Futures wheel — remote work becomes default
Q4 Company OKRs map mindmap with 22 nodes 10 new qualified logos Win rate ≥ 25% Expand enterprise pipeline Net revenue retention ≥ 120% Seat adoption +40% Increase expansion Grow ARR 30% 100% API coverage Zero-downtime cutover Core migration Sub-5-min quickstart 95% doc satisfaction Developer experience Ship Platform v2 8 senior engineers 2 staff PMs Hiring Voluntary attrition < 5% eNPS ≥ 40 Retention Strengthen team Q4 Company OKRs
Quarterly OKRs mindmap
Product Launch Plan map mindmap with 27 nodes Direct competitors Pricing benchmarks Competitive analysis SMB customers Enterprise pilot Target segments Market readiness Core API complete Edge cases resolved Feature freeze Load testing Cache rules Geo routing CDN configuration Infrastructure Engineering Landing page live Email campaign TechCrunch pitch Newsletter sponsors Press outreach Go-to-market Week 1 signups Activation rate NPS at day 30 Success metrics Product Launch Plan
Product launch plan mindmap

Research

1
PRISMA 2020 flow diagramsince v0.5.0§ PRISMA 2020 (Page MJ et al., BMJ 2021;372:n71); see 28-PRISMA-STANDARD.mdDocs →

PRISMA 2020 — the mandatory four-row flow diagram for systematic reviews and meta-analyses.

Effect of exercise on chronic low-back pain — SR PRISMA 2020 flow diagram (2020-single, systematic-review) — 7 boxes, 6 arrows Effect of exercise on chronic low-back pain — SR Identification Screening Included Identification of studies via databases and registers Records identified from: PubMed (n = 600) Embase (n = 450) Cochrane (n = 184) Web of Science (n = 184) Total (n = 1,418) Records removed before screening Duplicate records removed (n = 318) Records screened n = 1,100 Records excluded n = 870 irrelevant title (n = 750) non-English (n = 120) Reports assessed for eligibility n = 230 Reports excluded, with reasons: n = 195 wrong population (n = 80) wrong intervention (n = 60) wrong outcome (n = 55) Studies included in review Studies included (n = 35) Reports of included studies (n = 38)
PRISMA 2020 systematic review (single pipeline)
Effect of yoga on chronic back pain — SR PRISMA 2020 flow diagram (2020-dual, systematic-review) — 8 boxes, 7 arrows Effect of yoga on chronic back pain — SR Identification Screening Included Identification of studies via databases and registers Identification of studies via other methods Records identified from: PubMed (n = 600) Embase (n = 450) Cochrane (n = 184) Total (n = 1,234) Records removed before screening Duplicate records removed (n = 254) Identification of studies via other methods citation-search (n = 30) hand-search (n = 20) expert-recommendation (n = 6) Total (n = 56) Records screened n = 1,036 Reports sought for retrieval n = 226 Reports not retrieved (n = 12) Records excluded n = 810 duplicate (n = 120) irrelevant title (n = 560) non-English (n = 130) Reports assessed for eligibility n = 214 Reports excluded, with reasons: n = 191 wrong population (n = 80) wrong intervention (n = 60) wrong outcome (n = 51) Studies included in review Studies included (n = 23) Reports of included studies (n = 25)
PRISMA 2020 dual pipeline (databases + other methods)

Project Management

2
PERT / CPM networksince v0.6.0§ PMI PMBOK 7 + Moder 1983 (AON/PDM); see 32-PERT-STANDARD.mdDocs →

Activity-on-node project schedule that computes ES/EF/LS/LF, slack, and the critical path.

PERT network — Software project (AOA) 10 activities, project duration 70 days, critical path A → C → F → H → J. Software project (AOA) create schedule 10 buy hardware 5 programming 20 installation 5 conversion 15 test code 20 write manual 15 test system 10 training 5 user test 10 1 2 3 4 5 6 7 8 9 10 11 12 13 Project duration 70 days · 10 tasks · 10 dependencies · 5 critical Critical path: A → C → F → H → J
Activity-on-arrow (AOA) network
PERT network — Q3 Product Launch 7 activities, project duration 37 days, critical path A → C → D → E → G. Q3 Product Launch ES 0 DUR 5 EF 5 0 LS 0 SLACK 5 LF Market research A ES 5 DUR 15 EF 20 5 LS 0 SLACK 20 LF Backend API C ES 5 DUR 8 EF 13 12 LS 7 SLACK 20 LF Design mockups B ES 20 DUR 10 EF 30 20 LS 0 SLACK 30 LF Frontend build D ES 13 DUR 7 EF 20 28 LS 15 SLACK 35 LF Marketing collateral F ES 30 DUR 5 EF 35 30 LS 0 SLACK 35 LF QA / testing E ES 35 DUR 2 EF 37 35 LS 0 SLACK 37 LF Launch event G Project duration 37 days · 7 tasks · 8 dependencies · 5 critical Critical path: A → C → D → E → G
Q3 product launch PERT/CPM network
PERT network — Online Shop Project 8 activities, project duration 40 days, critical path T2 → T3 → T4 → T7 → T8. Online Shop Project Customer Account Shopping Site Shopping Cart Testing ES 0 DUR 3 EF 3 27 LS 27 SLACK 30 LF Support Account Deletion T1 ES 0 DUR 8 EF 8 0 LS 0 SLACK 8 LF Design a New Theme T2 ES 8 DUR 15 EF 23 8 LS 0 SLACK 23 LF Apply New Theme to the Site T3 ES 23 DUR 7 EF 30 23 LS 0 SLACK 30 LF Improve Searching T4 ES 8 DUR 8 EF 16 16 LS 8 SLACK 24 LF Enhance Shopping Cart Functionality T5 ES 16 DUR 6 EF 22 24 LS 8 SLACK 30 LF Enhance Shopping Cart Checkout T6 ES 30 DUR 2 EF 32 30 LS 0 SLACK 32 LF Ready Testing Environment T7 ES 32 DUR 8 EF 40 32 LS 0 SLACK 40 LF Test Online Shop T8 Project duration 40 days · 8 tasks · 8 dependencies · 5 critical Critical path: T2 → T3 → T4 → T7 → T8
PERT swimlanes grouped by team
PERT network — Three-point project 4 activities, project duration 17.83 days, critical path A → B → C → D. Three-point project ES 0 DUR 3.17 EF 3.17 0 LS 0 SLACK 3.17 LF Spec A σ=0.5 ES 3.17 DUR 8.5 EF 11.67 3.17 LS 0 SLACK 11.67 LF Build B σ=1.5 ES 11.67 DUR 4.17 EF 15.83 11.67 LS 0 SLACK 15.83 LF Test C σ=0.5 ES 15.83 DUR 2 EF 17.83 15.83 LS 0 SLACK 17.83 LF Deploy D σ=0.33 Project duration 17.83 days · 4 tasks · 3 dependencies · 4 critical · σ ≈ 1.69 Critical path: A → B → C → D
Three-point (PERT) estimation with variance
PERT network — Data-centre migration 10 activities, project duration 52 days, critical path A → C → D → F → G → H → I → J. Data-centre migration 0 5 10 15 20 25 30 35 40 45 50 Inventory systems A ES 0 EF 5 slack 0 Stakeholder review B ES 1 EF 7 slack 0 Vendor selection C ES 7 EF 15 slack 0 Architecture D ES 15 EF 25 slack 0 Procurement E ES 17 EF 29 slack 6 Code refactor F ES 25 EF 40 slack 0 Pilot env G ES 35 EF 40 slack 0 Pilot run H ES 40 EF 47 slack 0 Cutover @ 47 Hypercare J ES 47 EF 52 slack 0 SS+1d FS+2d FF Project duration 52 days · 10 tasks · 11 dependencies · 9 critical Critical path: A → C → D → F → G → H → I → J
Time-scaled migration plan (network-Gantt)
IDEF0 function modelsince v0.8.0§ FIPS PUB 183 (1993) · SADT (Ross); see 45-IDEF0-STANDARD.mdDocs →

Federal function-modelling standard — boxes are activities, arrows are positional (the ICOM rule: Input-left, Control-top, Output-right, Mechanism-bottom).

Fulfil customer order IDEF0 function model "Fulfil customer order" (node A0): 3 functions on a diagonal staircase. ICOM arrows: 4 input, 3 control, 3 mechanism, 2 output. Boxes: 1. Validate order (A1); 2. Pick and pack (A2); 3. Ship and invoice (A3). Fulfil customer order Customer order I1 Credit policy C1 Order management system M1 Validated order Inventory I2 Picking rules C2 Warehouse staff M2 Packed shipment Carrier contract C3 Shipping carrier M3 Delivered order O1 Invoice O2 Validate order 1 Pick and pack 2 Ship and invoice 3 NODE A0 TITLE Fulfil customer order NUMBER
IDEF0 A0 — fulfil customer order

Concurrency

1
Petri netsince v0.6.0§ Murata 1989 + ISO/IEC 15909-1 (place/transition net); see 34-PETRINET-STANDARD.mdDocs →

Place/transition net that computes the dynamics — enabled transitions and token firing, not just shapes.

Petri net — After fire: T1 3 places, 2 transitions, 4 arcs. Marking {P2:1}. Enabled: T2. Class: state machine, workflow net. After fire: T1 P1 P2 P3 T1 T2
Firing a transition advances the marking
Petri net — Classic 4 places, 2 transitions, 7 arcs. Marking {P1:1, P3:2, P4:1}. Enabled: T1. Classic P1 P2 P3 P4 T1 T2
The classic Petri net — concurrency with feedback
Petri net — Mutual Exclusion — two processes, one resource 5 places, 4 transitions, 12 arcs. Marking {idleA:1, idleB:1, mutex:1}. Enabled: enterA, enterB. Mutual Exclusion — two processes, one resource idleA A idle idleB B idle mutex resource critA A critical critB B critical enterA exitA enterB exitB
Mutual exclusion with a shared resource
Petri net — Order workflow 6 places, 4 transitions, 10 arcs. Marking {in:1}. Enabled: split. Class: workflow net. Order workflow in received pick invoice packed billed out shipped split pack bill ship
Order-fulfilment workflow net (WF-net)
Petri net — Arc Types 5 places, 3 transitions, 10 arcs. Marking {Idle:1, Permit:1, Buffer:2}. Enabled: Start. Arc Types 2 Idle Busy Fault Permit Buffer K=3 Start Complete Reset
Petri net arc types
Petri net — Producer / Consumer (bounded buffer) 4 places, 2 transitions, 8 arcs. Marking {pReady:1, free:3, cReady:1}. Enabled: produce. Class: marked graph. Producer / Consumer (bounded buffer) pReady producer ready free free slots used used slots K=3 cReady consumer ready produce deposit consume withdraw λ=0.8
Producer / consumer with a bounded buffer

Risk & Reliability

4
Fault Tree Analysissince v0.6.5§ NUREG-0492 Fault Tree Handbook + IEC 61025:2006 + NASA FT Handbook 2002; MOCUS cut sets (Fussell-Vesely 1972); see 37-FAULT-TREE-STANDARD.mdDocs →

Deductive top-down reliability analysis — decompose one undesired top event through Boolean AND/OR/voting gates to basic component failures; the engine computes the minimal cut sets and the top-event probability.

Both pumps fail Fault tree for "Both redundant pumps fail": 1 top, 2 basic. 1 minimal cut set: {PA, PB}. P(top) = 1.00e-4 (rare). Both pumps fail Both redundant pumpsfail PA Pump A fails p=0.01 PB Pump B fails p=0.01 P(top) = 1.00e-4 (rare)
Redundant pump failure (AND gate)
Product not removed Fault tree for "Failure to remove product": 1 top, 3 intermediate, 4 basic. 2 minimal cut sets: {CDM}, {MSF}. Single points of failure: CDM, MSF. P(top) = 0.0044 (rare). Product not removed Failure to removeproduct Arm jams or collides MSF Manipulator system … p=0.0035 Loss of positionfeedback ESF Encoder sensor fail… p=0.0021 RCF Resolver cable fault p=0.0012 Wrong slot commanded CDM Controller command … p=9.00e-4 MSF Manipulator system … p=0.0035 P(top) = 0.0044 (rare)
Repeated event with cut-set absorption
Water overheating Fault tree for "Water overheating": 1 top, 2 intermediate, 5 basic. 4 minimal cut sets: {C}, {D}, {E}, {A, B}. Single points of failure: C, D, E. P(top) = 0.371 (rare). Water overheating Water overheating Circuit failure andno warning lamp A Chip failure p=0.05 B Warning lamp burned p=0.03 E Booster failure p=0.02 No voltage at input C No burn in network p=0.12 D Fuse blown p=0.23 P(top) = 0.371 (rare)
Water overheating (classic textbook tree)
Vessel ruptures Fault tree for "Pressure vessel ruptures": 1 top, 2 intermediate, 3 basic, 1 house, 1 undeveloped. 1 minimal cut set: {PRV_A, PRV_B, PUMP}. P(top) = 1.60e-6 (mcub). Event "EXT" is declared but referenced by no gate (unconnected). Vessel ruptures Heaterenergised 2/2 Pressure vesselruptures Sustainedover-pressure PUMP Pump runaway p=0.004 Both reliefs fail PRV_A Relief A stuck p=0.02 PRV_B Relief B stuck p=0.02 P(top) = 1.60e-6 (mcub)
Pressure vessel rupture (full vocabulary)
Bowtie risk diagramsince v0.6.6§ CCPS / Energy Institute 2018 (Bow Ties in Risk Management) + IEC 31010:2019 §B.4.6 + ICAO Doc 9859; Swiss-cheese lineage (Reason 1990); see 38-BOWTIE-STANDARD.mdDocs →

Barrier-based risk management — one hazard's top event (the knot) with threats fanning in through preventative barriers on the left and consequences fanning out through mitigative barriers on the right, the whole shaped like a bow tie.

Working at height Bowtie: hazard "Working at height", top event "Person falls from height"; 2 threats, 2 consequences, 9 barriers, 1 escalation factor. Working at height Personfalls fromheight Working at height Guardrail removedfor access Permit-to-worksystem Temporary edgeprotection Edge protectionnot inspected Pre-useinspection regime Spotter /banksman Fragile roofsurface Crawling boards +signage Roof-access riskassessment Fatality Fall-arrestharness + lanyard Rescue plan +first aid Serious injury Safety nettingbelow On-site medic +evacuation Threat Barrier (prevent / mitigate) Top event Consequence Escalation factor
Working at height — fall from height
Hot work — fire bowtie Bowtie: hazard "Hot work near flammable materials", top event "Ignition of flammable atmosphere"; 2 threats, 2 consequences, 7 barriers, 2 escalation factors. Hot work — fire bowtie Ignition offlammableatmosphere Hot work near flammablematerials Sparks / hot slag Hot-work permit Fire watch Fire watch leavespost early Post-workmonitoring period(60 min) Static discharge Bonding +grounding Antistatic PPE Flash fire Fixed firesuppression Suppressionisolated formaintenance Impairmentregister + MoC Asset loss Fire-ratedseparation Business-continuityplan Threat Barrier (prevent / mitigate) Top event Consequence Escalation factor
Hot work — ignition of flammable atmosphere
LPG storage — loss of containment Bowtie: hazard "LPG stored under pressure", top event "Loss of containment"; 3 threats, 3 consequences, 12 barriers. LPG storage — loss of containment Loss ofcontainment LPG stored under pressure Corrosion ofvessel wall Corrosion-resistantcoating UT thicknessinspection Overpressureduring filling High-pressuretrip (SIL 2) Pressure reliefvalve Mechanical impact(vehicle) Bollards /vehicle barriers Site speed limit+ banksman Jet fire Gas detection +ESD Deluge / waterspray Vapour cloudexplosion Ignition-sourcecontrol (ATEX) Blast-resistantcontrol room Toxic /asphyxiationexposure Personal gasmonitors Emergencyevacuation plan Threat Barrier (prevent / mitigate) Top event Consequence
LPG storage — loss of containment
Runway excursion Bowtie: hazard "Aircraft landing in adverse conditions", top event "Runway excursion on landing"; 3 threats, 2 consequences, 10 barriers. Runway excursion Runwayexcursionon landing Aircraft landing in adverseconditions Unstable approach Stabilised-approachgate (go-aroundpolicy) Approachmonitoring +callouts Contaminatedrunway Runway conditionreporting (RCR) Landingperformanceassessment Excessive landingspeed Speed / energymanagement SOP Autobrakeselection Hull damage Runway end safetyarea (RESA) Arrestor bed(EMAS) Injuries /fatalities Cabin-crew brace+ evacuation Airport emergencyresponse Threat Barrier (prevent / mitigate) Top event Consequence
Runway excursion (aviation SMS)
Event Tree Analysissince v0.8.0§ IEC 62502:2010 · NUREG/CR-2300 (PRA) · ISO 31010 Annex B; see 39-EVENT-TREE-STANDARD.mdDocs →

Forward-looking risk: one initiating event branches through each safety function into outcome sequences, with computed path frequencies.

Flammable release Event tree for "Loss of containment" (f₀ = 0.02): 3 functions, 4 sequences. Safe shutdown: 0.01197. Jet fire: 0.00513. Large dispersion: 0.0019. Vapour cloud explosion: 0.001. Dominant sequence: "Safe shutdown" [1s 2s 3s] at 0.01197. Flammable release Initiating Event Gas detection alarms Emergency isolation No ignition source Outcome Frequency Loss of containment f₀ = 0.02 Success (1s) 0.95 Success (2s) 0.9 Success (3s) 0.7 Failure (3f) 0.3 Failure (2f) 0.1 Failure (1f) 0.05 Safe shutdown 0.01197 · 1s 2s 3s Jet fire 0.00513 · 1s 2s 3f Large dispersion 0.0019 · 1s 2f Vapour cloud explosion 0.001 · 1f
Flammable release event tree (process QRA)
Large LOCA Event tree for "Large-break LOCA" (f₀ = 1.000e-4): 4 functions, 5 sequences. OK: 9.644e-5. Late release: 2.463e-6 (Σ of 2 sequences). Early release: 9.990e-7. Core damage: 1.000e-7. Dominant sequence: "OK" [1s 2s 3s 4s] at 9.644e-5. Large LOCA Initiating Event Reactor trips ECCS injection Containment heat removal Containment integrity Outcome Frequency Large-break LOCA f₀ = 1.000e-4 Success (1s) 0.999 Success (2s) 0.99 Success (3s) 0.98 Success (4s) 0.995 Failure (4f) 0.005 Failure (3f) 0.02 Failure (2f) 0.01 Failure (1f) 0.001 OK 9.644e-5 · 1s 2s 3s 4s Late release 4.846e-7 · 1s 2s 3s 4f Late release 1.978e-6 · 1s 2s 3f Early release 9.990e-7 · 1s 2f Core damage 1.000e-7 · 1f
Large LOCA event tree (reactor PRA)
FMEA (Failure Mode and Effects Analysis)since v0.8.0§ AIAG-VDA FMEA Handbook (2019) · IEC 60812:2018 · SAE J1739 · MIL-STD-1629A; see 40-FMEA-STANDARD.mdDocs →

The reliability worksheet that computes its own risk — RPN = S×O×D plus AIAG-VDA Action Priority, ranked and colour-coded.

Injection moulding PFMEA FMEA worksheet (process); 3 failure-mode row(s); ranked by RPN; highest risk: "Warpage" S6·O6·D7 → RPN 252, AP Medium (action should be taken); 3 flagged. Injection moulding PFMEA Flag: rpn > 100 · Rank: RPN # Item Function Failure Mode Effect(s) S Cause(s) O Current Controls D RPN AP 1 Cooling step — Solidify part to spec Warpage Out-of-tolerance dimension 6 Uneven cooling channel flow 6 D: CMM sampling 7 252 Mediu m 2 Incomplete part scrapped 7 Injection pressure too low 5 P: Pressure setpoint lock D: Vision check 4 140 Mediu m 3 Incomplete part scrapped 7 Blocked gate 3 D: Cycle-time monitor 6 126 Mediu m Mould fill step — Fill cavity with melt Short shot
Injection-moulding PFMEA
EV battery pack DFMEA FMEA worksheet (design); 4 failure-mode row(s); ranked by AP; highest risk: "Thermal runaway" S10·O3·D4 → RPN 120, AP High (action needed); 2 flagged. EV battery pack DFMEA Number: DFMEA-2026-014 Flag: ap >= High · Rank: AP # Item Function Failure Mode Effect(s) S Cause(s) O Current Controls D RPN AP 1 Pack fire / occupant injury 10 Internal short from dendrite growth 3 P: Cell qualification D: In-line CT scan 4 120 High 2 Pack fire / occupant injury 10 Overcharge past cutoff 2 P: BMS voltage clamp D: Redundant voltage sense 3 60 High 3 Busbar joint — Conduct current between modules High-resistance connection Local overheating 8 Loose torque on weld 4 D: End-of-line resistance test 4 128 Mediu m 4 Cell module — Store and deliver energy Capacity fade Reduced range 6 Electrolyte depletion 5 D: Periodic SOH estimate 6 180 Low Cell module — Store and deliver energy Thermal runaway
EV battery pack DFMEA

Network & Infrastructure

2
Network topologysince v0.6.0§ Cisco-convention topology icons + hierarchical/spine-leaf models + ANSI/TIA-606 + ONVIF; see 35-NETWORK-STANDARD.mdsymbolsDocs →

IT / CCTV network topology with Cisco-convention device icons, typed links, subnets/VLANs, and topology-correct layout.

Network diagram — Branch LAN - Star Layout 6 devices, 5 links, 0 boundaries. Topology: star. Links: 4 copper, 1 poe. Branch LAN - Star Layout 1G Access · VLAN 10 · 1G Access · VLAN 10 · 1G Access · VLAN 20 · 1G VLAN 30 · 1G · PoE Gateway Access Switch Admin PC Laptop Printer Wi-Fi AP
Network layout modes
Network diagram — Link types 7 devices, 6 links, 0 boundaries. Topology: tree. Links: 1 fiber, 1 lag, 1 wireless, 1 copper, 1 poe, 1 vpn. Link types 10G Gi0/1 Gi1/0/1 20G Trunk · VLAN 10,20 · 1G PoE VPN · site-to-site Core Sw A Sw B AP s1 c1 VPN VPN GW
Every link type on one fabric
Network diagram — DC Fabric 9 devices, 11 links, 0 boundaries. Topology: spine-leaf. Links: 11 copper. DC Fabric 25G 25G 25G h1 h2 h3 sp1 sp2 lf1 lf2 lf3 lf4
Spine-leaf data-center fabric
Network diagram — Branch Office 6 devices, 5 links, 4 boundaries. Topology: hierarchical. Links: 1 serial, 4 copper. Branch Office HQ Building DMZ 10.0.10.0/24 MDF Rack 10G Trunk · VLAN 10 Internet fw1 core1 Web Server a1 User PC 10.0.10.50
Physical and logical boundaries in one diagram
Network diagram — Acme HQ — CCTV 10 devices, 9 links, 1 boundaries. Topology: hierarchical. Links: 1 serial, 1 fiber, 4 copper, 3 poe. Acme HQ — CCTV 192.168.20.0/24 ISP 1Gbps 10G Trunk · VLAN 20 · 1G Trunk · VLAN 20 · 1G 1G PoE PoE PoE Internet Perimeter FW Core SW PoE PoE Switch A PoE PoE Switch B NVR Video Recorder Guard Station Lobby Dome 192.168.20.11 Gate PTZ 192.168.20.12 Dock Bullet 192.168.20.13
CCTV camera network topology
Network diagram — Driscoll Campus 12 devices, 11 links, 0 boundaries. Topology: hierarchical. Links: 9 copper, 1 serial, 1 lag. Driscoll Campus 10G 40G Trunk · VLAN 100 Internet WAN Core Firewall Edge Rtr 1 Core SW 1 Core SW 2 Dist A Dist B ×4 Server Farm a1 a2 a3
Three-tier enterprise campus network
Network diagram — Zero-trust SaaS VPC 10 devices, 10 links, 4 boundaries. Topology: hierarchical. Links: 1 fiber, 4 vpn, 5 copper. Warnings: trunk link edgeproxy–fw connects no switch-class device (line 28). Zero-trust SaaS VPC DMZ 10.20.10.0/24 10.20.30.0/24 Admin Zone 10G VPN VPN · OIDC VPN · device posture 1G Trunk · VLAN 110 Access · VLAN 210 · 1G Access · VLAN 210 · 1G Access · VLAN 230 · 1G VPN Internet Identity Provider VPN Client VPN Segmentation FW LB Public ALB PXY Reverse Proxy API 1 10.20.10.11 API 2 10.20.10.12 Postgres HA 10.20.30.20 Admin Laptop
Zero-trust cloud VPC topology
Threat model (DFD + STRIDE)since v0.8.0§ Shostack, Threat Modeling (2014) STRIDE-per-element · Microsoft SDL · base DFD DeMarco/Yourdon; see 46-THREAT-MODEL-STRIDE-STANDARD.md + 31-DFD-STANDARD.mdDocs →

Security data-flow diagram where the engine annotates each element with its applicable STRIDE threats and flags every flow that crosses a trust boundary.

E-commerce checkout STRIDE threat model: 2 external entities, 2 process(es), 2 data store(s), 5 data flow(s). 3 boundary-crossing flow(s): Customer→1.0, 1.0→2.0, 2.0→Payment_Gateway. Customer (external) → Spoofing, Repudiation. Payment_Gateway (external) → Spoofing, Repudiation. 1.0 (process) → Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, Elevation of privilege. 2.0 (process) → Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, Elevation of privilege. D1 (store) → Tampering, Information disclosure, Denial of service. D2 (store) → Tampering, Repudiation, Information disclosure, Denial of service. E-commerce checkout Internet DMZ Internal HTTPS Checkout Place order Write order Charge card Order event Customer SR 1.0Web App STRIDE 2.0Order Service STRIDE Payment Gateway SR Orders DB TID Audit TRID
E-commerce checkout threat model (STRIDE)

General

2
Flowchartsince v0.1.1 · upd v0.2.0, v0.2.5, v0.3.0, v0.3.1§ Sugiyama layered DAG + orthogonal routingsymbolsDocs →

Generic flowchart with start/end/decision/process nodes.

Flowchart Flowchart with 14 nodes and 16 edges. commit → build build → unit unit → fail: No No unit → scan: Yes Yes scan → vuln vuln → fail: Yes Yes vuln → stage: No No stage → smoke smoke → fail: No No smoke → approve: Yes Yes approve → wait: No No approve → prod: Yes Yes prod → health health → done: Yes Yes health → rollback: No No rollback → done Push to main Push to main Build artifact Build artifact Unit tests pass? Unit tests pass? Security scan Security scan High-severity CVEs? High-severity CVEs? Deploy to staging Deploy to staging Smoke tests green? Smoke tests green? Fail build Fail build Manual approval? Manual approval? Await approver Await approver Deploy to production Deploy to production Post-deploy health check? Post-deploy health check? Automatic rollback Automatic rollback Release complete Release complete
CI/CD pipeline with gated deploy
Flowchart Flowchart with 14 nodes and 18 edges. start → intake intake → docs docs → request: No No request → docs: Resubmitted Resubmitted docs → coverage: Yes Yes coverage → deny1: No No deny1 → close coverage → fraud: Yes Yes fraud → review: Yes Yes review → liability fraud → liability: No No liability → denial: No No denial → close liability → estimate: Yes Yes estimate → approve approve → estimate: Needs changes Needs changes approve → pay: Approved Approved pay → close Claim submitted Claim submitted Capture FNOL data Capture FNOL data Documents complete? Documents complete? Request missing documents Request missing documents Policy active on loss date? Policy active on loss date? Issue coverage denial Issue coverage denial Fraud score high? Fraud score high? Manual SIU review Manual SIU review Liability accepted? Liability accepted? Send denial letter Send denial letter Calculate covered amount Calculate covered amount Adjuster approval? Adjuster approval? Payment ledger Payment ledger Close claim Close claim
Insurance claim adjudication
Flowchart Flowchart with 9 nodes and 10 edges. start → validate validate → reserve: Yes Yes validate → notify: No No notify → done reserve → payment payment → ship: Yes Yes payment → cancel: No No ship → confirm confirm → done cancel → done New order received New order received Inventory available? Inventory available? Reserve items Reserve items Notify customer Notify customer Payment authorized? Payment authorized? Ship order Ship order Cancel & release Cancel & release Send confirmation email Send confirmation email End End
E-commerce order fulfillment
Timelinesince v0.2.0 · upd v0.3.1§ Timeline convention with era bandsDocs →

Horizontal or vertical timeline with events, eras, milestones.

Timeline — Acme — First Five Years Schematex timeline diagram Acme — First Five Years Founders meet at Y Combin…2020-06 Incorporation + pre-seed …2020-11 First engineer hired2021-04 Product beta — 50 design …2021-09 Seed round — $6M2022-03 Team reaches 20 people2022-11 Platform v1 GA2023-05 Series A — $22M2023-10 100th enterprise customer2024-06 Platform v2 launched2025-01 2021 2021 2022 2022 2023 2023 2024 2024 2025 2025
Company milestone history
Timeline — Smith v. Acme - Case Timeline Schematex timeline diagram Smith v. Acme - Case Timeline Complaint filed2025-01-10 Answer due2025-02-07 Plaintiff deposition2025-04-15 Expert reports exchanged2025-05-22 Summary judgment motion2025-07-15 Mediation2025-08-20 Trial setting2025-10-06 2025 2025 2025 2025 2025 2026 2026
Litigation case timeline
Timeline — Platform v2 Launch Schematex timeline diagram Platform v2 Launch engineering design marketing Engineering build Design polish Marketing collateral QA hardening Press embargo …Feature freeze Public launch Teams engineering design marketing 2026 2026 2026 2026 2026
Product launch timeline