Oh yeah, Dane mentioned about removing the knot/repo since its not being used actively. (sorry, just now noticed this comment!)

thanks Tynan. very much interested to see how it looks on a TRMNL. 

haha, that would be cool. please share it if you do get a chance to build it. hardware + atproto has lots of potential IMO.

haha, Thanks Tynan!

On a serious note though, there should be a layer to the left of the App block in the diagram called App Backend ( which acts as a  View Aggregator), and we should also call out the Private App Data Store (PADS?) that already exists in the architecture. For example, bluesky uses them for bookmarks etc and leaflet uses it for drafts. The backend/aggregator is the layer that aggregates data from both the PDS and private store before presenting it to the app.This would also resolve confusion about people saying data (like bookmarks) is stored in the AppView, which should have always been understood as a presentation layer.

Or an App-P-I server.