Data And Functions Backend

Purpose

Use Subterranean's built-in database path before inventing custom persistence.

Default data approach

• Model persisted records as Data tables.
• Let generated Functions handle standard table operations.
• Use custom api/*.ts routes for validation, composition, and product-specific workflows around those tables.

Design process

1. Identify the product's core data objects.
2. Define table names, field names, field types, required fields, and useful descriptions.
3. Keep initial schemas small and aligned with the first product slice.
4. Use user-facing labels that match the product language.
5. Explain which UI actions read from, write to, or transform each table.

API route guidance

• Keep route handlers focused on one workflow.
• Validate inputs at route boundaries.
• Return useful error messages for the UI.
• Avoid direct database assumptions when generated Functions already cover the need.

Handoff

When backend work is complete, report the tables/functions/routes added and how the frontend calls them.