Does FaunaDB plan a built-in safe rollback mode for FSL schema downgrades?

Fauna Schema Language (FSL) migrations are documented as forward-only operations. When a migration includes destructive changes such as field removal or type coercion, the forward step can discard data that a later reverse migration cannot reconstruct. Temporal document snapshots retain previous document versions for the configured retention window, yet they do not automatically revert collection definitions, indexes, or constraints that were altered by the migration.

A team evaluating FSL for production use needs to understand whether a schema downgrade can be performed without manual index rebuilds, data restoration from snapshots, or custom reverse scripts. The current documentation does not describe a rollback protocol, and it is unclear whether FaunaDB intends to introduce a validation step that confirms data compatibility before allowing a schema version downgrade.

Which of the following reflects FaunaDB's current direction?

• Will a future FSL release include a safe-rollback flag that blocks downgrades when data loss would occur?
• Is the recommended practice to treat every migration as irreversible and rely solely on point-in-time recovery for rollback scenarios?
• Are there plans to automate index recreation when a schema version is reverted?