Fix migration workflow: upload as artifact instead of scp to practice EC2

This commit is contained in:
2026-08-13 11:14:25 +07:00
parent 7ebbe1f309
commit a4819b8653
51 changed files with 6830 additions and 8 deletions
+20
View File
@@ -0,0 +1,20 @@
# Architecture decision records
| ADR | Title | Status | Reflected in code? |
|---|---|---|---|
| [0001](0001-vector-db-qdrant.md) | Use Qdrant as the vector database | Accepted | **Yes**`adapters/qdrant.py`, `ingestion/load/qdrant_repo.py` |
| [0002](0002-argocd-gitops.md) | Use the team's existing ArgoCD instance for deployment (GitOps) | Accepted — target, **not yet implemented** | **No** — production is Docker Compose on EC2 ([20](../20-deployment.md)) |
| [0003](0003-pdf-parsing-strategy.md) | PDF parsing strategy, validated empirically | Accepted | **Yes**`ingestion/extract/`, `ingestion/segment/detector.py` |
| [0004](0004-chunking-strategy.md) | Chunking strategy for drug monographs | Accepted (monograph range only) | **Yes**`ingestion/chunk/chunker.py` |
| [0005](0005-segment-output-contract-for-chunking.md) | `segment/` output contract needed by `chunk/` | Proposed; header says "contract only, no implementation" | **Yes, now implemented**`segment/models.py` + `chunk/` follow it. The status line is stale |
| [0006](0006-quarantined-block-references-in-chunks.md) | Chunks must carry references to lifted table/formula blocks | Accepted, implemented in schema v4 | **Yes**`ChunkAttachment`, `has_quarantined_content`, the ADR-0006 gate set |
| [0007](0007-conversational-reasoning-rag.md) | Conversational reasoning RAG (state + bounded loop) | **Superseded by 0008** | **No**`rag/conversation.py` and `rag/reasoning.py` no longer exist |
| [0008](0008-llm-understanding-one-shot-rag.md) | LLM query understanding + one-shot grounded RAG | Accepted, live since 2026-08-06 | **Yes**`rag/understanding.py`, `rag/agent.py`, `rag/answer.py` |
| [0009](0009-no-rag-framework.md) | No RAG framework — hand-written orchestration behind ports | Accepted (recorded retrospectively) | **Yes** |
| [0010](0010-interim-single-host-compose-deployment.md) | Single-host Docker Compose as the interim deployment | Accepted (recorded retrospectively) | **Yes** |
ADRs 0009 and 0010 were written during the documentation pass described in
[DOCUMENTATION_PLAN.md](../DOCUMENTATION_PLAN.md). They record decisions that are
unambiguously visible in the implementation but had no ADR. Where the rationale
could not be recovered from the repository, they say so rather than inventing
one.