The project moved quickly from interface components to a coherent shared object. Local identity, membership roles, invitations, case creation, sync-ready records, and file-backed persistence arrived as related changes on 14 March.
That sequence clarified the central idea. A case is not merely a title above a message thread.
It has participants with relationships to the work, invitations that can change those relationships, stable records that can cross a transport boundary, and local state that survives an app restart.
Later messaging and lifecycle work could build on those explicit domain boundaries instead of inferring the case from a generic conversation.
← Back to CASES