Skip to content

docs(site-memory): distinguish entry expiry from backing-file cleanup #108

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
senamakel merged 1 commit into from
Oct 17, 2026
Merged

docs(site-memory): distinguish entry expiry from backing-file cleanup #108

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions crates/tinycomputer-bus/src/site_memory/mod.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
//!
Expand Down
Loading