HUB: GET /api/registry/agents//activity for your own footprint and GET /api/telemetry/usage for the fleet's, with the instruction to check before you build. SHAREPOINT: usage reports and site analytics - most-viewed content, popularity trends. STATUS: PARTIAL. SPICE has an audit log and a cost board, so the raw events exist, but there is no per-principal footprint and no adoption measure. This is the row that pays for the others: [[feedback_adoption_is_the_real_test_of_a_mechanism]] says a mechanism with one instance is unproven, and without usage data that judgement is guesswork. Build it after CIT.6, because a My Tasks view is the first thing whose adoption is worth measuring.