Architecture Decision Records (ADRs)¶
Version: 1.2.0 Updated: 2026-01-31
This directory contains all Architecture Decision Records (ADRs) for the AEGIS project.
What is an ADR?¶
An Architecture Decision Record captures an important architectural decision made along with its context and consequences. ADRs are immutable once accepted—superseding decisions create new ADRs.
ADR Index¶
| ADR | Title | Status | Date | Related GAP |
|---|---|---|---|---|
| ADR-001 | Workflow State Persistence | Implemented | 2025-12-27 | GAP-M3 |
| ADR-002 | BIP-322 Signature Format | Implemented | 2025-12-27 | GAP-M4 |
| ADR-003 | Hybrid Post-Quantum Signatures | Implemented | 2025-12-28 | GAP-Q1 |
| ADR-004 | Hybrid Post-Quantum Encryption | Implemented | 2025-12-29 | GAP-Q2 |
| ADR-005 | KL Divergence Threshold Calibration | Accepted | 2025-12-26 | GAP-H1 |
| ADR-006 | Posterior Predictive for Bayesian Gates | Implemented | 2026-01-31 | NEW-A |
| ADR-007 | AWS Deployment Architecture | Accepted | 2026-02-10 | ROADMAP 17-20 |
ADR Template¶
New ADRs should follow this structure:
# ADR-XXX: Title
> **Status**: Proposed | Accepted | Implemented | Superseded
> **Date**: 2026-01-01 (example — replace with actual decision date)
> **Decision Makers**: Team/Individual names
> **Related Gap**: GAP-XX (if applicable)
> **Implementation**: Path to implementation (if implemented)
---
## Context
What is the issue that we're seeing that is motivating this decision or change?
## Decision Drivers
| Driver | Weight | Notes |
|--------|--------|-------|
| Factor 1 | HIGH/MEDIUM/LOW | Description |
## Options Considered
### Option 1: Name
**Approach**: Description
**Pros**: ...
**Cons**: ...
**Verdict**: SELECTED / REJECTED - Reason
## Decision
Describe the decision and the architecture.
## Consequences
### Positive
- List positive outcomes
### Negative
- List trade-offs and risks
### Neutral
- List neutral impacts
## Implementation Plan
Link to EPCC plan or brief implementation steps.
## References
- Links to relevant documentation
## Changelog
| Date | Author | Changes |
|------|--------|---------|
Status Definitions¶
- Proposed: Under discussion, not yet accepted
- Accepted: Decision made, implementation pending
- Implemented: Decision implemented and verified
- Superseded: Replaced by a newer ADR (link to successor)
See Also¶
- Gap Analysis - Gap tracking and resolution
- Repository Structure - Codebase organization
- Implementation Plans - EPCC implementation details