Architecture Decision Records (ADR) — SOTER / Logos

This directory holds the SOTER and Logos Architecture Decision Records (ADRs). Since May 2026, all ADRs are modularly recorded as individual markdown files in the adr/ directory.

Below is the index of all established Architecture Decisions:

Index of ADRs

• ADR-001 (Accepted) — Transformational Change Model vs. Procedural Notation (BPMN). Adopted cybernetic SVO state transformations instead of procedural BPMN activities.
• ADR-002 (Accepted) — Separation of Genotype (Ontology) and Phenotype (Projections/Views). Separation of text-based .model from rendered diagrams and interactive interfaces.
• ADR-003 (Accepted) — Choice of Technology Stack. Moved from JVM/PlantUML to Python (Lark parser), Git, and modern web graphics.
• ADR-004 (Accepted) — Relation Filtering Algorithm in Views (slice_view). Added filtering modes for relations inside views.
• ADR-005 (Temporary) — 1 .model file = 1 Process Convention. Temporary 1-to-1 mapping until multi-process syntax is defined.
• ADR-006 (Accepted) — Extract Ledger Protocol as an independent fact kernel.
• ADR-007 (Accepted) — Asynchronous M2M API and middleware constraint.
• ADR-008 (Accepted) — Bitemporal auditing via hash-binding and Claim Check.
• ADR-009 (Accepted) — Ledger storage backend strategy.
• ADR-010 (Proposed) — Session lifecycle model dilemma.
• ADR-011 (Proposed) — Akasha reader-side reliability and raw-faithful default.
• ADR-012 (Proposed) — Fact envelope source sequencing and fact kinds.
• ADR-013 (Proposed) — Interpretive authority and jurisdiction.
• ADR-014 (Proposed) — Akasha deployment, role, and milestone order.

For guidelines on amending architecture or submitting a new ADR, please consult the SOTER Constitution § 5.

Related Documents

• DocumentationStyleGuide.md - writing profile and document-type rules.
• AdrTemplate.md - adr document template.
• ArchitectureOverview.md - technical architecture entry point.