跳转至

Historical version

This page records design, operation, or validation facts from an earlier release. It is not current V7.17.3 guidance. Start from the documentation hub for current instructions.

V7.3.0 Audit Report

Chinese: Chinese documentation

Current conclusion

The V7.3.0 behavioral and release diff is reviewed through two independent logically read-only perspectives: data contracts and test delivery. Only the deduplicated, consolidated conclusion is accepted for release. Scope includes Reviewer result contracts, minimum-profile gates, attribution finalization, unknown-cost semantics, Plugin runtime selection, version metadata, bilingual artifacts, and upgrade paths.

The implementation remains fail closed. Reviewer results below the minimum profile cannot close normally; Reviewers cannot finalize their own attribution; missing cost cannot drive low-yield decisions; Plugin mode cannot fall back to a stale standalone runtime; and insufficient real calibration evidence cannot rewrite default routing. execution_authorization=NONE and the Terra High automatic ceiling are unchanged.

The first review round identified four consolidated root causes: the controller did not recursively validate calibration results, unfinalized cost entered the benefit denominator, missing or damaged installation state could select a stale runtime, and upgrade documentation omitted 7.2.0. After repair, the controller rejects sensitive nested fields and non-string evidence before any state or ledger write; benefit metrics use finalized cost while total observed cost remains visible; an installed Plugin fails closed when state or its bound cache is unavailable; and both language guides explicitly include 7.2.0. A targeted second review is a hard publication gate, and release proceeds only with no remaining blocker.

Review is logically read-only rather than system read-only: the parent session retains workspace write authority while Reviewers operate under explicit read-only responsibility. This conclusion covers code, documentation, tests, and local installation. Commit, push, tag, public release, and post-download artifact verification remain independent states requiring separate readback.

Audit scope

  • Reviewer packet/result/state schema v3/v3/v5 compatibility and legacy v2 result reading
  • minimum_acceptable_profile, append-only INLINE/DELEGATE decisions, and budget boundaries
  • Finding disposition, attribution finalization, deduplicated calibration ledger, and profile-weight-v1 cost
  • Missing cost, unfinalized attribution, insufficient samples, and unchanged-default-routing gates
  • Plugin versus standalone runtime selection, installation-state binding, and fail-closed missing-cache behavior
  • Current 7.3.0 metadata, bilingual release, historical-evidence isolation, and the 7.2.0 upgrade path

Historical docs/releases/v7.2.0 and earlier content remains unchanged and does not serve as current 7.3.0 acceptance evidence.