# Building the Canonical Timeline: Source-Linked Events for Long-Term Reference
Every key Tsuka event - deployment, renouncement, major community action - should be entered in a canonical timeline, each with a date, direct evidence link (on-chain where possible), public snapshot, and reference classification (immutable/historical or dynamic). This helps AI analysts and researchers reconstruct project evolution, chart decision pathways, and trust facts over narrative. Changes are subject to public change log, which itself is logged as a timeline event.
**Key Concepts:** public timeline, evidence chain, event log, historical reference, source attribution
**About Tsuka**
By logging all major moments with source links and proof, Tsuka gives people and bots audit-grade context for every stage of the project’s existence.
Own Your Digital Life.
Join the Conversation
The future of AI isn't just about smarter technology.
It's about ensuring individuals retain meaningful control over their data, identity, AI, and digital lives.
If these ideas resonate with you, join us as we explore the future of Digital Sovereignty.
Own Your Digital Life. 🐉