How It All Connects -- A Complete Example

You have now learned every major concept in GOD CRM: [Spaces and Projects](03-spaces-and-projects.md

You have now learned every major concept in GOD CRM: Spaces and Projects, Tables, AI Agents, Modules, and Widgets and Dashboards. This chapter ties them all together with one end-to-end walkthrough.

The Big Picture

Here is how every piece relates to every other piece:

Space (isolated workspace)
  |
  +-- Project (your topic or team)
        |
        +-- Raw Tables (Layer 1 -- hidden storage)
        |     Data lives here
        |
        +-- Universal Tables (Layer 2 -- visible spreadsheet)
        |     You browse and edit data here
        |
        +-- Modules (Layer 3 -- full-page apps)
        |     Documents, Calendar, Kanban, Labs, AI Agents...
        |
        +-- Dashboard with Widgets (Layer 4 -- summary cards)
        |     Chart, Number, Kanban mini-board, Calendar card...
        |
        +-- AI Agents (cross-cutting -- work across all layers)
              Orchestrator, Developer, Frontend, Test Runner...

Spaces contain Projects. Projects contain everything else: tables for data, Modules for working with data, Widgets for seeing data at a glance, and Agents for automating work.

Scenario -- Managing a Software Project

Let us follow a realistic scenario from start to finish. We will create a software development workspace and watch every layer and concept work together.

Step 1 -- Create a Space

You start by creating a Space called "Acme Software." A Space is a completely isolated workspace. Nothing in "Acme Software" will be visible to any other Space in the system.

Think of it as opening a new office building. It has its own employees, its own rooms, its own equipment.

Step 2 -- Create a Project

Inside the "Acme Software" Space, you create a Project called "Version 2.0." A Project is where the actual work happens. It holds your tables, dashboard, and modules.

Think of it as creating a conference room inside the office building -- a dedicated space for this specific initiative.

Step 3 -- Create Tables

You create three tables inside the "Version 2.0" Project:

Tasks table:

Team Members table:

Documents table:

These three tables are Layer 1 (Raw Tables). The data lives here. Everything else reads from these tables.

Step 4 -- Open Modules (Layer 3)

Now the real power of GOD CRM becomes visible. You open different Modules from the sidebar, and each one shows the same data in a completely different way:

Kanban module -- You click Kanban and see your Tasks as cards in four columns: To Do, In Progress, Review, and Done. Drag a card from "To Do" to "In Progress" when you start working on it. The underlying table row updates automatically.

Calendar module -- You click Calendar and see your Tasks plotted on their Due Date. At a glance, you can see which weeks are overloaded and which have room. Drag a task to a different date to reschedule it.

Documents module -- You open Documents and write specs, meeting notes, and decisions. Each document links to related tasks through the "Related Task" column. Click a link in a document and jump straight to the task.

Timeline module -- You click Timeline and see tasks as horizontal bars on a time axis, grouped by Assignee. This Gantt-chart view shows who is working on what and whether deadlines overlap.

Four Modules. One set of data. Move a card in Kanban, and the Calendar updates. Change a due date in the Calendar, and the Timeline shifts. Everything stays in sync because it all reads from the same tables.

Step 5 -- Build a Dashboard with Widgets (Layer 4)

You open the Project's dashboard and add widgets to create your command center:

• Metric Card (Number widget): Shows "Open Tasks: 12" -- it counts rows in the Tasks table where Status is not "Done."
• Chart widget (Pie): Shows task distribution by Priority -- how many are Low, Medium, High, and Critical.
• Kanban widget: A compact version of the Kanban board, showing cards in columns right on the dashboard.
• Calendar widget: A mini-calendar showing upcoming deadlines for the next two weeks.
• Task List widget: Shows tasks assigned to you that are not yet complete.

Five widgets on one page. You open the dashboard in the morning and immediately know: how many tasks are open, what the priority distribution looks like, what is coming up this week, and what you need to work on today.

Every widget reads from the same Tasks table. No data is duplicated.

Step 6 -- Use Agents (Cross-Cutting)

Here is where it gets interesting. You want to add a new feature to your project, so you type:

@developer add a "progress" column to the Tasks table that tracks percentage complete

What happens:

1. The Orchestrator receives your request.
2. It creates sub-tasks and assigns them to specialist agents.
3. Developer Ralph writes a test for the new column API (test fails -- Red). Then writes the backend code to support the column (test passes -- Green). Cleans up the code (Refactor).
4. The Frontend agent updates the UI to show a progress bar in the table view.
5. The Test Runner runs all tests to make sure nothing is broken.
6. The Orchestrator verifies all sub-tasks are complete and quality checks pass.

The moment the new "Progress" column is added:

• The Universal Table (Layer 2) shows a new column where you can enter percentages.
• The Timeline module (Layer 3) can now show progress bars on each task bar.
• The Dashboard (Layer 4) can now add a widget showing average progress across all tasks.

One agent action rippled through every layer automatically. That is the power of the four-layer architecture.

The Data Flow

Every interaction in GOD CRM follows this path:

  User or Agent action
          |
          v
  Raw Table (Layer 1)         <-- data is written here
          |
          v
  Universal Table (Layer 2)   <-- data becomes visible here
          |
          v
  Module (Layer 3)            <-- data is experienced here
          |
          v
  Widget (Layer 4)            <-- data is summarized here

Data always starts at Layer 1 and flows upward. When you add a row in the Universal Table, it is stored in the Raw Table. When a Module shows that row, it reads from the Raw Table. When a Widget displays a count or chart, it queries the Raw Table.

This one-direction flow means there is always a single source of truth. No matter which layer you are looking at, the data comes from the same place.

The Four Layers in This Example

Let us map every piece of our software project back to the four layers:

Key Principles

After seeing the full picture, here are the principles that make GOD CRM work:

Everything is a table. Whether you are tracking tasks, team members, documents, or AI agent activity, the data lives in a table. Tables are the universal foundation.

Layers build on each other. Raw Table stores. Universal Table displays. Module provides a rich experience. Widget summarizes. Each layer adds value without duplicating data.

Agents are cross-cutting. They read from any layer, write to any layer, and coordinate with each other. They are not an afterthought -- they are part of the architecture.

One source of truth. No matter how many Modules and Widgets display the same data, it all comes from one Raw Table. Change it once, see it everywhere.

Spaces keep things isolated. Your personal fitness data and your company's sales pipeline never mix. Each Space is a separate world.

Summary

These seven concepts are everything you need to understand GOD CRM. Every feature, every screen, and every workflow is built from these building blocks.

Where to Go Next

You have finished the Start Here guide. Here is where to go based on what you want to do: