← Back to Kontasks
Domains: The Coverage Dimension
Output
📊 Domains: The Coverage Dimension
Topics track what kind of work (planning, design, testing...). Domains track what area of the app the work touches. Together they form a coverage matrix ensuring nothing gets neglected.
Two Dimensions of Work
TOPICS (Process Phase)
Requirements → Planning → Design → ... → Docs
↓ ↓ ↓ ↓
D Auth/Identity [ ] [ ] [✓] [ ]
O Data/Storage [ ] [✓] [✓] [ ]
M API/Backend [✓] [ ] [ ] [ ]
A UI/Frontend [ ] [ ] [✓] [✓]
I DevOps/Infra [ ] [ ] [ ] [ ]
N Integration [ ] [ ] [ ] [ ]
S Security [ ] [ ] [ ] [ ]
Proposed Domains (Functional Areas)
| 🔐 | Auth | Authentication, authorization, identity, permissions, sessions |
| 💾 | Data | Storage, database, models, queries, migrations, caching |
| 🔌 | API | Backend endpoints, services, business logic, MCP tools |
| 🖼️ | UI | Frontend, components, layouts, styling, user experience |
| ⚙️ | Ops | DevOps, deployment, monitoring, logs, infrastructure |
| 🔗 | Integration | External APIs, webhooks, third-party services, sync |
| 🛡️ | Security | Vulnerabilities, hardening, secrets, compliance, audit |
How Domains Would Work
- Kontask tagging: Each kontask can touch 1+ domains
- Coverage gaps: Dashboard shows which domains haven't seen recent work
- Balance check: "You've done 15 UI tasks but 0 Security tasks this week"
- Ship readiness: Ensure all domains have been addressed before release
Topics vs Domains
| Aspect | Topics | Domains |
|---|---|---|
| Question | What kind of work? | What part of the app? |
| Examples | Design, Testing, Bugfix | Auth, Data, UI |
| Count | 12 (lifecycle phases) | 7 (functional areas) |
| Purpose | Process maturity | Coverage breadth |
Questions for Discussion
- Are these 7 domains the right functional areas?
- Should domains be a separate entity type (gvDomain) or just tags?
- How granular? e.g., split "Data" into "Schema" vs "Queries"?
- Should some be platform-specific? (e.g., "WebSocket" for greatVibe)
Quick Actions
Original Request
No layout configured
Details
Type
General
Status
Completed
Scope
vibetools
Tags
designschemadomains
Created
10 Jan 2026, 8:04 pm
Updated
10 Jan 2026, 8:04 pm
Created By
claude
Raw Data
{
"id": "8388623a-801d-4081-ac34-bc070246f9b9",
"type": "general",
"status": "completed",
"title": "Domains: The Coverage Dimension",
"context": {
"output": "<div style=\"background:#1e1e1e;color:#e0e0e0;padding:20px;border-radius:8px;font-family:'Consolas','Monaco',monospace;\">\n<h2 style=\"font-family:sans-serif;color:#fff;margin:0 0 16px 0;\">📊 Domains: The Coverage Dimension</h2>\n\n<p style=\"color:#abb2bf;line-height:1.6;margin-bottom:20px;\">Topics track <strong>what kind of work</strong> (planning, design, testing...). Domains track <strong>what area of the app</strong> the work touches. Together they form a coverage matrix ensuring nothing gets neglected.</p>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin-bottom:20px;\">\n<h3 style=\"color:#61afef;margin:0 0 12px 0;\">Two Dimensions of Work</h3>\n<pre style=\"color:#e0e0e0;margin:0;line-height:1.8;\">\n <span style=\"color:#c678dd;\">TOPICS (Process Phase)</span>\n Requirements → Planning → Design → ... → Docs\n ↓ ↓ ↓ ↓\n<span style=\"color:#98c379;\">D</span> Auth/Identity [ ] [ ] [✓] [ ]\n<span style=\"color:#98c379;\">O</span> Data/Storage [ ] [✓] [✓] [ ]\n<span style=\"color:#98c379;\">M</span> API/Backend [✓] [ ] [ ] [ ]\n<span style=\"color:#98c379;\">A</span> UI/Frontend [ ] [ ] [✓] [✓]\n<span style=\"color:#98c379;\">I</span> DevOps/Infra [ ] [ ] [ ] [ ]\n<span style=\"color:#98c379;\">N</span> Integration [ ] [ ] [ ] [ ]\n<span style=\"color:#98c379;\">S</span> Security [ ] [ ] [ ] [ ]\n</pre>\n</div>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin-bottom:20px;\">\n<h3 style=\"color:#e5c07b;margin:0 0 12px 0;\">Proposed Domains (Functional Areas)</h3>\n<table style=\"width:100%;border-collapse:collapse;color:#e0e0e0;\">\n<tr style=\"border-bottom:1px solid #3e4451;\">\n <td style=\"padding:8px;\">🔐</td>\n <td style=\"padding:8px;color:#f43f5e;font-weight:bold;\">Auth</td>\n <td style=\"padding:8px;color:#7f848e;\">Authentication, authorization, identity, permissions, sessions</td>\n</tr>\n<tr style=\"border-bottom:1px solid #3e4451;\">\n <td style=\"padding:8px;\">💾</td>\n <td style=\"padding:8px;color:#3b82f6;font-weight:bold;\">Data</td>\n <td style=\"padding:8px;color:#7f848e;\">Storage, database, models, queries, migrations, caching</td>\n</tr>\n<tr style=\"border-bottom:1px solid #3e4451;\">\n <td style=\"padding:8px;\">🔌</td>\n <td style=\"padding:8px;color:#22c55e;font-weight:bold;\">API</td>\n <td style=\"padding:8px;color:#7f848e;\">Backend endpoints, services, business logic, MCP tools</td>\n</tr>\n<tr style=\"border-bottom:1px solid #3e4451;\">\n <td style=\"padding:8px;\">🖼️</td>\n <td style=\"padding:8px;color:#c678dd;font-weight:bold;\">UI</td>\n <td style=\"padding:8px;color:#7f848e;\">Frontend, components, layouts, styling, user experience</td>\n</tr>\n<tr style=\"border-bottom:1px solid #3e4451;\">\n <td style=\"padding:8px;\">⚙️</td>\n <td style=\"padding:8px;color:#f97316;font-weight:bold;\">Ops</td>\n <td style=\"padding:8px;color:#7f848e;\">DevOps, deployment, monitoring, logs, infrastructure</td>\n</tr>\n<tr style=\"border-bottom:1px solid #3e4451;\">\n <td style=\"padding:8px;\">🔗</td>\n <td style=\"padding:8px;color:#14b8a6;font-weight:bold;\">Integration</td>\n <td style=\"padding:8px;color:#7f848e;\">External APIs, webhooks, third-party services, sync</td>\n</tr>\n<tr>\n <td style=\"padding:8px;\">🛡️</td>\n <td style=\"padding:8px;color:#eab308;font-weight:bold;\">Security</td>\n <td style=\"padding:8px;color:#7f848e;\">Vulnerabilities, hardening, secrets, compliance, audit</td>\n</tr>\n</table>\n</div>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin-bottom:20px;\">\n<h3 style=\"color:#56b6c2;margin:0 0 12px 0;\">How Domains Would Work</h3>\n<ul style=\"color:#abb2bf;line-height:1.8;margin:0;padding-left:20px;\">\n<li><strong>Kontask tagging:</strong> Each kontask can touch 1+ domains</li>\n<li><strong>Coverage gaps:</strong> Dashboard shows which domains haven't seen recent work</li>\n<li><strong>Balance check:</strong> \"You've done 15 UI tasks but 0 Security tasks this week\"</li>\n<li><strong>Ship readiness:</strong> Ensure all domains have been addressed before release</li>\n</ul>\n</div>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin-bottom:20px;\">\n<h3 style=\"color:#98c379;margin:0 0 12px 0;\">Topics vs Domains</h3>\n<table style=\"width:100%;border-collapse:collapse;color:#e0e0e0;\">\n<tr style=\"border-bottom:1px solid #3e4451;background:#3e4451;\">\n <th style=\"padding:8px;text-align:left;\">Aspect</th>\n <th style=\"padding:8px;text-align:left;\">Topics</th>\n <th style=\"padding:8px;text-align:left;\">Domains</th>\n</tr>\n<tr style=\"border-bottom:1px solid #3e4451;\">\n <td style=\"padding:8px;\">Question</td>\n <td style=\"padding:8px;color:#c678dd;\">What kind of work?</td>\n <td style=\"padding:8px;color:#98c379;\">What part of the app?</td>\n</tr>\n<tr style=\"border-bottom:1px solid #3e4451;\">\n <td style=\"padding:8px;\">Examples</td>\n <td style=\"padding:8px;\">Design, Testing, Bugfix</td>\n <td style=\"padding:8px;\">Auth, Data, UI</td>\n</tr>\n<tr style=\"border-bottom:1px solid #3e4451;\">\n <td style=\"padding:8px;\">Count</td>\n <td style=\"padding:8px;\">12 (lifecycle phases)</td>\n <td style=\"padding:8px;\">7 (functional areas)</td>\n</tr>\n<tr>\n <td style=\"padding:8px;\">Purpose</td>\n <td style=\"padding:8px;\">Process maturity</td>\n <td style=\"padding:8px;\">Coverage breadth</td>\n</tr>\n</table>\n</div>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;\">\n<h3 style=\"color:#f43f5e;margin:0 0 12px 0;\">Questions for Discussion</h3>\n<ol style=\"color:#abb2bf;line-height:1.8;margin:0;padding-left:20px;\">\n<li>Are these 7 domains the right functional areas?</li>\n<li>Should domains be a separate entity type (gvDomain) or just tags?</li>\n<li>How granular? e.g., split \"Data\" into \"Schema\" vs \"Queries\"?</li>\n<li>Should some be platform-specific? (e.g., \"WebSocket\" for greatVibe)</li>\n</ol>\n</div>\n</div>",
"choices": [
{
"label": "Use these 7 domains",
"value": "Implement domains with Auth, Data, API, UI, Ops, Integration, Security",
"primary": true
},
{
"label": "Fewer domains",
"value": "Simplify to fewer core domains - suggest what to consolidate"
},
{
"label": "More domains",
"value": "Add more specific domains - suggest what's missing"
},
{
"label": "Just use tags",
"value": "Don't create a formal domain system, just use freeform tags on kontasks"
}
]
},
"createdBy": "claude",
"createdAt": "2026-01-10T10:04:35.755Z",
"updatedAt": "2026-01-10T10:04:36.020Z",
"scope": "vibetools",
"tags": [
"design",
"schema",
"domains"
]
}