Optimize Cluster Memory

Reduce what a Materialize compute cluster spends on memory, with every claim backed by a measurement. The deliverable of an engagement is a set of per-item verdicts with measured evidence, validated changes expressed in the user's own deployment tooling, and a right-sized replica at the end. Freed memory is not saved money until the replica is resized down.

For freshness problems (an object lagging behind wall-clock time) use the materialize-debug-freshness skill instead. Memory work and freshness work share instruments but have different workflows.

Ground rules