每項帶來重要影響的操作都應留下證據。
Zof 記錄發生哪些變更、驗證了什麼、哪些工具與模型參與其中、產生哪些證據、符合哪些政策、由誰授權操作，以及之後發生什麼。
一個物件，回答 發生了什麼，以及為何值得信任。
Zof 將驗證結果、支持性紀錄及授權決策彙整成佐證套件，以供審查。Control Plane 評估操作能否繼續時會使用這些佐證。
Change
- Reference
- PR #4831 · payments/auth.ts
- Generated by
- Coding agent (model and version recorded)
- Affected systems
- 7 · Tier 0
- Risk
- High
Verification
- Unit
- Pass
- Integration
- Pass
- Security
- Pass
- Performance
- Pass
- PCI controls
- Pass
Evidence
- Artifacts
- 37
- Execution traces
- 14
- Policy evaluations
- 6
- Approvals
- 2
Authorization
- Payments Tier 0 policy
- Satisfied
- Security policy
- Satisfied
- Human approval
- Approved · release owner (named)
Outcome
- Decision
- Release authorized
- Production
- Healthy after release
- Evidence ID
- zof_ev_8f29…
Eight questions, answered for every action.
What changed
The change itself, its scope, and the systems the System Graph resolved as affected.
Who or what proposed it
A named developer, a coding agent, or an automation, with the model and tool versions involved.
What was verified
Which verification domains ran, what they covered, and what they found.
Which tools and models participated
Deterministic tools, verification systems, customer validators, and approved models, each attributed.
What evidence was produced
Artifacts, execution traces, screenshots, logs, and policy evaluations, sealed together.
Which policies were satisfied
Every policy evaluated against the change, with its result and the version of the policy that applied.
Who authorized it
The named approvers, their roles, and the exact decision they made.
What happened afterward
Production outcome recorded against the change, so the loop closes with what actually happened.
是證明，而非儀表板。 為日後查閱而建構。
儀表板告訴您此刻正在發生什麼。佐證則讓數月後的審查者了解當時已知的資訊、作出的決策，以及該決策當時為何合理。
- 有紀錄且可追溯來源
佐證紀錄將發現及決策連結至產生它們的工具、系統或人員。
- 依政策管理儲存與資料外傳
私有部署中的佐證儲存及任何已核准的資料外傳，皆遵循您設定的環境與政策。
- 可從 System Graph 查詢
從服務追溯至影響它的變更、當時存在的佐證，以及所作的決策。
- 可按需匯出
發布摘要、合規佐證套件及主管報告均由相同的套件產生。
The same evidence, read by four different rooms.
Release reviews
What must be proven for this release, and whether it has been.
Auditors and compliance
Which controls applied, which were satisfied, and who approved, with provenance.
Incident reconstruction
What changed before the incident, what evidence existed, and what was decided.
Leadership
Release readiness and risk posture built from proof, not from a status slide.
了解您的系統的佐證套件樣貌
預約 Reliability Sprint，檢視限定範圍評估中的情境、觀察到的行為及支持性紀錄。
- 佐證處理遵循您的部署政策
- 來源資訊連結至發現
- 可匯出供稽核使用
