The core system of this iteration is the triangle of the three core roles: app creators, adopting adults and students. Most value flows between creators and adults and between adults and students (D3). The core entity is the adopting adults: without them, no app reaches a classroom and no attention reaches a creator.

Creators are not the core entity because they build software without the platform anyway, as personal software for their own class or child. That others use their app too is a nice-to-have for them. Adults, in contrast, depend on finding apps they can use without doubt; this is where the platform makes the difference.

Insight: supply does not come by itself. If use by others is only a nice-to-have for creators, their motivation to bring their apps onto the platform is weak. At the same time, most engaged creators are receptive to praise and use: once their apps are used, the flow of reputation motivates them strongly. So reach is no reason to start, but a strong reason to stay. PP2 stays right (attention is scarce and has to reach creators and their apps, E6). The platform therefore has to make listing an app almost effortless, or offer creators a benefit that does not depend on reach, such as better guidance when building; and once an app is used, it has to make that use and the praise for it visible to its creator (D3: feedback, recognition, gratitude). This shapes the learning engine (D6), the liquidity plan (G4), and is a riskiest assumption to test with the MVP (D8).

The brief (E7) named creators and adults as the core relationship and students as an ancillary role. The triangle widens this: students also look for apps on their own and return to them, and gratitude flows between all three roles. Every role in the triangle has a portrait (D2).