The Echelon Systems
A connected engineering ecosystem for building software with explicit state, durable evidence, bounded authority, measurable quality, and fewer hidden assumptions.
These systems are designed to work together. Some govern how work is performed, some make application behavior explicit, some constrain the browser and presentation layers, and others preserve evidence about security, quality, diagnostics, and decisions. The point is not a larger toolchain. The point is making important engineering claims inspectable.
Govern the work and the state
Praxis
The repository operating system: work protocol, evidence, research records, telemetry, verification, diagnostics, upgrades, and durable handoffs. The established ROS command remains a compatibility interface.
Ordo
State-Directed Engineering. Models legal states, transitions, capabilities, obligations, evidence, unknown effects, and the rules that keep agents from silently inventing domain behavior.
Visual Engineering
Installs evidence-bounded UI research and guidance so interface decisions are grounded in current evidence rather than copied conventions or stale snapshots.
Communication Engineering
An evidence-bounded discipline for choosing and evaluating communication by purpose, audience, proof obligation, context, and consequence.
Make claims prove themselves
Tutela
Security engineering built around assets, trust boundaries, threats, invariants, controls, evidence, unknowns, findings, and explicit release posture. It does not declare a system “secure”; it shows what the evidence supports.
Aegis
Typed operational fault handling and recovery for .NET applications, with redaction, lifecycle, escalation, safe presentation, diagnostics, containment, and durable fault evidence.
Dokimos
Evidence-based code quality over time. Preserves immutable observations, detects regressions and improvements, tracks hotspots, and keeps every quality judgment attributable to source, analyzer, configuration, and scope.
Percepta
Governs what users must be able to perceive about application state, actions, constraints, and unresolved work. It closes the gap between a visually correct interface and the correct product.
Build the surface without surrendering authority
Forma
The zero-runtime Echelon design system: semantic HTML, CSS, tokens, accessibility contracts, reusable browser-native components, application patterns, and white-label presentation.
Folio
Standards-first print components and layout primitives for professional HTML, paper, and PDF output, including repeatable results reports and demanding paged-media layouts.
Limen
The browser boundary. Browser capabilities stay separate from application authority, with plain serializable messages crossing the threshold and domain state remaining in the engine.
Conditor
Turns an empty repository into a governed engineering environment from a declarative manifest: resolve, install, verify, lock, scaffold, and hand off execution without manual file copying.
Apply the same discipline to harder domains
Strata
Declarative PostgreSQL schema management that distinguishes “matches” from “not compared,” “not modelled,” and “unverifiable” instead of turning missing knowledge into a false pass.
Echelon Diagnostic Framework
A diagnostic grammar for making system diagnoses explicit enough to challenge, with evidence boundaries, hypotheses, confidence policy, and controlled validation.
Clarity
Makes beliefs, assumptions, evidence, confidence, ownership, monitoring, and reconsideration criteria explicit so decisions can adapt when reality changes.
HelixNote
Ledger-first documentation and reasoning for complex cases where facts, timelines, contradictions, uncertainty, provenance, and reviewability matter.
Chrona
Echelon's time-entry application, built as a governed system rather than a detached CRUD utility and designed to participate in the wider project-administration flow.
Summa
The project-administration and financial-work foundation, coordinating work across independently authoritative repositories while preserving ownership boundaries.
Signal
An Echelon pilot for structured assessment work, built on the same repository operating discipline and evidence model as the rest of the ecosystem.
One ecosystem, not a bag of tools
The systems reinforce one another: Ordo constrains meaning, Percepta constrains what must be visible, Forma and Folio shape presentation, Limen protects the browser boundary, and Praxis preserves the evidence that the work actually happened.