Staleness isn't solved yet - honest answer is manual curation for now. age_days is on every memory so clients can factor it in, but there's no automatic decay.
It's on the roadmap. I wanted retrieval solid before layering temporal complexity on top. Longer term — age-weighted scoring, surfacing "this is 6 months old" in the MCP response metadata.
For the moment there is scoping feature that allows you to store & filter which helps narrow down retrieval.
Perhaps there is an upshot. If the Chinese government have complete access to all traffic in China, they will be unable to deny knowledge of hacking originating from their own IP blocks. By the same token you would expect that all unlawful traffic originating in China to cease.
It's on the roadmap. I wanted retrieval solid before layering temporal complexity on top. Longer term — age-weighted scoring, surfacing "this is 6 months old" in the MCP response metadata.
For the moment there is scoping feature that allows you to store & filter which helps narrow down retrieval.