Some checks failed
Documentation Lint & Validation / Markdown Linting (push) Has been cancelled
Documentation Lint & Validation / Validate mdBook Configuration (push) Has been cancelled
Documentation Lint & Validation / Content & Structure Validation (push) Has been cancelled
mdBook Build & Deploy / Build mdBook (push) Has been cancelled
Rust CI / Security Audit (push) Has been cancelled
Rust CI / Check + Test + Lint (nightly) (push) Has been cancelled
Rust CI / Check + Test + Lint (stable) (push) Has been cancelled
Documentation Lint & Validation / Lint & Validation Summary (push) Has been cancelled
mdBook Build & Deploy / Documentation Quality Check (push) Has been cancelled
mdBook Build & Deploy / Deploy to GitHub Pages (push) Has been cancelled
mdBook Build & Deploy / Notification (push) Has been cancelled
Architecture Decision Records (ADRs)
This directory documents significant architectural decisions made during VAPORA development. Each ADR captures the context, decision, rationale, and consequences of important design choices.
ADR Index
| # | Title | Status | Date |
|---|---|---|---|
| 0001 | A2A Protocol Implementation | Accepted | 2026-02-07 |
| 0002 | Kubernetes Deployment Strategy for kagent Integration | Accepted | 2026-02-07 |
| 0003 | Error Handling and JSON-RPC 2.0 Compliance | Accepted | 2026-02-07 |
How to Use ADRs
- Reading an ADR: Start with the "Decision" section, then read "Rationale" to understand why
- Proposing Changes: Create a new ADR if changing a key architectural decision
- Context: ADRs capture decisions at a point in time; understand the phase (MVP, phase 1, etc.)
- Related Decisions: Check links to understand dependencies between decisions
ADR Format
Each ADR follows this structure:
- Status: Accepted, Proposed, Deprecated, Superseded
- Date: When the decision was made
- Authors: Team or individuals making the decision
- Context: Problem we were trying to solve
- Decision: What we decided to do
- Rationale: Why we made this decision
- Consequences: Positive and negative impacts
- Alternatives Considered: Options we rejected and why
- Migration Path: How to evolve the decision
- References: External documentation