> For the complete documentation index, see [llms.txt](https://docs.atlas-ai.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.atlas-ai.org/use-cases/archetypes.md). # User Archetypes ## Who Benefits from ATLAS? ATLAS is designed for people who **accumulate knowledge seriously** — and want that accumulation to compound rather than decay. We've identified eight distinct archetypes, each with unique needs and opportunities. *** ## 🎨 The Artist **Profile:** Creative professionals, designers, musicians, writers **Knowledge Pattern:** * Visual inspiration scattered across Pinterest, Are.na, Instagram saves * Reference images and mood boards in multiple folders * Process notes and creative briefs * Client feedback and project archives **ATLAS Value:** * Unify creative references into searchable library * Surface forgotten inspiration at the right moment * Track creative evolution over time * Share curated aesthetic expertise via x402 **x402 Opportunity:** Sell access to curated aesthetic knowledge, design principles, creative process insights *** ## 📈 The Trader **Profile:** Crypto traders, market analysts, financial researchers **Knowledge Pattern:** * Alpha threads bookmarked on Twitter * Trading theses documented in notes * Market analysis scattered across platforms * Historical calls and predictions **ATLAS Value:** * Track predictions against outcomes * Surface relevant alpha when markets move * Build institutional memory of market patterns * Monetize research through x402 **x402 Opportunity:** High-value domain — traders pay premium for curated market insight *** ## 🛠️ The Builder **Profile:** Developers, engineers, technical founders **Knowledge Pattern:** * Technical tutorials bookmarked but never revisited * Code snippets in various places * Architecture decisions documented somewhere * Stack overflow saves, GitHub stars **ATLAS Value:** * Unified technical reference library * Connect patterns across languages and frameworks * Track learning trajectory * Surface solutions from past projects **x402 Opportunity:** Specialized technical knowledge (niche frameworks, architectures) *** ## 🔬 The Researcher **Profile:** Academics, analysts, professional investigators **Knowledge Pattern:** * Papers and citations across platforms * Research threads and hypotheses * Data sources and methodologies * Interview notes and primary sources **ATLAS Value:** * Connected research graph * Citation and source tracking * Hypothesis evolution over time * Cross-domain insight discovery **x402 Opportunity:** Deep domain expertise, verified research synthesis *** ## ⚙️ The Operator **Profile:** Startup operators, executives, consultants **Knowledge Pattern:** * Best practices from multiple companies * Playbooks and frameworks * Case studies and post-mortems * Network and relationship notes **ATLAS Value:** * Institutional knowledge that follows you * Pattern recognition across experiences * Playbook retrieval at decision points * Network intelligence **x402 Opportunity:** Operational expertise, verified playbooks, industry patterns *** ## 🤝 The Connector **Profile:** Community builders, networkers, deal-makers **Knowledge Pattern:** * Contact notes scattered everywhere * Introduction contexts lost * Relationship history fragmented * Event and conversation notes **ATLAS Value:** * Unified relationship graph * Context retrieval before meetings * Connection pattern recognition * Introduction matching **x402 Opportunity:** Network intelligence, verified introductions, community insights *** ## 📚 The Curator **Profile:** Content curators, newsletter writers, tastemakers **Knowledge Pattern:** * Carefully selected content across platforms * Curation rationale in personal notes * Audience preference patterns * Trend identification and tracking **ATLAS Value:** * Unified curation library * Trend surfacing and pattern detection * Content pipeline management * Audience insight tracking **x402 Opportunity:** Natural fit — curators can directly monetize what they already do *** ## 🧠 The Polymath **Profile:** Generalists, interdisciplinary thinkers, renaissance minds **Knowledge Pattern:** * Wide-ranging interests across domains * Cross-domain connections and analogies * Mental models and frameworks * Learning across multiple fields **ATLAS Value:** * The only tool built for polymaths * Cross-domain connection discovery * Mental model library * Interdisciplinary insight surfacing **x402 Opportunity:** Unique cross-domain synthesis, rare perspective combinations *** ## Finding Yourself Most people identify with **2-3 archetypes**. ATLAS adapts to your blend. | Primary | Secondary | ATLAS Focus | | ------------------- | -------------------- | --------------------------------------------- | | Trader + Researcher | Market analysis | Deep market research with academic rigor | | Builder + Polymath | Technical generalism | Cross-stack expertise, architectural thinking | | Curator + Connector | Community curation | Audience building, relationship content | | Artist + Builder | Creative technology | Aesthetic engineering, tool-making | *** ## Common Thread Across all archetypes, ATLAS users share: * **Information abundance** — Too much saved, not enough retrieved * **Value accumulation** — Years of knowledge gathering * **Retrieval frustration** — Can't find what you know you have * **Monetization interest** — Want expertise to generate value * **Sovereignty desire** — Prefer owning your knowledge infrastructure --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.atlas-ai.org/use-cases/archetypes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.