From 9d0f6f0213f2a552c5fd42349706b2c07154c259 Mon Sep 17 00:00:00 2001 From: Steven Enamakel Date: Sat, 17 Oct 2026 09:06:53 +0530 Subject: [PATCH] docs(site-memory): clarify backing-file maintenance ownership --- crates/tinycomputer-bus/src/site_memory/mod.rs | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/crates/tinycomputer-bus/src/site_memory/mod.rs b/crates/tinycomputer-bus/src/site_memory/mod.rs index 45b20262..8e5969be 100644 --- a/crates/tinycomputer-bus/src/site_memory/mod.rs +++ b/crates/tinycomputer-bus/src/site_memory/mod.rs @@ -4,9 +4,13 @@ //! The module returns, with every finished task, the plan it ran and the //! elements its steps found, and takes them back on the next task on that //! site. It keeps nothing between tasks itself, so the host serves this -//! interface and decides only *where* the bytes live (a file, a storage -//! port). The reuse rules, the fact-value filtering and the 30-day expiry -//! are the module's (`tinycomputer-core::sites`), not the host's. +//! interface and owns where the bytes live (a file, a storage port). The +//! reuse rules, the fact-value filtering and each plan's or hint's 30-day +//! freshness are the module's (`tinycomputer-core::sites`), not the host's. +//! +//! A host may also periodically remove unchanged backing files as physical +//! storage maintenance. Schedule that cleanup outside `Load` requests; it is +//! independent of the module's per-plan and per-hint freshness rules. //! //! Three members, all synchronous request/response over plain data: //!