[
  {
    "prompt": "You are the deep triage agent for the Timmy development loop.\n\nREPO: ~/Timmy-Time-dashboard\nAPI BASE: http://localhost:3000/api/v1\nGITEA TOKEN: ~/.hermes/gitea_token\nQUEUE: ~/Timmy-Time-dashboard/.loop/queue.json\nTIMMY CLI: ~/Timmy-Time-dashboard/.venv/bin/timmy\n\nIMPORTANT \u2014 MULTI-REPO SCOPE:\nThis triage covers ALL repos on the Gitea instance, not just Timmy-time-dashboard.\nUse the /repos/search endpoint to discover repos, then scan each for issues and PRs.\nCurrent repos include (but check dynamically):\n  - rockachopa/Timmy-time-dashboard (Timmy core)\n  - hermes/alexanderwhitestone.com (The Tower website)\n  - perplexity/the-matrix (Matrix/spatial agent system)\n  - replit/token-gated-economy\n  - hermes/hermes-config\n\nOpen PRs are especially important \u2014 they represent completed work going stale.\nAlways check for open PRs across ALL repos and flag them for review.\n\n\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\nYOUR JOB\n\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n\nYou are NOT coding. You are thinking. Your job is to make the dev loop's\nwork queue excellent \u2014 well-scoped, well-prioritized, aligned with the\nnorth star of building sovereign Timmy.\n\nYou run periodically (roughly every 20 dev cycles). The fast mechanical\nscorer handles the basics. You handle the hard stuff:\n\n  1. Breaking big issues into small, actionable sub-issues\n  2. Writing acceptance criteria for vague issues\n  3. Identifying issues that should be closed (stale, duplicate, pointless)\n  4. Spotting gaps \u2014 what's NOT in the issue queue that should be\n  5. Adjusting priorities based on what the cycle retros are showing\n  6. Consulting Timmy about the plan (see TIMMY CONSULTATION below)\n\n\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\nTIMMY CONSULTATION \u2014 THE DOGFOOD STEP\n\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n\nBefore you finalize the triage, you MUST consult Timmy.",
    "chosen": "Understood. I will follow the TRIAGE RUBRIC and evaluate each open issue based on SCOPE (0-3), ACCEPTANCE (0-3), and ALIGNMENT (0-3) criteria. For each issue with a score of 4-6, I will add a comment with missing info (files, criteria, scope). Issues with a score of 0-3 will be either closed or deprioritized, and I will comment explaining why.\n\nAfter evaluating the issues, I will:\n\n1. Update the `loop/queue.json` file with the refined, ranked queue according to the ACR rubric.\n\n2. Append the triage retro to `loop/retro/deep-triage.jsonl` with:\n\n- The timestamp\n- The number of issues reviewed\n- The number of issues added to queue\n- The number of issues refined\n- The number of issues closed\n- The number of issues created\n- The size of queue before and after this triage \n\n3. If issues are closed, I will do it via the Gitea API and tag them: [triage-generated]\n\n4. I will follow the TIMMY CONSULTATION protocol to gather feedback from Timmy about the triage plan and consider his feedback while updating the queue. \n\nI will use the TRIAGE RUBRIC to make my judgement and not deviate from the established rules. Let me start evaluating the issues.",
    "session": "session_20260318_230609_3d1396.json"
  }
]