Liquibase changelog layout for a service, ORM- and framework-agnostic. Use when adding or editing a migration, organizing changelogs, or choosing a changeset format. One YAML changelog file per table (the whole history of that table in one place); a master changelog includes the per-table files; changesets are additive-only and immutable once shipped — to change a table, append a new changeset, never edit one in place. Raw SQL only via sqlFile when a change can't be expressed declaratively.