RELEASE & ROLLBACK PROOF / R25

把“已经上线”拆成可复核的 release、smoke 与 rollback 证据

R25 控制面已完成：85 个 release packet 包含 255 个证明阶段、1,020 条验证条件。真实 owner/release receipt 仍为 0，因此 R26 最终验收保持 fail-closed。

CURRENT KNIFE 27 / 27R26 · Program Acceptance 已接管最终队列

R25 合同完成不代表发布证明完成；没有制品 digest、生产 smoke 和回滚演练 receipt，就不能宣称页面 release-ready。

RELEASE CONTROL PLANE / 85 SCREENS

同一 Screen ID 贯穿候选、生产与恢复链

每页都必须锁定 exact release identity，执行 production smoke，并证明前一可用制品能够有界恢复；平台方法可复用，页面结果不能批量复制。

RELEASE PACKETS85one per CURRENT Screen ID

PROOF STAGES2553 stages per page

VERIFICATION CHECKS1020twelve per release packet

ELIGIBLE085 packets locked

ACCEPTED0R26 final gate remains red

R25RELEASE CONTRACT255 proof stages registered

→

R25 RECEIPTRELEASE + SMOKE + ROLLBACK0 / 255 accepted

→

R26PROGRAM ACCEPTANCE0 / 85 accepted

STAGE 01 · RELEASE85 LOCKED

EXACT RELEASE IDENTITY

把 Screen ID 绑定到不可变 source、build、配置、迁移和发布目标。

Immutable source identitysource repository、full commit SHA、clean build context 与 Screen ID 可追溯
Artifact digest and provenance制品类型、build ID、SHA-256、签名和生成流水线均可验证
Configuration and migration manifest配置版本、secret reference、feature flag、schema/migration 与兼容窗口已登记
Deployment target and ownership环境、region/channel、service/bundle、release owner 与批准的 R24 packet 一致

STAGE 02 · SMOKE85 LOCKED

PRODUCTION SMOKE

在真实发布目标验证入口、主任务、依赖、可观察性和失败预算。

Public entry and identity线上入口、版本标识、鉴权与租户/subject 绑定命中预期 release
Primary task and receipt页面主任务在生产依赖上完成，并生成可复核业务/交互 receipt
Dependency and negative probes关键依赖、权限拒绝、超时、降级与恢复路径通过有界 smoke
Trace, SLI and rollback triggertrace/log/metric 可关联 release，且 rollback trigger、观察窗与阈值明确

STAGE 03 · ROLLBACK85 LOCKED

ROLLBACK DRILL

证明前一制品可恢复、数据兼容、切换有界且恢复后主任务仍通过。

Previous artifact pinned前一可用制品、配置、schema 与恢复目标均以不可变 ID 固定
Data and client compatibility向后兼容、migration down/forward-fix、缓存与客户端版本影响已验证
Bounded rollback execution触发者、命令/渠道、开始结束时间、影响范围与审计 receipt 完整
Post-rollback recovery smoke恢复版本、健康、页面主任务、数据完整性与告警清除全部复核

WEB + ADMIN55 LOCKED

55 screens · 165 stages

candidate → canary → smoke → atomic route switch → previous release restore

PACKETS: 55
CHECKS: 660

iOS NATIVE28 LOCKED

28 screens · 84 stages

archive → sign/notarize → phased distribution → previous build recovery

PACKETS: 28
CHECKS: 336

HOSTED SURFACES2 LOCKED

2 screens · 6 stages

bundle candidate → host canary → version pin → previous bundle restore

PACKETS: 2
CHECKS: 24

VERIFIED REFERENCE / SCOPE-BOUNDED

一份真实发布样本，只校准方法，不替产品填证据

developer portal 的上一刀部署已经经历 exact source、构建、canary、原子切换、回滚目标固定和公网 smoke。它证明控制面设计可执行，但作用域仅限 developer.reits.tech。

REFERENCE_PARTIAL

developer.reits.tech · R24 deployment reference

REFERENCE ONLY · does not satisfy any of the 85 product release packets

5 PASS · 1 BOUND

SOURCE70b0e9175c510c218b1f2431ebecc39582917fe7

ROLLBACK TARGETd5d84defedaeb01e7631413a74232d9acfe583d6

SITES VERSION61

OBSERVED2026-07-18

Exact source pushed

Sites source branch and immutable EC2 release use commit 70b0e91.

PASS

Build and contract suite

37/37 rendered contracts and 133/133 UI CI packets passed before publish.

PASS

Isolated canary smoke

R24 APIs and representative pages passed on the isolated canary service.

PASS

Atomic production switch

current symlink moved to an immutable release and the production service returned active.

PASS

Rollback target pinned

Previous immutable R23 release remains the recovery target; an intentional rollback drill was not executed.

BOUND

Public production smoke

developer.reits.tech returned HTTP 200 and exact R24 program/API counts.

PASS

/opt/reits-developer-portal/releases/70b0e9175c510c218b1f2431ebecc39582917fe7打开生产站 →

PRODUCT RELEASE QUEUES / 9

产品 release owner 负责制品与恢复，不跳过四方审批

每个队列保留候选 source revision、production posture、平台交付方法、首个 Gate 和逐页 proof path。

R16 · 公共官网

reits-info-portal

10 LOCKED

PACKETS: 10
STAGES: 30
CHECKS: 120
ACCEPTED: 0

CANDIDATE SOURCE05500792e5795111889a53670fc609e9174190d1SOURCE = PRODUCTION

首页、搜索、文章和 Pixel Atlas 先完成三视口稳定 fixture 与截图。

R16 · 社区

reits-bbs

8 LOCKED

PACKETS: 8
STAGES: 24
CHECKS: 96
ACCEPTED: 0

CANDIDATE SOURCE1d2d5b6fdbe1918245298cb5f0830c094356b02cSOURCE = PRODUCTION THEME

Feed、Topic、Composer 先形成登录/匿名、长内容、媒体和风险状态基线。

R16 · 预约与商家

public-booking-platform

9 LOCKED

PACKETS: 9
STAGES: 27
CHECKS: 108
ACCEPTED: 0

CANDIDATE SOURCE6f3e62af47cff3dc95d782a299b09b5f10278b3dSOURCE = EC2 RELEASE

发现、店铺、预约与状态链先绑定 111 source / 51 exposure 双事实和事务 fixture。

R17 · 采集控制面

data-sources

15 LOCKED

PACKETS: 15
STAGES: 45
CHECKS: 180
ACCEPTED: 0

CANDIDATE SOURCEcb37d2ce9633e7395d614f3b3239c5efea2902f7EXACT

概览、采集源、运行日志先从 8,567 行 App.vue 拆出独立视觉和键盘证据。

R17 · 行情控制面

trading-data-source

10 LOCKED

PACKETS: 10
STAGES: 30
CHECKS: 120
ACCEPTED: 0

CANDIDATE SOURCE55b1ad827176b0937963d5694f411e901665fcfdABSENCE BOUND

Dashboard、Source、Task 必须同时捕获 source-only UI 与生产缺失态。

R17 · 开放平台

miniapp-open-platform

4 LOCKED

PACKETS: 4
STAGES: 12
CHECKS: 48
ACCEPTED: 0

CANDIDATE SOURCEfa9283d6c7ea964864d7a1b31035b03411802622SOURCE / RUNTIME SPLIT

R18 · Matrix X

matrix-x-chat-ios

14 LOCKED

PACKETS: 14
STAGES: 42
CHECKS: 168
ACCEPTED: 0

CANDIDATE SOURCE257e604a5073b1ecab0f905d7ec59dfb78960639IM RUNTIME EXACT · DISTRIBUTION UNPROVEN

R19 · Matrix Quant iOS

matrix-quant-im-ios

14 LOCKED

PACKETS: 14
STAGES: 42
CHECKS: 168
ACCEPTED: 0

CANDIDATE SOURCE604987ac36dcc9a66e8f8d2c86c0af197cd7a289LATEST CANDIDATE · PRODUCTION ABSENT

策略、回测、run、signal 先证明 data-as-of、no-execution、Release adapter 与 App Store exact。

R19 · 端上模拟器

matrixantai-sim

1 LOCKED

PACKETS: 1
STAGES: 3
CHECKS: 12
ACCEPTED: 0

CANDIDATE SOURCE18aee8d3141d26c8e9a914f0e57ca971589c023cCANDIDATE PACKAGE · PRODUCTION ABSENT

桌面、窗口、MiniApp、offline/a11y 四环境先绑定 reviewed synthetic slice 与 result hash。

PROOF STAGES255 / 255

85screens

255locked

RELEASE PROOF STAGER25-portal-home-exact_release

OWNER APPROVAL BLOCKED

R24 FOUR-OWNER RECEIPTS0/4 owner approvals signedartifacts/ui/portal-home/approvals/product.jsonartifacts/ui/portal-home/approvals/design.jsonartifacts/ui/portal-home/approvals/architecture.jsonartifacts/ui/portal-home/approvals/qa.json

Product、Design、Architecture、QA 四份 receipt 全部 accepted 后，release packet 才可进入候选构建。

公共官网 · R16 · WEB_ADMIN

全球资讯首页

EXACT RELEASE IDENTITY · 把 Screen ID 绑定到不可变 source、build、配置、迁移和发布目标。

Stage owner: Release Engineering + Repository Owner
Candidate source: 05500792e5795111889a53670fc609e9174190d1
Posture: SOURCE = PRODUCTION
Target: immutable web/admin release + production route
Delivery method: candidate → canary → smoke → atomic route switch → previous release restore

VERIFICATION CHECKS0 / 4

01
Immutable source identity
source repository、full commit SHA、clean build context 与 Screen ID 可追溯
LOCKED
02
Artifact digest and provenance
制品类型、build ID、SHA-256、签名和生成流水线均可验证
LOCKED
03
Configuration and migration manifest
配置版本、secret reference、feature flag、schema/migration 与兼容窗口已登记
LOCKED
04
Deployment target and ownership
环境、region/channel、service/bundle、release owner 与批准的 R24 packet 一致
LOCKED

PROOF RECEIPT PATHartifacts/ui/portal-home/release/exact_release.jsonreleaseId: null · buildDigest: null · completedAt: null

R25 事实边界

R25 已为 85 张 CURRENT 建立 85 个 release packet、255 个 exact-release/smoke/rollback 证明阶段和 1,020 条验证条件。R24 当前 0/340 owner receipt signed，因此全部 packet 都 BLOCKED_BY_OWNER_APPROVALS；developer portal 的 R24 生产发布只作为方法校准样本，不替九个产品提供 release proof。

85 locked · 255 stages · 1,020 checks · 0 release-ready打开机器清单 →