Skip to content

Memory prototype runtime

2026-09-15 KST

Runtime contract

prototypeStorage is a module-owned Map with a Storage-shaped API. It is not an alias for browser storage. Domain modules can share snapshots without persistence beyond the current document. Existing injected repositories keep domain seams for testing, but production frontend resolvers select only their local adapter. No environment flag can select Supabase.

prototypeDemoSession owns public fixture identities, in-memory signup and passwords. authSession applies existing role/module UI restrictions to that local identity. This client-side model provides no real authorization. A future real product needs a separately reviewed authentication and data-service boundary, not a secret or live client key added here.

useMemberForm owns the list and selected record together. Row selection passes its identity; saving a card or record updates that row, creation assigns a unique management code, and local deletion updates selection. useCounterparties owns its existing shared master and all fourteen primary/secondary contact fields. Management/registration identity remains immutable on edit.

Accounting print preview uses SPA routing and shares the current document's payload. Language preference and stale chunk recovery may use browser storage. Business/auth modules may not.

Extension workflow

Add a field to its domain fixture/model, derive list/detail from the same store, add validation and interaction tests, then use existing EDS patterns. Do not add a DB migration or call a production API for a visual prototype change. Retain loading/empty/error UI states where useful for demonstration. Do not show successful payment, message sending, public-data lookup or identity verification when no corresponding simulation exists.

Current limits

Local adapters that previously returned empty/unavailable still do so for unimplemented workflows. This conversion is not a feature-completion claim for hospitality, collections, provisional settlement, property occupancy linking or external provisioning. Backend-shaped normalizers and reference tests can remain without shipping a backend connection.

Validation

Required: repository full review gate; memory runtime tests; role/module guards; real built-route sign-in, record edit/reopen, SPA navigation, reload reset, and business-network request checks. See the review report in docs/process/ for actual results rather than assuming this checklist passed.