Developer portalrunning
架构、UI、契约、QA 与运行真值入口
ARCHITECTURE DOSSIER · 08
多团队交付与 QA 架构
任务包、契约、UI CI、发布证据、灰度与回滚
MIXED
DELIVERYCODE + RUNTIME + QA01Client
02Edge
Gitea org / branch rulesmixed
仓库、review、保护分支与 webhook
03Service
Screen packet registryrunning
133 个 Screen ID、九态、owner、viewport、G1–G8 evidence path
UI CI validatorrunning
unique ID、F4 分轨、九态、契约、风险与 fail-closed readiness
Product evidence producertarget
fixture、contract、visual/a11y、security、release、production proof
Release controllermixed
artifact、approval、deploy、smoke、rollback
04State
Evidence registrymixed
commit、contract、screenshots、test、deploy result 与 digest
CRITICAL SEQUENCE
真实主链与事务边界
每一步都必须能回到调用方、契约、状态 owner 与失败证据；UI 只显示服务端已经确认的真值。
- 01
Architect 在 /api/ui-ci 分配稳定 Screen ID、九态、owner 与 G1–G8 path
→ - 02
产品 owner 提交符合 schema 的 task packet 与 exact contract revision
→ - 03
AI/开发者在独立 owner paths 实现确定性 fixture 和产品代码
→ - 04
CI 生成 static/unit/contract/visual/a11y/interaction/security evidence 与 sha256
→ - 05
validator 校验 manifest、digest、跨仓 consumer 与 fail-closed 决策
→ - 06
owner review 后构建 immutable artifact 并绑定 exact commit
→ - 07
部署 smoke、SLO 与 rollback receipt 登记后才允许 production proven
INTERFACE REGISTER
跨项目接口与安全条件
producer、consumer、契约和 guard 同时登记；其中任何一列缺失都不能进入多团队并行开发。
ProducerVersioned contractConsumerSecurity / consistency guard
Developer portal
UiCiPacket {screen,stateFamily,owners,evidencePaths,readiness}AI / developers / repository CI133 unique F4 TARGET; nine states; no readiness inheritance
Repository CI
UiEvidenceManifest v1 {source,states,evidence,decision}K16 validator / Release controllerG1–G8 paths + sha256 + schema + fail closed
Release
DeploymentEvidence {artifact,env,migration,smoke,slo,rollback}Developer portalexact commit + owner approval + external journey
STATE OWNERSHIP
数据真值与恢复
STORErepositories + DB
RETENTION长期
RECOVERYoff-host Gitea backup
STOREGit + /api/ui-ci
RETENTION版本化永久
RECOVERY从 exact commit 重建
STOREGitea artifact; registry ingestion target
RETENTION按 PR + release policy
RECOVERY可从 commit + deterministic fixtures 重建
STOREreits-knowledge
RETENTION永久版本化
RECOVERYGit history
FAILURE MODEL
故障必须怎样收敛
SYMPTOM冲突、重复实现、契约漂移
CONTAIN任务包 owner + file/screen scope
assignment registrySYMPTOM页面随合并悄悄漂移
CONTAIN稳定 viewport + baseline + threshold
visual diff artifactSYMPTOM线上无法定位代码或回滚
CONTAINartifact 绑定 exact commit
release record + smokeSYMPTOM设计完成被误报为产品上线
CONTAINregistry/policy 与 product evidence 分轨；缺任何必需 evidence 即 blocked
K16 truth-boundary validatorQA RELEASE GATES
不是画完架构图就算完成
这些门禁连接 UI 状态、接口负向路径、运行证据与可恢复性；发布证据必须绑定 exact commit。
133 Screen ID 唯一、F4 TARGET 分轨、九态和 G1–G8 path 完整
K16 registry report
task packet + owner paths + non-goals + rollback
G1 blocking
lint/type/schema/secret + deterministic fixture/unit
G2/G3 blocking
producer/consumer contract + compatibility/migration
G4 blocking
九态 visual/a11y/interaction/responsive/native matrix
G5 blocking
authz/resource/abuse/privacy/redaction/artifact integrity
G6 blocking
exact artifact、SBOM、config、migration、rollback
G7 blocking
external synthetic、telemetry、error budget、owner ack
G8 production proof