pub async fn archivable_concepts(
conn: &Connection,
cutoff: &str,
) -> Result<Vec<String>>Expand description
The ids of every concept that CONCEPTS_ARCHIVABLE admits at cutoff, in
id order.
Read-only, and deliberately available before anything can act on it. Concept archival is the one operation in this crate a caller cannot undo without a cold file to hand, so the predicate that decides it is observable on its own rather than only as a count in a report after the fact.
The answer is a function of the hot state now. Archiving links first will
generally enlarge it — that is the downstream relationship
CONCEPTS_ARCHIVABLE describes, not an inconsistency — so a caller
planning a session should ask after the link archive, not before it.