Skip to content

Commit e68a499

Browse files
committed
[docs] clarify observed read status and response mapping semantics
Signed-off-by: Viwat Vchirawongkwin <viwat.v@chula.ac.th>
1 parent 3cf3f42 commit e68a499

2 files changed

Lines changed: 15 additions & 0 deletions

File tree

‎docs/specifications/firmware/TDD.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2004,6 +2004,11 @@ strict fresh challenge echo, and zero additional recovery emissions. Normal
20042004
unobserved callers retain their existing behavior and block-device identity.
20052005
All five overlay tests prove observed mounting, attachment sealing only after
20062006
`vfs.mount`, and bounded recovery sealing before any possible agent startup.
2007+
Erased-scan status tests cover both observed and unobserved callers: `None`,
2008+
exact integer zero, and boolean `True` succeed, while `False`, floating zero,
2009+
and custom equality-to-zero objects fail without formatting. Collector tests
2010+
round-trip the actual firmware getter through JSON with reordered mapping
2011+
keys; exact key sets remain required without imposing MicroPython dict order.
20072012

20082013
The workspace acquisition tests MUST exercise the live collector's event
20092014
sequence and reject an expected four-line summary without measured siblings.

‎docs/specifications/firmware/specs.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -548,6 +548,10 @@ program_calls erase_calls workspace_attached recovery_attempts
548548
recovery_emissions complete fault overflow media_state
549549
```
550550

551+
The accessor and its MicroPython JSON transport have no mapping-order
552+
requirement. Consumers require the exact key set and field types; canonical
553+
host-side evidence files retain their separately specified byte ordering.
554+
551555
The schema is integer `1`; `boot_id` is a fresh per-VM 16-byte random value
552556
encoded as 32 lowercase hex characters, not device identity or an
553557
authorization signal. `challenge` echoes this read's fresh host nonce, without
@@ -568,6 +572,12 @@ start in that case. Inspection MUST neither rerun mounting nor modify media.
568572
Fresh source-bound performance/resource and physical qualification gates
569573
apply to all five changed images; the observer does not waive those gates.
570574

575+
The complete-device erased scan accepts a read status only when it is `None`,
576+
boolean `True`, or exact integer zero, matching successful native block-read
577+
outcomes. Boolean `False` is a failed read, not integer-zero success. Floating
578+
zero and custom objects that merely compare equal to zero are uncertain
579+
statuses and MUST NOT grant format authority, even with an all-erased buffer.
580+
571581
### 4.8 Execution modes (FR-MODE)
572582

573583
- **FR-MODE-1** — The agent MUST support **agent mode (idle)**: advertising and/or connected, servicing PBLE/1 file/info/console-input commands with no user program executing; `RUN_STATE` reports `idle`. — *(source: PRD §10.6, [protocol.md §6](../protocol.md#6-run--stop--console); verify: HIL, conformance; story: F-03, F-12)*

0 commit comments

Comments
 (0)