All

This is d2pro, the pro demo: a small online shop that sells coffee gear, built on d2. Everything here is made up and resets on every update, so try anything.

The specification of d2pro: what it's for, its parts, and what's decided

The components of d2pro: its functional areas, what each is for and what it uses

The design of d2pro: the mechanisms that realise its specification, for any code base

The API of d2pro as designed: conventions and the routes each feature uses

The pro demo: a small online shop that sells coffee gear, with its model, sample data and flows. It's a wiki topic, Home, like every project's start page: change it any t

This is a project on d2: a notebook and an app in one, built with an AI.

The project log of d2pro: changes and decisions by the people on it, dated

How Prototype 1 (a d2 prototype) met the design of d2pro, per feature

this project's own way of working, on top of d2's skills; read after them. Its person and its AIs keep it.

A small online shop, Grindstone Coffee Gear, as a domain model: what it sells, who buys, their orders, and how orders get to them. Its sample data is in shop-samples; wha

Two flows about carts. A new cart tells the shop who's shopping. Abandoned carts runs once a day (a cron, declared in Init): any cart still open after 48 hours is marked

Every message the shop sends goes through this one rule. Here it keeps the message in the shop's outbox (a Message object, see shop), so the demo shows what would go out

Order placed. When an order is created, the shop issues its invoice, reserves the stock for each line (from the first warehouse that has enough), checks whether that left

Shipped. When a shipment's status becomes shipped, its order is marked shipped and the customer gets the tracking number.

Low stock. When a stock level drops below its reorder point, whoever runs the shop hears about it, with the supplier to call and how long they take to deliver. It runs wh

The black-box tests of d2pro: at least one per spec line, each run as a person

The UI specification of d2pro: how its UI behaves — screen flows, layouts, what each page shows

Each shop flow, run by hand on the sample data (in the [Fiddle](/fiddle?tab=stories&topic=Story:shop-flows), nothing is kept). The triggers in Init start the same flows w

Sample objects for shop: Grindstone Coffee Gear, a made-up shop with 12 products, 6 customers, carts, orders in each status, two warehouses and a return. Each $object Cla

Open items for d2pro

Short how-tos, each a few steps. Pick what you want to do; the guides below go deeper.

running AI agents by role, watching them, guardians

what the AI agents did

The current way: [Run your agents in the background](/page/AgentOnboardingDemons) (after [Choose your agents](/page/AgentChooseRoles)); this page is the older kit's.

a builder's onboarding on a project they joined (not the owner's setup): pick a door, which connects your AI (razie, designer-106 chat, 2026-10-12); where a builder with

the project's messages between agents and people, and the agents' alerts

What's a chat loop? Today you talk to your AI in its own app, and it works on d2 when you ask. In a chat loop your AI stays on d2: it keeps listening to the chat here, so

Dev-sync is the round arrows button at the top. Turn it on while you, or your AIs, are changing things, and the pages you have open keep themselves current.

the Drafts page — what is waiting to be published, yours and your AI's, and what you can do with each

When you talk with your AI about a page ("open the sync section", "show me that item"), ESP (also called Mind Meld) lets it take you there. You don't have to hunt for the

the expression language by example, and every core function

Your project's Files keep images, PDFs, mockups and other files your pages and documents use. Open them from the Toolbox (Files) or at /cdn on your project.

a Focus, one subject's thoughts and topics on one page, from a search to pipeline tasks

the agents that check the others' work and only report

the init page: what it is, the lifecycle messages it handles, declaring crons, examples

an init page that uses them

A journey is a person's path through an app's pages to a goal: from where they start to where they are done. Open them at [/page/Journey](/page/Journey).

what d2 tells your project as things happen

who your AIs may message, how much, what they said, and what happens when they misbehave

keeping notes in an Obsidian vault and topics on d2 in step

what your AI may do on its own, and what waits for you

the list of work, by role

the life of the pipeline's tasks

project's decisions and changes

creating one, members, roles and permissions

your AI's tokens, the vault and what your AI may do on its own

everything you can set, on one page, with a search

How to get help: send a message, or let your own AI in for a few hours.

the system view on hero and creator projects: each feature, what you asked for, and whether it's built and checked

the full view on pro and master: spec, design, implementation and tests side by side

ThoughtFlow: turning your thoughts into work, and how it changes the pages it is on

your private thought locker: capture, tag, find, and send thoughts to your AI

every tool of your project on one page

secrets for your AI agents

talk to d2: dictate thoughts and chats, and control them with "ok" commands

the Work page: to-dos and pipeline items side by side, by feature

The simple way: you talk to your AI in its own app, it builds here on d2. Nothing to set up. The only question is how you see both: your AI's chat, and the page it's chan