Architecture Decision Records

Every architectural decision on record, in the order it was made.

• ADR 1: Domain Centric Architecture
• ADR 2: Store Data as JSON
• ADR 3: Neo4j as Graph Database
• ADR 4: Use a Dedicated MediaWiki Revision Slot
• ADR 5: Subject GUIDs
• ADR 6: Schemas
• ADR 7: Multiple Subjects Per Page
• ADR 8: One Schema per Subject
• ADR 9: Move Away from JSON Schema
• ADR 10: Add GUIDs to Relations
• ADR 11: Include Writer's Schema in Subjects
• ADR 12: Backend Validation
• ADR 13: Restrict Neo4j Access
• ADR 14: Improved ID Format
• ADR 15: Dedicated Editors
• ADR 16: Frontend State Management
• ADR 17: Names as Identifiers
• ADR 18: Views and Layouts
• ADR 19: Graph Database Architecture
• ADR 20: Codex Styling Policy
• ADR 21: Add Backend Validation
• ADR 22: Multi-wiki Graph Node Identity
• ADR 23: Subject Sources
• ADR 24: Frontend Extension Mechanism
• ADR 25: Backend-driven Frontend Validation
• ADR 26: Validation Severity Levels
• ADR 27: Access Control
• ADR 28: Relations Model
• ADR 29: Scalability Targets
• ADR 30: Frontend Stores Are Registries, Not Caches
• ADR 31: Optional Subject Labels
• ADR 32: Subject-to-Page Index