Dagr Analytics Repo Orientation

Why not?

• The repository is not an ad-tech system, recommendation engine, identity profiler, or claim-governance authority.(semantic trap / refusal)
• It does NOT own:(semantic trap / refusal)
• It does not govern them.(semantic trap / refusal)
• Do not fingerprint a browser to decide it "must be an agent.(semantic trap / refusal)
• Do not infer:(semantic trap / refusal)
• Do not ratify this exact public schema until proving lanes establish field needs.(semantic trap / refusal)
• Never require a persistent person identifier merely to count page views.(semantic trap / refusal)
• No blanket "share my memory graph.(semantic trap / refusal)
• Do not silently splice historical series.(semantic trap / refusal)
• Do not start with one ambiguous counter.(semantic trap / refusal)
• No one data warehouse should implicitly collapse all three.(semantic trap / refusal)
• Do not optimize likes/dwell time.(semantic trap / refusal)
• Do not introduce it as ceremony before a use case requires it.(semantic trap / refusal)
• Do not silently derive sensitive personal attributes from activity merely because they are statistically predictable.(semantic trap / refusal)
• Do not cryptographically sign every click.(semantic trap / refusal)
• Do not begin with Amnesiac.(semantic trap / refusal)