Solid Vue Development

State vs. Behavior

• State = what something is → reactive refs on the owner of that concern
• Behavior = what something does → named functions (signIn(), getTemplate())
• Never model a process as state. If you're naming refs after verbs (isLoading, hasFetched, shouldRefresh), the process has escaped into the wrong layer.

Component Boundaries

• Components call functions. They don't own logic that belongs to a manager or service.
• Auth, sync, Drive, encryption — these have dedicated owners. Components receive state and call methods; they don't implement.

Manager Pattern

• Encapsulate a domain's state AND behavior in a single manager (e.g. GoogleDriveConnectionManager).
• The manager exposes reactive state for the UI to read and named functions for the UI to call.