ENGINEERING
Architecture Decision Records
Explicit decisions, context, and consequences. ADRs are engineering artefacts — not marketing claims.
PRODUCTION DOCUMENTATIONRecords
-
ADR-001-local-first
ADR-001 Local-first architecture
-
ADR-002-php-node-boundary
ADR-002 PHP/Node boundary
-
ADR-003-json-persistence
ADR-003 JSON persistence
-
ADR-004-ranking
ADR-004 Ranking architecture
-
ADR-005-public-intelligence
ADR-005 Public intelligence boundaries
-
ADR-006-security-model
ADR-006 Security model
-
ADR-007-search-architecture
ADR-007 Search architecture
-
ADR-008-knowledge-graph
ADR-008 Knowledge graph
-
ADR-009-observability
ADR-009 Observability
-
ADR-010-future-extensibility
ADR-010 Future extensibility
-
ADR-011-cpanel-deployment
ADR-011 cPanel deployment
-
ADR-012-backup-architecture
ADR-012 Backup architecture
-
ADR-013-api-versioning
ADR-013 API versioning
-
ADR-014-media-security
ADR-014 Media security
-
ADR-015-observability
ADR-015 Observability
-
ADR-016-research-integrity
ADR-016 Research integrity
-
ADR-017-graceful-degradation
ADR-017 Graceful degradation
-
ADR-018-performance-strategy
ADR-018 Performance strategy
-
ADR-019-privacy
ADR-019 Privacy
-
ADR-020-disaster-recovery
ADR-020 Disaster recovery
ADR-009 Observability
Accepted
Status: AcceptedContext: Operators need health and audit without third-party APM.
Decision: JSONL app logs, audit-log.jsonl, /api/health service checks, optional monitor scheduler.
Consequences: Local observability; limited distributed tracing.