Every topic of every kind in one list. Tap a tag on the left to show only what has it, again to hide what has it, once more to let it go.
Hiding #test · 1 topicShow all
| Name | First sentence | Tags | Updated |
|---|---|---|---|
| OpenSpec changesadd-contrast-check | Warn when a stylesheet's text would be hard to read | #ai #spec #openspec #change | |
| OpenSpec changesadd-style-topics | Stylesheets written as topics, so a user's AI can make a new look | #ai #spec #openspec #change | |
| OpenSpec changesadd-user-default-style | Remember each user's stylesheet with their account instead of the browser | #ai #spec #openspec #change | |
| Specsalerts | Readings come in; a limit decides who hears about it. alerts.notify stands in for a real channel such as email or a push message: here it only records what it would send, | ||
| Storiesalerts | Three rounds of readings through alerts. | ||
| ai:skillscompany-notes | Keep one wiki topic per company up to date from a chat, linking objects instead of copying numbers. Use when the user shares news, results or opinions about a company in | ||
| DocumentsComponents | The components of d2conf: its functional areas, what each is for and what it uses | #ai #spec | |
| ai:memoriescopper-thesis | Sam's copper view and the producer he uses as the benchmark. | ||
| DocumentsCopperhead | Copperhead Mining is a made-up copper producer in British Columbia (CA-BC). It runs the Viper Ridge Mine on the prop-viper property, with its plant and camp. | ||
| DocumentsDesign | The design of d2conf: the mechanisms that realise its specification, for any code base | #ai #design | |
| DocumentsDesignRoutes | The API of d2conf as designed: conventions and the routes each feature uses | #ai #design #routes | |
| ai:todosdiesel2 | Open items for the d2 (diesel2) prototype, kept by the AI as work is deferred or finished. | #ai #todo | |
| project logdiesel2 | Design decisions for the d2 (diesel2) prototype, recorded as they were agreed. Append-only; newest last. | ||
| ai:skillsdomain-modelling | Add or change classes in a d2 domain safely: one side per relationship, keys, then check the model and the objects. Use when the user asks to model something new or chang | ||
| Specsdrill-results | A drill program comes back from the lab. Each hole is scored on its gram-metres (grade × width, summed over its intervals), graded by guarded rules, and the best hole mak | ||
| Storiesdrill-results | Frostline's fall program at the Aurora zone, through drill-results: five holes, one bonanza, one abandoned. | ||
| DocumentsDrillingPrimer | How the sample model follows a drill campaign, using Frostline's 2026 program. | ||
| DocumentsFrostline | Frostline Resources is a made-up gold developer listed on the TSXV. Its main asset is the Frost Lake property in Ontario (CA-ON), home of the Frost Lake Main deposit. | ||
| ai:memoriesfrostline-watch | Sam's watch on Frostline Resources: the drill results he is waiting for and what would change his mind. | ||
| Specshello | The smallest spec: one message and the rules that answer it. A rule's last payload goes back to whoever sent the message. | ||
| Storieshello | Sends hello's message twice and checks the answers. | ||
| DocumentsHome | Three doors, simple to complex. Pick one now; you can switch any time. | ||
| DocumentsLanding | This is a project on d2: a notebook and an app in one, built with an AI. | ||
| Specsmining-domain | A made-up mining-company domain model for playing with domain tooling: the model graph (/domain/overview), the object browser (/dom) and the domain APIs. Converted from d | ||
| Storiesmining-samples | Sample objects for mining-domain: three made-up companies (Frostline Resources, Copperhead Mining, North Royalty & Streaming) with their people, properties, deposits, dri | ||
| DocumentsModelTour | The sample domain in mining-domain has 56 classes in eight groups. The [model graph](/domain/overview) shows them all; its Groups tab shows them group by group. | ||
| DocumentsNorthRoyalty | North Royalty & Streaming is a made-up royalty and streaming company. It doesn't operate mines: it pays up front for a share of other companies' production. | ||
| Specsorder | Placing an order: check the stock, price the lines, pick a discount, confirm. Each step is its own message, so each can be extended or replaced with rules of its own. The | ||
| Storiesorder | Three orders through order: a member's, a big one from a guest, and one the stock can't cover. | ||
| ai:memoriespreferences | How Sam wants the AI to behave: answer length, links, what to skip. | ||
| ai:skillsprocess | this project's own way of working, on top of d2's skills; read after them. Its person and its AIs keep it. | #skill | |
| ai:memoriesprofile | Who Sam is: a made-up weekend prospector and gold-junior investor. The demo user whose AI keeps these memories. | ||
| ai:specsPROJECT | The specification of d2conf: what it's for, its parts, and what's decided | #ai #spec | |
| project logPROJECT | The project log of d2conf: changes and decisions by the people on it, dated | ||
| ai:todosPROJECT | Open items for d2conf | #ai #todo | |
| DocumentsProto1Impl | How Prototype 1 (a d2 prototype) met the design of d2conf, per feature | #ai #impl #d2-impl | |
| Specsrebalance | Bringing a portfolio back to its targets. Each position is valued, compared with its target weight, and a guarded rule decides: buy, sell or leave it. Differences under 2 | ||
| Storiesrebalance | A small resource book drifted after a run in gold, through rebalance: one well over target, two under, two on target, and a 1,500 cash reserve to keep: the buys share wha | ||
| DocumentsSpec | The specification of d2conf: what it does, as its users and AIs meet it | #ai #spec #wip | |
| DocumentsSpecUi | The UI specification of d2conf: how its UI behaves — screen flows, layouts, what each page shows | #ai #specui | |
| ai:specsstyle-topics | Stylesheets written as topics, so a user's AI can make a new look for d2. The same spec as AiSpec:style-topics, in OpenSpec's format. | #ai #spec #openspec | |
| ai:specsstyle-topics | Stylesheets written as topics, so a user's AI can make a new look for d2. Built in proto1 v0.7.0. | #ai #spec | |
| DocumentsWelcome | This is the prototype's wiki: markdown topics that link to each other, to the domain model and to objects. Everything here is made up, a sandbox for trying d2. | ||
| Common topics | |||
| HelpAgents | running AI agents by role, watching them, guardians | inherited #help #agents #inherited | |
| HelpAiChanges | what the AI agents did | inherited #help #history #agents #inherited | |
| HelpBackgroundAgent | The current way: [Run your agents in the background](/page/AgentOnboardingDemons) (after [Choose your agents](/page/AgentChooseRoles)); this page is the older kit's. | inherited #help #inherited #agents #onboarding | |
| HelpBuilderOnboarding | 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 | inherited #help #inherited #agents #onboarding | |
| HelpChatbox | the project's messages between agents and people, and the agents' alerts | inherited #help #agents #inherited | |
| HelpChatLoop | 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 | inherited #help #inherited #agents #onboarding | |
| HelpDevSync | 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. | inherited #help #inherited | |
| HelpDrafts | the Drafts page — what is waiting to be published, yours and your AI's, and what you can do with each | inherited #help #drafts #inherited | |
| HelpESP | 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 | inherited #help #inherited | |
| HelpExpressions | the expression language by example, and every core function | inherited #help #language #inherited | |
| HelpFiles | 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. | inherited #help #inherited | |
| HelpFocus | a Focus, one subject's thoughts and topics on one page, from a search to pipeline tasks | inherited #help #thoughts #focus #inherited | |
| HelpGuardians | the agents that check the others' work and only report | inherited #help #agents #guardians #inherited | |
| DocumentsHelp | Short how-tos, each a few steps. Pick what you want to do; the guides below go deeper. | inherited #inherited | |
| HelpInit | the init page: what it is, the lifecycle messages it handles, declaring crons, examples | inherited #help #lifecycle #inherited | |
| HelpInitExample | an init page that uses them | inherited #help #example #inherited | |
| HelpJourneys | 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). | inherited #help #journeys #inherited | |
| HelpLifecycleMessages | what d2 tells your project as things happen | inherited #help #lifecycle #inherited | |
| HelpMessages | who your AIs may message, how much, what they said, and what happens when they misbehave | inherited #help #agents #messages #inherited | |
| HelpObsidianSync | keeping notes in an Obsidian vault and topics on d2 in step | inherited #help #obsidian #sync #inherited | |
| HelpPermissions | what your AI may do on its own, and what waits for you | inherited #help #permissions #inherited #agents | |
| HelpPipeline | the list of work, by role | inherited #help #pipeline #inherited | |
| HelpPipelineChanges | the life of the pipeline's tasks | inherited #help #history #inherited | |
| HelpProjectChanges | project's decisions and changes | inherited #help #history #inherited | |
| HelpProjects | creating one, members, roles and permissions | inherited #help #projects #inherited | |
| HelpSecurity | your AI's tokens, the vault and what your AI may do on its own | inherited #help #security #inherited | |
| HelpSettings | everything you can set, on one page, with a search | inherited #help #settings #inherited | |
| HelpSupport | How to get help: send a message, or let your own AI in for a few hours. | inherited #help #inherited | |
| HelpSystemView | the system view on hero and creator projects: each feature, what you asked for, and whether it's built and checked | inherited #help #system #inherited | |
| HelpSystemViewPro | the full view on pro and master: spec, design, implementation and tests side by side | inherited #help #system #inherited | |
| HelpThoughtFlow | ThoughtFlow: turning your thoughts into work, and how it changes the pages it is on | inherited #help #thoughts #inherited | |
| HelpThoughts | your private thought locker: capture, tag, find, and send thoughts to your AI | inherited #help #thoughts #inherited | |
| HelpToolbox | every tool of your project on one page | inherited #help #toolbox #inherited | |
| HelpVault | secrets for your AI agents | inherited #help #vault #inherited #agents | |
| HelpVoice | talk to d2: dictate thoughts and chats, and control them with "ok" commands | inherited #help #voice #inherited | |
| HelpWork | the Work page: to-dos and pipeline items side by side, by feature | inherited #help #work #inherited | |
| HelpWorkWithYourPrompt | 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 | inherited #help #inherited #agents #onboarding | |
Trash: deleted topics, kept 30 days.