Motivation
Architecture Decision Records are the durable why of AskMyDocs: each one captures a problem, the options weighed, the decision taken, and its consequences. This page is the terse, numbered index; for the narrative that groups them into dependency arcs, see architecture decisions. The full records live indocs/adr/ in the repository.
The records
Each row links to its full record in the repository.| # | Title |
|---|---|
| 0001 | Canonical knowledge layer inside knowledge_documents |
| 0002 | Lightweight knowledge graph via kb_nodes / kb_edges |
| 0003 | Human-gated promotion pipeline (raw → curated → canonical) |
| 0004 | v4.2 sister-package integration |
| 0005 | v4.3 React 19 host bump |
| 0006 | v4.3 Nightly eval-harness regression cron |
| 0007 | v4.4 Adversarial nightly opt-in |
| 0008 | v4.5 Universal connectors + source-aware ingestion + modern chat surface |
| 0009 | v4.6 Connector package extraction + IoC bridge + composer-extra discovery |
| 0010 | v4.7 Tabular Review + Workflows + AI-suggest |
| 0011 | v6.0 AI Act compliance integration via extracted packages |
| 0012 | v8.0 Notification system (DB-backed, multi-channel) |
| 0013 | v8.8 KB lifecycle intelligence — Plus |
| 0014 | v8.11 Auto-Wiki auto tier |
How ADRs are used here
- A new architectural decision ships its own record in
docs/adr/and a row in this index — in the same PR that introduces the change. - A decision is never silently reversed: a later ADR that supersedes an earlier one says so explicitly, and the earlier record stays for the trail.
- Load-bearing constraints called out across the docs — no AI SDKs (raw
Http::), the human-gated promotion boundary, canonical-markdown-as-source-of-truth — trace back to these records.
Architecture decisions
The narrative grouping these records into arcs.
Architecture overview
The system spine that connects the subsystems.