account-state

Create an XState class under model/nipXX modeled on MuteListState or BookmarkListState, pin the addressable note with cache.getOrCreateAddressableNote, expose a StateFlow via stateIn, and instantiate it in Account.kt. Mutation helpers build and sign the updated event, which the caller publishes.

Use LocalCache.getOrCreateNote when rendering a specific note or user by id. Use account.<feature>.flow when rendering user-specific state like follows, mutes, or relay lists. For feeds, use a FeedFilter with FeedViewModel instead of scanning LocalCache.

LocalCache is a singleton holding LargeCache maps of notes, users, and addressables. Incoming relay events are parsed into typed Event subclasses, inserted via insertOrUpdateNote, and indexed by hashtag, address, and deletion status.

No, LocalCache is a process-global singleton shared across accounts. Switching accounts does not wipe it; the new Account re-derives its StateFlows from the same underlying cache.

MemoryTrimmingService evicts least-recently-used notes and users from LocalCache under Android memory pressure. Previously returned Note references remain usable but detached, so do not assume a seen note stays resident.