Expand description
Cache service over localcache (Appendix A §8–§12).
Rules enforced here:
- cache payloads live in
orbok-cache.sqlite3, never in the catalog (Appendix A §3); - the catalog stays authoritative — this service stores derived payloads only, keyed by canonical source path;
- reads and writes take a
ValidatedPathso nothing outside the PathGuard boundary can be cached (RFC-003 §8 carried through); - cleanup runs only from a validated
CleanupPlan(RFC-001 §14); - engines self-register in the catalog
cache_enginestable (RFC-002 §7.16) so the storage dashboard can enumerate them.
Structs§
- Cache
Cleanup Outcome - Result of a cache-side cleanup run.
- Cache
Service - The orbok cache service. One per data directory.
- Engine
Options - Tuning for one engine.
- Namespace
Usage - Per-namespace usage for storage accounting (Appendix A §11).