Architecture Decision Log¶
| Owner | Architecture Practice |
| Created | 2026-03-01 |
| Last Updated | 2026-03-03 |
| Total Decisions | 11 |
Overview¶
This is the global architecture decision log for the NovaTrek Adventures platform. Each ADR follows the MADR (Markdown Any Decision Record) format and is numbered sequentially.
Decisions originate in ticket-level solution designs and are promoted to this global log when they affect corporate architecture baselines — service contracts, data models, integration patterns, or cross-cutting concerns.
Decision Index¶
| ADR | Title | Status | Date | Services Affected | Origin |
|---|---|---|---|---|---|
| ADR-001 | AI Toolchain Selection for Architecture Practice | Proposed | 2026-03-01 | — (practice-level) | Phase 1 |
| ADR-002 | Documentation Publishing Platform Selection | Proposed | 2025-01-27 | — (practice-level) | Phase 6 |
| ADR-003 | Use Nullable Fields for Elevation Data | Accepted | 2026-02-15 | svc-trail-management | NTK-10001 |
| ADR-004 | Configuration-Driven Classification over Database-Driven | Accepted | 2024-08-14 | svc-check-in, svc-trip-catalog | NTK-10002 |
| ADR-005 | Pattern 3 as Default Fallback for Unknown Categories | Accepted | 2024-08-19 | svc-check-in | NTK-10002 |
| ADR-010 | Switch from PUT to PATCH Semantics for Schedule Updates | Proposed | 2026-02-28 | svc-scheduling-orchestrator | NTK-10004 |
| ADR-011 | Add Optimistic Locking to DailySchedule Entity | Proposed | 2026-02-28 | svc-scheduling-orchestrator | NTK-10004 |
Decisions by Service¶
| Service | Decisions |
|---|---|
| svc-check-in | ADR-004, ADR-005, ADR-006, ADR-007, ADR-008, ADR-009 |
| svc-guest-profiles | ADR-006, ADR-008 |
| svc-reservations | ADR-006, ADR-007 |
| svc-scheduling-orchestrator | ADR-010, ADR-011 |
| svc-trail-management | ADR-003 |
| svc-trip-catalog | ADR-004 |
Decisions by Status¶
| Status | Count | ADRs |
|---|---|---|
| Accepted | 7 | ADR-003 through ADR-009 |
| Proposed | 4 | ADR-001, ADR-002, ADR-010, ADR-011 |
| Deprecated | 0 | — |
| Superseded | 0 | — |
Promotion Process¶
Decisions are promoted from ticket-level 3.solution/d.decisions/decisions.md to this global log when:
- The decision affects a service's public API contract (endpoints, schemas, error codes)
- The decision changes a service's data model (new entities, schema migrations)
- The decision establishes a cross-service integration pattern (orchestration, events, shared contracts)
- The decision introduces a cross-cutting architectural pattern (caching strategy, locking, authentication)
Each promoted ADR is normalized to MADR format and linked back to its originating ticket.