Cobalt — Mutations

To implement optimistic UI updates while maintaining server-side data consistency, use a dual-lane strategy combining Zero custom mutators for instant web feedback with Hono REST endpoints for robust server-side validation. Both paths share the same underlying Drizzle mutation logic to guarantee data integrity.

The best way to standardize data mutations across web and mobile clients is to define a unified architectural pattern using Zero custom mutators for web optimistic UI and Hono RPC endpoints for cross-platform writes. This enforces Zod validation and ownership-by-filter security constraints across all consumers.

To add a new data mutation supporting instant web feedback and external webhooks, implement a Zero mutator for the web client's optimistic UI and a corresponding Hono REST endpoint for webhook support. Both must adhere to the established Drizzle schema and Zod validation rules.

Yes, Zero supports server-authoritative ownership checks by enforcing ZQL filters and Zod validation. This integration prevents unauthorized data modification by ensuring all custom mutators and REST endpoints respect ownership-by-filter security constraints defined in the Drizzle schema.

You should use Zero custom mutators when you need optimistic UI write paths for web clients, and Hono REST endpoints for non-optimistic writes, mobile applications, or external consumers. Both approaches share the same underlying Drizzle mutation logic for data consistency.

Optimistic UI writes fail Zod validation on the server when the client-side mutator payload does not adhere to the established Drizzle schema constraints. Ensure your Zero custom mutators and Hono REST endpoints share the exact same underlying Drizzle mutation logic and Zod validation schemas.