Underlying these models is the observation that the primary B2C job is [providing structure for context and memory] (Obs_StructureContextMemory). However, the taxonomy faces internal friction; a recent reclassification of a [beta user from outside tech] (Archetype_KnowledgeRichConsumer) highlighted a [typology axis collision] (Position_TypologyAxisCollision) between AI-fluency and distribution-motion. Furthermore, the founder's own usage patterns serve as a [cautionary research baseline] (Position_FounderAsPoorUserExample), as typical users may not maintain their graphs with the same rigor. Strategic focus is currently directed toward [architecture and standards teams] (Narrative_ArchitectureTeamsBeachhead) as an ideal beachhead, with [operations personnel] (StyleObs_OpsPersonaQuote) identified as a high-pain target for pitch development.
Sub-areas
Archetype KnowledgePackager5 nodes The Knowledge Packager archetype names a distribution motion — experts who want to package and distribute existing knowledge — separable from AI-fluency. Its sharpest definitional …
Witness phrases
verbatim 90% of what I see people chasing though is structure for context and memory.
verbatim I'm a poor example of a user because I am the power user par excellence
verbatim Look for operations people because they've got the most chaotic job right now... We're making 75 decisions a day.
verbatim The fluency-vs-distribution axis collision may misclassify others in the typology
verbatim The typology may be fundamentally flawed due to the collision of AI-fluency and distribution-motion axes.
verbatim The 'Tinkerer' archetype presents a barrier to adoption because existing 'shitty-but-working' solutions are already entrenched.
verbatim Foundational usage patterns (the founder as power user) may create a disconnect between product design and typical user behavior.
In this area
ClaimArchetype_KnowledgeRichConsumer Archetype C2: The Knowledge-Rich Consumer. People like a beta user from outside tech who have deep domain knowledge but are consumers of AI technology, not tinkerers. Use Claude or ChatGPT. May be the first time they've used a tool that pro
ClaimArchetype_Tinkerer Archetype C1: The Tinkerer. Programmer or programmer-adjacent who has already hacked together context management (CLAUDE.md files, custom prompts). It works but is siloed, non-collaborative, not portable across repos. the customer's chief a
ClaimArchetype_TrustSeeker Archetype B: The Trust Seeker. Already using AI, can't verify output. Executives, ops leads. Pain: 'I don't know if this is right / my team is using AI and I can't tell what it's making up.' These are daily users, not just buyers. Maps to t
Narrative_ArchetypeTaxonomyRestructured Archetype Taxonomy: Whose Expertise × In What Context × Who Consumes
NarrativeNarrative_ArchitectureTeamsBeachhead Architecture Teams as Beachhead
ObservationObs_FounderPowerUserQuote Scarlet's self-diagnosis as a poor user example — the power user par excellence whose graph stays current in ways typical users' will not.
ObservationObs_StructureContextMemory Tony's observation that 90% of what people are chasing is structure for context and memory — the core JTBD for aswritten's B2C market.
StyleObservationStyleObs_OpsPersonaQuote Look for operations people because they've got the most chaotic job right now... We're making 75 decisions a day.
5 further nodes are not published in the public projection. Each node links from the entity index.