C08-RT: Yes

Archived previous-definition assessment — revision 4.72. Retired in 5.73; excluded from the active matrix and counts. This historical verdict is not a current assessment.

Rationale

The prior No correctly identified activity-bearing destination-table writes, but also rejected volatile storage because RAM records remain after communication. That was inconsistent with the bounded volatile-storage interpretation used for C08 elsewhere. Reticulum accepts an explicit config directory and derives storage, cache, resources, identities and blackhole paths beneath it. Transport startup loads destination_table only when present; its absence is not a startup requirement failure. With the whole runtime directory on verified noswap tmpfs, static local provisioning restored separately and no durable logs or memory exports, normal persistence calls write volatile files. This supports Yes for the explicit deployment, while stock disk-backed operation still records activity. Live RAM records and post-restart relearning remain; no deletion-at-session-end or anonymity guarantee is implied.

Assessment method

Pinned source and official configuration documentation; no execution

Source context

Reticulum 1.5.5 configuration root, optional path loading and persistence

Outstanding qualification

Verify every selected serial-interface/cache/log destination stays within the volatile root or a nonpersistent sink; forbid external path overrides and persistent process dumps/swap. Start from static provisioning without destination_table, allow announces/path discovery, exercise forwarding and persistence, then cold-restart and verify relearning without importing activity histories. No such protocol or mount experiment ran in this review.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.

round132-sources.json