Open standards & artifacts for accountable systems.

Standard

Permanent link /standards/micro-diagram-language

Micro-diagram language specification

Canonical shapes, line styles, and axes for explaining accountable-system diagrams.

Why this exists

Keep diagrams consistent and legible.

Every diagram should be explainable using this spec alone, with grayscale-friendly symbols and unambiguous roles.

Scholarly metadata

Authorship

Contact: standards@ethotechnics.org

Publication details

  • Published: Feb 1, 2026
  • Last updated: Feb 1, 2026
  • Version: v1.0.0
  • DOI: Pending Zenodo deposit

License: CC BY 4.0

Credit Ethotechnics Institute Ethotechnics Diagram Council, include the page title + version, and link to the canonical permalink.

Archive snapshot: Wayback capture

Changelog

  • v1.0.0 · 2026-02-01 — Defined canonical shapes, line semantics, and example diagrams.

Canonical shapes

Shapes define roles and boundaries.

Use these forms to avoid semantic drift across diagrams.

State

Rounded rectangle

A discrete system state, status, or lifecycle stage.

Agent

Circle

A human, team, or automated agent with agency.

Boundary

Dashed frame

A scope boundary for policy, jurisdiction, or system limits.

Authority

Shield

The binding authority that can enforce or reverse outcomes.

Line styles

Line semantics denote force, authority, and contingency.

Keep weights consistent and use grayscale-friendly contrast.

Causal

Solid arrow

Shows direct causality or irreversible action.

Authority

Double stroke

Marks decisions that bind policy or governance.

Contingent

Dashed arrow

Shows a possible, conditional, or reversible path.

Axes

Axes are explicit in every diagram.

Axis labels make time, authority, and burden visible at a glance.

  • Time: left-to-right (start → completion) with clock markers.
  • Authority: bottom-to-top (user → system → binding authority).
  • Burden: thickness or shaded bands show cumulative time tax.

Example

Execution vs redress clocks.

Show how system execution can outrun human redress windows.

<rect class="state" />
<line class="causal" />
<rect class="boundary" />
<line class="contingent" />

Example

Stoppability vs reversibility.

Use a solid stop for immediate halt and a dashed return for reversal windows.

<circle class="agent" />
<rect class="state" />
<line class="causal" />
<line class="contingent" />

Citations

Cite this diagram language.

Reuse the spec verbatim to keep future visuals aligned.

Copy citation (APA/BibTeX)

Cite this diagram language Formats: APA, MLA, Chicago, BibTeX, RIS

Version

v1.0.0

Last updated

Feb 1, 2026

DOI

Pending Zenodo deposit

APA

Ethotechnics Diagram Council. (2026). Micro-diagram language specification. Ethotechnics Institute. https://ethotechnics.org/standards/micro-diagram-language

MLA

Ethotechnics Diagram Council. "Micro-diagram language specification." Ethotechnics Institute, 2026, https://ethotechnics.org/standards/micro-diagram-language.

Chicago

Ethotechnics Diagram Council. "Micro-diagram language specification." Ethotechnics Institute. Feb 1, 2026. https://ethotechnics.org/standards/micro-diagram-language.

BibTeX

@misc{micro_diagram_language,
  title={Micro-diagram language specification},
  author={Ethotechnics Diagram Council},
  year={2026},
  howpublished={Ethotechnics Institute},
  url={https://ethotechnics.org/standards/micro-diagram-language},
  version={v1.0.0}
}

RIS

TY  - WEB
TI  - Micro-diagram language specification
AU  - Ethotechnics Diagram Council
PY  - 2026
UR  - https://ethotechnics.org/standards/micro-diagram-language
ER  -

See also: Standards · Mechanisms