From agent trace to decision: measuring cost per outcome

From agent trace to decision: measuring cost per outcome A data-flow diagram generated by Archify. 01 / Capture 02 / Attribute + score 03 / Join 04 / Store 05 / Decide Agent sessions · traces · tokens · tools · 01 / Capture · instrumented Agent sessions traces · tokens · tools instrumented Users & staff · feedback · escalations · 01 / Capture · signals Users & staff feedback · escalations signals Cost attribution · per task · per feature · 02 / Attribute + score · spend Cost attribution per task · per feature spend Business outcomes · resolved · converted · 02 / Attribute + score · KPI Business outcomes resolved · converted KPI Quality evals · judges + rubrics · 02 / Attribute + score · quality Quality evals judges + rubrics quality Outcome join · task · result · cost · 03 / Join Outcome join task · result · cost Metrics store · cost per outcome · 04 / Store · trended Metrics store cost per outcome trended Weekly review · 3 charts, worst runs · 05 / Decide · people Weekly review 3 charts, worst runs people Budget guard · ceilings + alerts · 05 / Decide · limits Budget guard ceilings + alerts limits tokens + tools per session sampled traces sampled labels human cost per task spend business KPI result pass or fail quality cost per outcome derived weekly trends read-only spend vs ceiling guardrail Legend primary data policy / PII async batch data store data flow