Investigation Kontask Design Discussion

Details

Raw Data

{
  "id": "6dcea038-777f-4829-90bd-c63dc1c54843",
  "type": "general",
  "status": "completed",
  "title": "Investigation Kontask Design Discussion",
  "description": "Exploring persistent investigation tracking beyond standard kontasks",
  "context": {
    "output": "<div style=\"background:#1e1e1e;color:#e0e0e0;padding:20px;border-radius:8px;font-family:system-ui,-apple-system,sans-serif;\">\n<h2 style=\"color:#fff;margin:0 0 16px 0;\">🔍 Investigation Kontask Design</h2>\n\n<p style=\"color:#9ca3af;margin-bottom:20px;\">You've identified a real gap. Let me break down the problem and explore solutions.</p>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin-bottom:16px;\">\n<h3 style=\"color:#f59e0b;margin:0 0 12px 0;\">The Problem</h3>\n<p style=\"margin:0 0 12px 0;\">Current kontasks are <strong>turn-bounded</strong>:</p>\n<ul style=\"margin:0;padding-left:20px;line-height:1.8;\">\n<li>Created at end of turn with findings</li>\n<li>No place to accumulate evidence <em>during</em> investigation</li>\n<li>If Claude crashes mid-investigation, context is lost</li>\n<li>Multi-turn debugging has no persistent \"case file\"</li>\n</ul>\n</div>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin-bottom:16px;\">\n<h3 style=\"color:#22c55e;margin:0 0 12px 0;\">Option A: Investigation Kontask Type</h3>\n<p style=\"margin:0 0 12px 0;\">A new <code style=\"background:#3d3d3d;padding:2px 6px;border-radius:4px;\">type: \"investigation\"</code> with special behavior:</p>\n<ul style=\"margin:0;padding-left:20px;line-height:1.8;\">\n<li><strong>Created at start</strong> of investigation (not end)</li>\n<li><strong>Append-only updates</strong> - each turn adds findings to existing card</li>\n<li><strong>Structured sections</strong>: Symptoms → Hypothesis → Evidence → Resolution</li>\n<li><strong>Crash-safe</strong> - evidence persisted after each append</li>\n<li><strong>Status progression</strong>: investigating → blocked → resolved/unresolved</li>\n</ul>\n<pre style=\"background:#1a1a1a;padding:12px;border-radius:4px;margin:12px 0;overflow-x:auto;font-size:0.9rem;\">\n<span style=\"color:#7f848e;\">// Investigation card structure</span>\n{\n  <span style=\"color:#e5c07b;\">\"type\"</span>: <span style=\"color:#98c379;\">\"investigation\"</span>,\n  <span style=\"color:#e5c07b;\">\"title\"</span>: <span style=\"color:#98c379;\">\"Kongate crash on malformed XML\"</span>,\n  <span style=\"color:#e5c07b;\">\"status\"</span>: <span style=\"color:#98c379;\">\"investigating\"</span>,\n  <span style=\"color:#e5c07b;\">\"context\"</span>: {\n    <span style=\"color:#e5c07b;\">\"symptoms\"</span>: <span style=\"color:#98c379;\">\"Service dies when...\"</span>,\n    <span style=\"color:#e5c07b;\">\"hypothesis\"</span>: [<span style=\"color:#98c379;\">\"H1: Null pointer\"</span>, <span style=\"color:#98c379;\">\"H2: Memory\"</span>],\n    <span style=\"color:#e5c07b;\">\"evidence\"</span>: [  <span style=\"color:#7f848e;\">// Appended each turn</span>\n      { <span style=\"color:#e5c07b;\">\"turn\"</span>: 1, <span style=\"color:#e5c07b;\">\"finding\"</span>: <span style=\"color:#98c379;\">\"Stack trace shows...\"</span> },\n      { <span style=\"color:#e5c07b;\">\"turn\"</span>: 2, <span style=\"color:#e5c07b;\">\"finding\"</span>: <span style=\"color:#98c379;\">\"Reproduced with...\"</span> }\n    ],\n    <span style=\"color:#e5c07b;\">\"resolution\"</span>: <span style=\"color:#c678dd;\">null</span>\n  }\n}\n</pre>\n</div>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin-bottom:16px;\">\n<h3 style=\"color:#3b82f6;margin:0 0 12px 0;\">Option B: Support Issues (Higher-Level Entity)</h3>\n<p style=\"margin:0 0 12px 0;\">A new top-level concept that <em>contains</em> kontasks:</p>\n<ul style=\"margin:0;padding-left:20px;line-height:1.8;\">\n<li><strong>Support Issue</strong> = umbrella for related work</li>\n<li>Links multiple kontasks, turns, commits together</li>\n<li>Has its own lifecycle: open → investigating → resolved → closed</li>\n<li>Shows in sidebar/nav as distinct from kontasks</li>\n<li>Could also cover \"working jobs\" (planned multi-turn work)</li>\n</ul>\n<pre style=\"background:#1a1a1a;padding:12px;border-radius:4px;margin:12px 0;overflow-x:auto;font-size:0.9rem;\">\n<span style=\"color:#7f848e;\">// Support Issue structure</span>\n{\n  <span style=\"color:#e5c07b;\">\"id\"</span>: <span style=\"color:#98c379;\">\"issue-abc123\"</span>,\n  <span style=\"color:#e5c07b;\">\"type\"</span>: <span style=\"color:#98c379;\">\"support\"</span>,  <span style=\"color:#7f848e;\">// or \"job\", \"epic\"</span>\n  <span style=\"color:#e5c07b;\">\"title\"</span>: <span style=\"color:#98c379;\">\"Kongate crash investigation\"</span>,\n  <span style=\"color:#e5c07b;\">\"status\"</span>: <span style=\"color:#98c379;\">\"investigating\"</span>,\n  <span style=\"color:#e5c07b;\">\"linkedKontasks\"</span>: [<span style=\"color:#98c379;\">\"kt-1\"</span>, <span style=\"color:#98c379;\">\"kt-2\"</span>],\n  <span style=\"color:#e5c07b;\">\"linkedCommits\"</span>: [<span style=\"color:#98c379;\">\"abc123\"</span>],\n  <span style=\"color:#e5c07b;\">\"timeline\"</span>: [...]  <span style=\"color:#7f848e;\">// Auto-populated activity log</span>\n}\n</pre>\n</div>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin-bottom:16px;\">\n<h3 style=\"color:#8b5cf6;margin:0 0 12px 0;\">Option C: Hybrid - Investigation Mode</h3>\n<p style=\"margin:0 0 12px 0;\">Simpler: just add <code style=\"background:#3d3d3d;padding:2px 6px;border-radius:4px;\">mode: \"investigation\"</code> to any kontask:</p>\n<ul style=\"margin:0;padding-left:20px;line-height:1.8;\">\n<li>Enables append-only <code style=\"background:#3d3d3d;padding:2px 6px;border-radius:4px;\">context.findings[]</code> array</li>\n<li>Shows different UI (timeline view instead of static card)</li>\n<li>Auto-captures: timestamps, related files, commands run</li>\n<li>Less architectural change, faster to implement</li>\n</ul>\n</div>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin-bottom:16px;\">\n<h3 style=\"color:#ef4444;margin:0 0 12px 0;\">Key Design Questions</h3>\n<ol style=\"margin:0;padding-left:20px;line-height:2;\">\n<li><strong>Scope:</strong> Just investigations? Or also \"working jobs\" / epics?</li>\n<li><strong>Auto-capture:</strong> Should Claude auto-append findings, or explicit calls?</li>\n<li><strong>Crash recovery:</strong> Save after every finding, or batched?</li>\n<li><strong>UI placement:</strong> Separate nav section? Or filter on kontasks list?</li>\n<li><strong>Retention:</strong> How long to keep investigation history?</li>\n</ol>\n</div>\n\n<div style=\"background:#1a3a2e;border:1px solid #22c55e;padding:16px;border-radius:6px;margin-bottom:16px;\">\n<h3 style=\"color:#22c55e;margin:0 0 12px 0;\">💡 My Recommendation</h3>\n<p style=\"margin:0;line-height:1.8;\">Start with <strong>Option C (Investigation Mode)</strong> as a quick win - it's additive to existing kontask infrastructure. Then evolve toward <strong>Option B (Support Issues)</strong> if we find we need the higher-level grouping.</p>\n<p style=\"margin:12px 0 0 0;color:#9ca3af;\">The key insight is: <em>investigations need append-only persistence that survives crashes</em>. That's the minimum viable change.</p>\n</div>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;\">\n<h4 style=\"margin:0 0 8px 0;color:#fff;\">What's Your Take?</h4>\n<p style=\"color:#9ca3af;margin:0;\">Which direction resonates? Any other scenarios I should consider?</p>\n</div>\n</div>",
    "requestedAt": "2026-01-07T00:00:00.000Z",
    "requestId": "85ff6a57-87f8-4a52-9d04-69db9cd701b1",
    "choices": [
      {
        "label": "Option A: Investigation type",
        "value": "Let's explore Option A - a dedicated investigation kontask type with structured sections (Symptoms/Hypothesis/Evidence/Resolution). What would the full schema and UI look like?",
        "primary": false
      },
      {
        "label": "Option B: Support Issues",
        "value": "Let's explore Option B - Support Issues as a higher-level entity that groups related kontasks and commits. Design the full architecture.",
        "primary": false
      },
      {
        "label": "Option C: Investigation Mode",
        "value": "Let's start with Option C - add investigation mode to existing kontasks with append-only findings. Quick implementation plan?",
        "primary": true
      },
      {
        "label": "Different approach",
        "value": "I have a different idea for how to handle investigations and persistent context..."
      }
    ],
    "turnTiming": {
      "totalMs": 54481,
      "ttfeMs": 3797,
      "thinkingMs": 50683,
      "toolExecutionMs": 0,
      "toolCallCount": 0,
      "thinkingPct": 93,
      "toolsPct": 0,
      "ttfePct": 7
    }
  },
  "createdBy": "claude",
  "createdAt": "2026-01-07T09:22:17.155Z",
  "updatedAt": "2026-01-07T09:22:23.725Z",
  "requestId": "85ff6a57-87f8-4a52-9d04-69db9cd701b1",
  "scope": "vibetools",
  "tags": [
    "kontasks",
    "ui",
    "architecture"
  ],
  "targetUser": "claude"
}