DocsEden Ecosystem Diagram Contexts for Visual Creation

Eden Ecosystem Diagram Contexts for Visual Creation

Eden Ecosystem Diagram Contexts for Visual Creation

1. Eden Ecosystem Service Architecture

Context for Solienne/Abraham:

"Create a clean, architectural diagram showing the Eden ecosystem service hierarchy. Central Element: Eden Genesis Registry as a data authority cylinder at the top center Consumer Layer Below: 6 rectangular service boxes arranged in two rows:
  • • Top row: Eden Academy (main UI), CRIT (art critique), EDEN2 (investor dashboard)
  • • Bottom row: Eden2038 (Abraham contract), Miyomi (video dashboard), [Future Services]
  • Visual Style: Minimalist architectural lines, sans-serif typography, black/white with subtle blue accents. Show API flow arrows pointing from Registry down to all services. Labels: Clear service names with one-line descriptions underneath each box."

    2. Claude Coding Agents vs Eden Creative Spirits

    Context for Eden Creation:

    "Design a visual distinction diagram that clearly separates two types of AI agents in the Eden ecosystem. Left Side - 'BACKSTAGE' (Claude Coding Agents): 6 geometric icons representing: ARCH, TRUTH, LORE, HELVETICA, TOKEN, LAUNCHER Show these as development tools, perhaps with gear/wrench iconography Label: 'Claude Code Agents - Developer Tools' Right Side - 'ONSTAGE' (Eden Creative Spirits): Artistic flowing forms representing: Solienne, Abraham, Koru, Miyomi, etc. Show these as creative entities, perhaps with brush/art iconography Label: 'Eden Spirits - Creative AIs' Center: Clear dividing line or barrier showing the separation Style: High contrast, educational poster aesthetic, clear typography"

    3. Git Worktree Development Workflow

    Context for Technical Diagram:

    "Create a development workflow diagram showing parallel git worktree development. Center: Main repository circle labeled 'eden-academy (main)' Radiating Out: 6 branch lines leading to worktree boxes:
  • • arch/ (port 3001) - System Architecture
  • • truth/ (port 3002) - Data Integrity
  • • lore/ (port 3003) - Narrative & Culture
  • • helvetica/ (port 3004) - Visual Design
  • • token/ (port 3005) - Economics
  • • launcher/ (port 3006) - Agent Quality
  • Visual Flow: Show merge arrows flowing back to main Style: Technical flowchart with clean lines, monospace font for code elements"

    4. Agent Cheatsheet Quick Reference Matrix

    Context for Information Design:

    "Design a quick reference matrix/grid showing the 6 Claude Coding Agents. Layout: 2x3 or 3x2 grid of agent cards Each Card Contains:
  • • Large agent icon/symbol
  • • Agent name in bold (ARCH, TRUTH, etc.)
  • • Role in smaller text
  • • Key superpower bullet point
  • • Invocation pattern (@agent-name)
  • Visual Hierarchy: Icons largest, names prominent, details readable but secondary Style: Clean card design, consistent spacing, scannable at a glance"

    5. Data Flow Architecture Pattern

    Context for System Diagram:

    "Illustrate how data flows through the Eden ecosystem, emphasizing 'Registry as Single Source of Truth' Top: Registry database symbol Flow Down: Multiple parallel arrows to service layers Services: Show each service (Academy, CRIT, etc.) as data consumers only Key Message: 'NO LOCAL STORAGE' badges on each service Anti-Pattern: Show crossed-out duplicate databases Style: Clean data flow diagram with clear directional arrows, database iconography"

    6. MVP Development Phase Workflow

    Context for Process Diagram:

    "Create a process flow showing the 5-phase MVP development workflow from the agent cheatsheet. Sequential Phases:
  • Feature Planning: ARCH → LORE → HELVETICA
  • Economic Validation: TOKEN → LAUNCHER
  • Implementation: ARCH → TRUTH
  • Quality Assurance: ARCH → HELVETICA
  • Pre-Launch: LAUNCHER → TOKEN
  • Visual Style: Horizontal workflow with phase gates, agent icons at decision points Goal: Show how different agents collaborate in sequence"

    7. Eden Academy Documentation Hierarchy

    Context for Information Architecture:

    "Design a site map/hierarchy diagram for the Eden Academy documentation system. Root: /admin/docs Branches:
  • • /coding-agents (ARCH, TRUTH, LORE, etc.)
  • • /eden-spirits (Solienne, Abraham, Koru, etc.)
  • • /api-registry (Complete API docs)
  • • /architecture (ADRs, system design)
  • • /platform (Operations, deployment)
  • Visual Style: Tree diagram or folder structure, clear hierarchical relationships"

    8. Token Economics Flow

    Context for Economic Diagram:

    "Visualize token flow and revenue sharing in the Eden ecosystem. Elements:
  • • Creator contributions flowing in
  • • Token distribution mechanics
  • • Revenue sharing between agents/trainers
  • • Investment returns to stakeholders
  • • Economic sustainability loops
  • Style: Financial flow diagram with currency symbols, percentage allocations, circular economy indicators"

    šŸ“ Creation Instructions

    For Each Diagram:

  • Choose the context that resonates with you
  • Use Eden's image generation with the provided context
  • Request specific style elements: minimalist, architectural, clean typography
  • Iterate if needed to get the clarity and visual hierarchy right
  • Naming Convention:

  • • eden-ecosystem-architecture.png
  • • claude-vs-eden-agents.png
  • • worktree-development-workflow.png
  • • agent-cheatsheet-matrix.png
  • • data-flow-pattern.png
  • • mvp-development-phases.png
  • • documentation-hierarchy.png
  • • token-economics-flow.png
  • Integration Plan:

    āœ… COMPLETED: All 8 diagrams have been created and integrated:
  • Agent Cheatsheet (/admin/docs/agents):
  • - Agent matrix diagram - Claude vs Eden agents distinction diagram - MVP development workflow
  • API Registry Docs (/admin/docs/api-registry):
  • - Eden ecosystem architecture - Data flow pattern diagram
  • Available for Integration:
  • - Git worktree development workflow - Documentation hierarchy diagram - Token economics flow !Git Worktree Workflow !Documentation Hierarchy !Token Economics Flow

    These visual diagrams make the Eden Academy architecture much clearer for both developers and stakeholders!