Skip to content

Commit 464679d

Browse files
committed
[docs] distinguish active OI policy validation from retained history
Signed-off-by: Viwat Vchirawongkwin <viwat.v@chula.ac.th>
1 parent f24adbf commit 464679d

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

  • docs/specifications/firmware

‎docs/specifications/firmware/TDD.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1878,6 +1878,13 @@ generated bytes exist.
18781878
exact profiles.
18791879

18801880
Profiles or successful samples from different baselines MUST NOT be mixed.
1881+
After a controlled refresh, the active-policy readiness test MUST validate the
1882+
currently referenced canonical baseline, its digest and filename/source binding,
1883+
and every baseline-derived threshold through the maintained release validator.
1884+
It MUST retain the source-era fixed performance SLOs and the fixed Waveshare
1885+
largest-block floor, rather than pinning a previous active policy's bytes or
1886+
measurement-derived resource values. Historical baseline immutability is a
1887+
separate assertion and remains unchanged when the active reference advances.
18811888
Historical pre-`0.5.0` and v0.5.x policies retain their exact V1 and V3/V2
18821889
derivation identifiers and arithmetic. The predecessor v0.6.0 contract also
18831890
retains V3/V2 when its bound source is at or before

0 commit comments

Comments
 (0)