YoVinchen
cfd6d4cbad
Some checks failed
verify / verify (push) Has been cancelled
The backend can now be inspected through a loopback-only gateway while the database-aware API remains on the internal data network. A governed synthetic demo proves readiness, pgvector retrieval, reranking, and citation output through real HTTP without invoking cloud models. Constraint: The previously exposed Bailian key is compromised and cannot be used for live validation Constraint: The API must be locally reachable while retaining no internet egress Rejected: Attach the API directly to the ingress network | a real socket test proved that configuration still had egress Rejected: Publish a port from the internal-only network | Docker Desktop did not expose the host port Confidence: high Scope-risk: moderate Reversibility: clean Directive: Keep model and database credentials out of the gateway; do not relax the fixed demo identity/profile filters Tested: make verify; 63 pytest tests; strict mypy; Ruff; Secret scan; Compose config; three backend image builds; API/DB/gateway healthy; migration exit 0; Swagger browser check; live/ready/meta/status/search HTTP; 20/20/20 index; API egress ENETUNREACH; empty gateway mounts and business environment Not-tested: Live Bailian calls require a newly rotated key; full generated-answer flow and React UI are not implemented
设计文档索引
当前进度
- Stage 0“仓库、安全和设计基线”已完成并推送。
- Stage 1“模型与数据库 PoC”正在进行。
- 当前整体完成度约 12%，合理区间为 10%–15%。
- 00–03 的设计基线已完成；业务代码完成度约 8%，Stage 1 离线数据库/适配器/seed 子闭环已验收，真实百炼 smoke 与前端产品功能尚未完成。
- 后续状态、依赖、验收证据、工期和提交节点以 项目全生命周期 TODO 为准。
文档列表
| 文档 | 内容 | 状态 |
|---|---|---|
| 00-overall-design.md | 项目范围、总体架构、技术选型、接口、数据模型与 RAG 主流程 | 设计基线完成 |
| 01-data-and-evaluation.md | 语料治理、解析、验证集生成、向量入库测试和论文评测 | 设计基线完成 |
| 02-deployment-and-security.md | Docker Compose、配置、密钥、监控、备份和安全 | 设计基线完成 |
| 03-implementation-plan.md | 阶段计划、完成定义、测试与验收清单 | 设计基线完成 |
| 04-project-todo.md | 从当前状态到最终答辩、发布和归档的任务看板 | Stage 1 进行中 |
| 05-stage1-runbook.md | Secret 初始化、离线数据库/seed、真实三模型 smoke 和排障命令 | Stage 1 运行手册 |
| adr/ | 不易逆转的架构决策记录 | 持续维护 |
文档中的工作空间地址统一使用 <workspace-id> 占位符；真实地址和凭证均属于部署配置，不写入仓库。
建议首次阅读按 00 → 01 → 02 → 03 → 04 的顺序；日常执行查看 04，运行 PoC 查看 05。