docs: plan vehicle ingest redesign phase 1

docs/superpowers/specs/2026-06-29-vehicle-ingest-redesign.md

@@ -165,6 +165,14 @@ Rules:
 - `rawUri` must be resolvable by history API for single-frame replay.
 - Malformed frames are written with `parseStatus=FAILED` when bytes are available.
 
+Deployment constraints:
+
+- Raw archive, TDengine, and the history service may run on different ECS instances, but should use private-network access in the same VPC and availability zone.
+- High-frequency historical queries only read TDengine and must not read raw archive.
+- Raw archive is only used by single-frame detail, troubleshooting, replay, and asynchronous export paths.
+- `rawUri` must be globally resolvable by services and must not be a private local absolute path on one ECS instance.
+- The first local raw archive implementation must stay behind a replaceable interface so it can later move to OSS, MinIO, or another object store.
+
 ### Kafka Topics
 
 Use stable versioned topics:

docs/superpowers/specs/2026-06-29-vehicle-ingest-redesign.zh.md

@@ -165,6 +165,14 @@ public record RawArchiveReceipt(
 - `rawUri` 必须能被历史 API 解析，用于单帧回放。
 - 异常帧只要有 bytes，也必须写入，并记录 `parseStatus=FAILED`。
 
+部署约束：
+
+- Raw archive、TDengine、history 服务可以不在同一台 ECS，但应在同一 VPC 和同一可用区内通过内网访问。
+- 高频历史查询只访问 TDengine，不访问 raw archive。
+- Raw archive 只进入单帧详情、问题排查、回放和异步导出路径。
+- `rawUri` 必须是全局可解析地址，不能是某台 ECS 私有的本地绝对路径。
+- 第一版本地 raw archive 需要通过可替换接口封装，后续可以切换到 OSS、MinIO 或其它对象存储。
+
 ### Kafka Topic
 
 使用稳定的版本化 topic：