Semantic value boundaries

Sapporta preserves semantic table values across generated forms, HTTP, application code, Grid, and SQLite. Use the leaf that owns the boundary you are implementing:

• Generated and client values covers the end-to-end value matrix, select-backed text, create-form drafts, and Grid editor decoding.
• Server write values and contracts covers authoritative prepared writes, structural schemas, Temporal conversion helpers, application contracts, and public SQL names.

A primary key in an address position — a URL segment, a query key, a grid row key — is a RecordId, and Table lookups and record ids owns that crossing.

For table declaration syntax, start with Table definitions. For operation-aware application issues, use Table validation.

Related documentation

• Generated record surfaces and form helpers
• Table endpoints
• Serialization and API errors