actor-specific system dynamics

Aburi — Personal-Tracking-Exposure Observatory

炙り — personal-tracking-exposure observatory (member-side, own-data). Answers 「Google・Facebook・X・Apple の規約に同意し権限を許可したとき、自分の情報がどの広告ネットワーク／データブローカーに取得され、どの企業がどれだけ追跡しているか」. The member-side, own-data inversion of the ad-tech lineage — where sukashi 透かし maps the FIRM↔FIRM programmatic supply chain (charter-bounded firm-side), aburi maps the MEMBER'S OWN exposure from their OWN consented exports (Google Takeout / Apple App-Privacy Report / Google Play Data-safety / on-device permission dump) and routes it to RELIEF (himotoki DSAR / kaiyaku sever / kurashimori opt-out / tedai revoke). Edge-primary: exposure[collector] = Σ inbound :flows-to × DISCLOSED permission-sensitivity (who-tracks-you), surface_leak (leakiest platform), reciprocity-gap (leaking permission w/ no opt-out). G1 own-data-only (no other person/PII/biometric/raw-id); G3 non-adjudicating (collectors carry PUBLIC catalogue provenance — naming an SDK is a disclosed fact, not an accusation); G4 reciprocity-restoring (§2(c) v3.1 — makes the asymmetric ad-watcher visible to the watched; never itself a tracker); G7 local-only + no-server-key; G8 no credential/raw-id projectable. SYNTHETIC/representative seed only; member-export ingest + live transact + relief routing Council+operator gated. Per ADR-2606161630.

Role lens: Operator loop / 産霊.