Transparency Trail Overview Operation History ↳ Preprocessing Audit Log ↳ Outlier Exclusion Log ↳ p-Hacking Detection Data Provenance ↳ N Disclosure ↳ Analysis Family Ledger ↳ Software & Version

Transparency Trail

Transparency Trail keeps the figure, its recorded preprocessing context, and its disclosure state connected through export review. When a reviewer asks how data were filtered, excluded, or framed for analysis, Licklider surfaces the relevant record instead of relying on memory.

What is Transparency Trail?

Transparency Trail is Licklider's record of what affected an exported result. It combines recent preprocessing context, exclusion history, analysis-family information, N disclosure, and version provenance so researchers can review what was done before results leave the platform.

The goal is not a particular log format. The goal is that output-facing disclosures remain tied to the same figure state that was actually analyzed and reviewed.

Transparency Trail covers two categories: Operation History captures what was done to the data in the current workflow. Data Provenance captures where the data came from, how many observations remained, and which software context produced the export.

Operation History

Operation History focuses on preprocessing summaries, outlier handling, and risk signals from repeated analysis choices. It helps researchers disclose what changed in the data and what should be acknowledged before claim-bearing export.

Data Provenance

Data Provenance covers the rest of the export context: how many observations were analyzed, which related analyses belong to the same dataset family, and which app, ruleset, backend, and model versions produced the current output.