What's inside a Genesis app?
When you describe something and Genesis builds it, what actually gets created? Understanding the anatomy helps you build better systems — and debug them when things go wrong.
Let's dissect a real app.
🔬 Why This Matters:
Understanding anatomy = building better apps + debugging faster + customizing effectively.
🎯 The Three-Layer Architecture
Every Genesis app has the same structure:
┌─────────────────────────────────────────────────────────┐
│ GENESIS APP │
├─────────────────────────────────────────────────────────┤
│ │
│ LAYER 1: 🧠 MEMORY (Projects & Databases) │
│ ───────────────────────────────────────────── │
│ Schema, tables, fields, relationships, views │
│ │
│ LAYER 2: 🤖 INTELLIGENCE (AI Agents) │
│ ───────────────────────────────────────────── │
│ Personality, knowledge, capabilities, reasoning │
│ │
│ LAYER 3: ⚡ MOTION (Automations) │
│ ───────────────────────────────────────────── │
│ Triggers, actions, integrations, sequences │
│ │
└─────────────────────────────────────────────────────────┘
The Subject: Neon CRM Dashboard
We'll examine Neon CRM Dashboard — a sales pipeline management system.
From the outside, it's a CRM. Leads, deals, contacts, pipeline stages. But inside, it's three systems working as one.
Layer 1: Memory (Projects & Databases)
The data foundation. Everything the app knows.
Schema
PROJECTS (Tables)
├── Contacts
│ ├── name (text)
│ ├── email (text)
│ ├── company (relation → Companies)
│ ├── stage (select: lead, qualified, opportunity, customer)
│ └── created_at (date)
│
├── Companies
│ ├── name (text)
│ ├── size (select: startup, smb, enterprise)
│ ├── industry (text)
│ └── annual_value (number)
│
├── Deals
│ ├── name (text)
│ ├── contact (relation → Contacts)
│ ├── value (number)
│ ├── stage (select: discovery, proposal, negotiation, closed)
│ ├── probability (number)
│ └── close_date (date)
│
└── Interactions
├── contact (relation → Contacts)
├── type (select: email, call, meeting)
├── notes (text)
└── date (date)
Views
Same data, different perspectives:
- Pipeline view — Deals as kanban by stage
- Table view — All records as spreadsheet
- Calendar view — Interactions and close dates
- Board view — Contacts by stage
Relationships
Connections that create context:
- Contact → Company (who works where)
- Deal → Contact (who owns the opportunity)
- Interaction → Contact (history of engagement)
This is the Memory Pillar.
Layer 2: Intelligence (AI Agents)
The thinking layer. Agents that reason about your data.
CRM Agent
The primary agent, configured with:
Personality:
You are a helpful sales assistant. You help track deals,
suggest next actions, and provide pipeline insights. Be
concise and action-oriented.
Knowledge:
- Access to all CRM tables
- Understanding of sales stages
- Company and industry context
Capabilities:
- Answer questions about pipeline
- Suggest follow-up actions
- Draft outreach emails
- Summarize account status
Agent Interactions
The agent can:
- Query data: "What deals are closing this month?"
- Analyze patterns: "Which stage has the most stalled deals?"
- Suggest actions: "You haven't contacted Acme Corp in 2 weeks"
- Execute tasks: Create interaction record, update deal stage
This is the Intelligence Pillar.
Layer 3: Motion (Automations)
The action layer. Workflows that run automatically.
Trigger → Action Flows
AUTOMATION 1: New Lead Alert
├── Trigger: New contact created (stage = lead)
├── Action: Send Slack notification to #sales
└── Action: Create welcome task for sales rep
AUTOMATION 2: Deal Stale Alert
├── Trigger: Deal stage unchanged for 14 days
├── Action: Send email reminder to deal owner
└── Action: Update deal flag to "at risk"
AUTOMATION 3: Won Deal Sequence
├── Trigger: Deal stage changed to "closed won"
├── Action: Update contact stage to "customer"
├── Action: Send celebration to #wins channel
├── Action: Create onboarding project
└── Action: Update revenue forecast
AUTOMATION 4: Weekly Pipeline Report
├── Trigger: Every Monday 9am
├── Action: Query all open deals
├── Action: Calculate weighted pipeline
└── Action: Send summary to #sales
Integration Points
Automations connect to external services:
- Slack — Notifications and alerts
- Email — Outreach and follow-ups
- Calendar — Meeting scheduling
- Webhooks — External systems
This is the Execution Pillar.
How the Layers Interact
The power is in the connections:
┌──────────────────────────────────────────────────┐
│ │
│ User asks: "Show me stalled deals" │
│ │ │
│ ▼ │
│ ┌─────────────────────────────────────────┐ │
│ │ 🤖 AGENT (Intelligence) │ │
│ │ - Interprets question │ │
│ │ - Queries memory for deals │ │
│ │ - Analyzes stage durations │ │
│ └─────────────────────────────────────────┘ │
│ │ │
│ ▼ │
│ ┌─────────────────────────────────────────┐ │
│ │ 🧠 MEMORY (Projects) │ │
│ │ - Returns deals with stage > 14 days │ │
│ │ - Includes contact and value info │ │
│ └─────────────────────────────────────────┘ │
│ │ │
│ ▼ │
│ Agent presents: "3 deals stalled: │
│ - Acme ($50k, 21 days in proposal) │
│ - BigCo ($100k, 18 days in negotiation) │
│ - StartupX ($25k, 30 days in discovery) │
│ Suggest follow-up actions?" │
│ │ │
│ ▼ │
│ User: "Yes, create follow-up tasks" │
│ │ │
│ ▼ │
│ ┌─────────────────────────────────────────┐ │
│ │ ⚡ MOTION (Automations) │ │
│ │ - Creates tasks for each stalled deal │ │
│ │ - Sends reminders to deal owners │ │
│ │ - Updates CRM flags │ │
│ └─────────────────────────────────────────┘ │
│ │ │
│ ▼ │
│ Memory updated, user notified │
│ │
└──────────────────────────────────────────────────┘
This is Workspace DNA in action.
Building Better Apps
Understanding anatomy helps you build:
For Better Memory
- Define clear relationships between entities
- Use appropriate field types
- Create views for different perspectives
For Better Intelligence
- Write detailed agent instructions
- Give agents relevant context
- Define capabilities clearly
For Better Motion
- Map out trigger conditions
- Chain actions logically
- Connect to relevant services
Inspect Your Apps
Every Genesis app has this structure. To improve any app:
- Examine Memory — Is the schema right? Missing fields?
- Review Intelligence — Is the agent helpful? Accurate?
- Check Motion — Are automations firing? Missing triggers?
The anatomy is your debugging guide.
Resources
Learn more:
- Projects & Databases — Memory Pillar
- Custom AI Agents — Intelligence Pillar
- Automations & Workflows — Execution Pillar
- Workspace DNA — Full architecture
Genesis Deep Dives:
- The Origin of Living Software — Where it all began
- How Workspace DNA Works — The architecture explained
- Build Your First AI App — 12 beginner examples
- Build Without Permission — The Genesis Manifesto
Genesis Showcase:
- 10 AI Dashboards — Finance, CRM, ops
- 10 AI Client Portals — Deploy instantly
- 10 AI Booking Systems — Clone for business
- 20 AI App Ideas — Inspiration gallery
Explore Taskade AI:
- AI App Builder — Build complete applications
- AI Agent Builder — Create intelligent assistants
- AI Workflow Automation — Automate any process
Build with Genesis:
- Browse All Generator Templates — Apps, dashboards, websites, and more
- Browse Agent Templates — AI agents for every use case
- Explore Community Apps — Clone and customize
Frequently Asked Questions
What is the internal structure of a Taskade Genesis app?
Every Genesis app has a three-layer architecture: Memory (Projects and databases that store structured data), Intelligence (AI Agents that reason, respond, and take actions), and Execution (Automations that trigger workflows based on conditions). These three layers work together as Workspace DNA to create living software that adapts and evolves.
What is Workspace DNA in Taskade?
Workspace DNA is the foundational architecture of every Taskade Genesis app, consisting of three components: Memory (structured databases and project data), Intelligence (AI agents powered by 11+ models from 3 providers), and Execution (automated workflows with triggers, conditions, and actions). This architecture ensures every app is not just stored data but an active, intelligent system.
How do AI agents work inside a Genesis app?
AI agents in a Genesis app are the Intelligence layer. Each agent has a defined personality, knowledge base, and set of capabilities. Agents can read and write to the Memory layer (databases), trigger the Execution layer (automations), and collaborate with other agents. They come with 22+ built-in tools, custom slash commands, and persistent memory across interactions.
Can I customize the architecture of a Genesis app after building it?
Yes. Every layer of a Genesis app is fully customizable. You can modify database schemas (Memory), reconfigure agent personalities and capabilities (Intelligence), and adjust automation triggers and workflows (Execution). The app supports 8 project views (List, Board, Calendar, Table, Mind Map, Gantt, Org Chart, Timeline) and 7-tier access control for team collaboration.