Versioned and Auditable by Design

Tavlon is designed to preserve table definitions over time. When a table definition changes, the change can be stored as a new version instead of silently replacing the previous structure.

This makes table definitions easier to review, compare, restore, and explain. A versioned table definition gives teams a record of how the structure changed and when those changes were made.

Why Versioning Matters

Tables often evolve. Columns may be renamed, optional fields may become required, and repeating sections may be added as business needs change. Without version history, these changes can be hard to track.

Text Definitions Make Changes Visible

Because Tavlon definitions are text-first, changes to table structure are easier to see. A column added to a definition, a renamed field, or a new repeating section can be reviewed as part of the table history.

            Locations: {{
            header: {{
            Name,
            Address,
            Array Shifts (...)
            }}
            }}
        

A definition like this can be stored, changed, and versioned. The structure remains readable, and the history of the definition remains available for review.

Designed for Auditability

Auditability means the table structure is not hidden inside a final document or spreadsheet. Tavlon keeps the definition visible as a managed source. This helps explain what changed, why a table appears the way it does, and which definition was used to produce an output.