Prototype frontend / backend boundary

2026-09-15 KST

leyve-console-proto now uses browser-document memory for UI prototyping. Its frontend does not send business queries, mutations, authentication or password-reset requests to a backend.

The repository's historical supabase/ source, migrations, functions and SQL smoke tests remain reference material. They were not deleted, executed, deployed or changed by this conversion. Existing hosted databases, server functions, stored data and infrastructure are outside this task.

Earlier backend handoffs describe proposed or historical production contracts, not the current prototype's runtime. Preserve identifier, scope, validation and business invariants when designing a future production service, but do not treat in-memory role guards as security or memory saves as durable transactions. Adding production behavior requires its own reviewed DB/API/authentication design and release authority.

The fourteen counterparty contact fields are editable in prototype memory. This does not claim the historical server schema stores those fields. There is no automatic migration or synchronization between prototype edits and live records.