Follow-up to #3801. /calculate still writes every household's tracer output to the runtime cache (policyengine_api/runtime_cache/household_traces.py, wired in household_calculation_service.py, family household-trace). Its only consumer was the tracer-analysis endpoint, which #3801 removed, so the write is now dead weight on the most important endpoint: extra Redis traffic and serialization per calculation.
Worth removing, but as its own change: it touches /calculate, so it deserves a contract check that the response shape (tracer_output in the calculation result) is unaffected — or a decision to keep storing traces for a future (Axiom-era) explanation feature.
Follow-up to #3801.
/calculatestill writes every household's tracer output to the runtime cache (policyengine_api/runtime_cache/household_traces.py, wired inhousehold_calculation_service.py, familyhousehold-trace). Its only consumer was the tracer-analysis endpoint, which #3801 removed, so the write is now dead weight on the most important endpoint: extra Redis traffic and serialization per calculation.Worth removing, but as its own change: it touches
/calculate, so it deserves a contract check that the response shape (tracer_outputin the calculation result) is unaffected — or a decision to keep storing traces for a future (Axiom-era) explanation feature.