Architecture Decision Records (ADRs)

Architectural decisions for the Noxys platform. Each ADR documents the context, decision, and consequences of a significant architectural choice.

Source of truth: this directory (docs/adr/). The Obsidian vault (03 - Decisions/) contains pointer files referencing this location.

Status legend

• Proposed — under discussion
• Accepted — current decision
• Superseded — replaced by a newer ADR
• Deprecated — no longer relevant

Index

#	Title	Status
004	ADR 004 — Detection: Hybrid Go-native + Python Presidio Sidecar	Accepted
005	ADR 005 — Infrastructure as Code: OpenTofu + Helm + Ansible (+ Docker Compose, Air-gap)	Accepted
006	ADR 006 — Voice DLP Strategy: 4-Phase Tiered Rollout with Whisper.cpp	Proposed
007	ADR-007: ML Training Forge Choice	Accepted
008	ADR-008 — Helm Chart Organization (Option C: Hybrid)	Accepted
009	ADR-009 — Three Deployment Modes Strategy (Extension / Agent / Proxy)	Accepted
010	ADR-010 — Pricing 3 tiers (Free / Pro / Enterprise) (internal)	Accepted
011	ADR-011 — Multi-modal detection pipeline (image / audio / video / code)	Accepted
012	ADR-012 — LiteLLM bundled as Python sidecar inside noxys-proxy (no standalone service)	Accepted
013	ADR-013 — Extension versioning strategy	Accepted
014	ADR-014 — AI placement strategy (internal)	Accepted
015	ADR-015 — Extension UX modes & lexicon refactor	Accepted
016	ADR-016 — Compliance frameworks (customer-facing)	Accepted
017	ADR-017 — Product compliance posture	Accepted
018	ADR-018 — Subscription lifecycle architecture (internal)	Accepted
019	ADR-019 — Prompt capture, storage, retention & sovereignty	Accepted
020	ADR-020 — Interaction lineage visualization	Accepted
021	ADR-021 — TanStack Query + Table adoption	Accepted
022	ADR-022 — UsersPage V2 spec	Accepted
024	ADR-024 — Authentication & MFA strategy	Accepted
026	ADR-026 — API completeness & OpenAPI policy	Accepted
028	ADR-028 — Core product priority: AI catalog + leakage detection + conditional prompt storage (internal)	Accepted
029	ADR-029 — Content-free session forensics & MCP enforcement (response to Varonis/Cursor)	Accepted

Workflow

Creating a new ADR

1. Pick the next available number (do not reuse gaps).
2. Copy _template.md to adr-NNN-short-slug.md.
3. Fill in Status, Context, Decision, Consequences.
4. Update this README index.
5. Open a PR — base staging.

Validation

Run scripts/check-adr-format.sh before opening a PR. The script verifies every ADR has Status, Context, Decision, and Consequences sections.

Numbering policy

ADR numbers are stable — never renumber. Gaps (e.g. missing 023, 025, 027) are intentional; renumbering breaks external references.