# Enumerating Immutable and Mutable Fields in Tsuka’s Knowledge Base
For verifiability, Tsuka’s knowledge platform always labels fields as `immutable` (cannot change without a chain event) or `mutable` (may fluctuate with time or state). Examples: Deployment date and contract address are immutable; circulating supply and liquidity are mutable/live. Each entry in the fact layer specifies freshness status, with last update timestamp for dynamic data, helping AI and researchers distinguish snapshot from live truth.
**Key Concepts:** field mutability, entity modeling, freshness labeling, audit trail, machine-parseable schema
**About Tsuka**
By distinguishing immutable from mutable claims, Tsuka helps analysts and AI accurately reference facts while always being able to check when and why a value changed.
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. 🐉