The 10-part model

14ten is built as a deterministic pipeline that converts observed accessibility events into provable compliance outputs.

1–4: Common language for accessibility events

1. Signal — a discrete, immutable fact (e.g., caption payload; speaker change notification).
2. Envelope — a trust wrapper for the signal (provenance, timing, integrity).
3. Taxonomy — a controlled vocabulary describing what kind of signal it is.
4. Normalization — a consistent structure so signals become comparable.

5–8: Deterministic logic and routing

5. Pipeline — observable flow that ingests and transforms signals.
6. Rule — a deterministic “policy-as-code” statement (auditable and testable).
7. Routing — declarative delivery of signals to destinations (UI, archives, compliance systems).
8. State — derived context computed from signals over time (e.g., “who is currently speaking”).

9–10: Compliance outputs

9. Evidence — persisted artifacts that substantiate a claim (caption logs, timing traces, rule execution records).
10. Assertion — a formal, auditable claim about compliance status derived from evidence.

Why this model is enterprise-shaped

• Deterministic: rules can be tested, versioned, and audited.
• Composable: systems can adopt pieces incrementally (signals first, assertions later).
• Inspectable: every claim points back to concrete evidence artifacts.

Diagram pack

• Signal / Envelope / Taxonomy / Normalization
• Pipeline / Rule / Routing / State
• Evidence → Assertion

See: Resources for the full PDF proposal and diagrams.