You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
id: investigate: boards — a modern phpBB on ID identity: no registration, copyable themes #2052
LIST 15a. Bring back phpBB3, modernised: everything needed to run boards where many people can create their own board, nobody registers (your Iroh ID is your identity), every board sets its own theme, and themes can be copied and shared. Posts carry pictures, audio, video. Investigate: board objects in the ID graph, moderation under the accept-all/trust-filter model, theme format + sharing, and federation between boards on different servers. Deliverable: board model sketch.
Program: Drew's 2026-10-28 directive (full text: hatch-personal memory/topics/id-program-2026-10-28.md).
Working pattern: parallel investigations, then the named synthesis issue merges them into a full design. Route guidance: Workhorse by default; Specialist/Summit for synthesis and ramification-heavy work. A result that says "done" is not the endpoint — the orchestrator reviews it and may commission another round. Deliverables: a markdown design/investigation doc (mermaid/SVG diagrams welcome) linked from this issue, plus follow-up issues for anything buildable. Build a proof of concept where the design calls for one, but do NOT build the permanent feature on top of an unreviewed PoC.
Acceptance criteria
A board model sketch exists: board objects in the ID graph, registration-free identity via Iroh ID, per-board themes with copy/share
Moderation under the accept-all/trust-filter model and federation between boards on different servers are addressed
LIST 15a investigation under epic #2056, feeding synthesis #2054. Filed by Drew 2026-10-28; not resolved by any merged PR. Suggested approach: bounded investigation write-up on this issue. Risk: theme format and moderation model are the two places a sketch can stay vague — the acceptance criteria name both.
— repo-fleet-monitor intake enrichment (protocol §5): acceptance criteria appended to the body where missing, labels normalized, meta/enriched applied.
Top priority — ID program wave-1. Drew directed this be picked up in the next runs (2026-10-29): enqueued directly as triage task 3357 in repo-health-code-pilot at queue priority 20 (only breakage-class work at priority 10 outranks it). Wave-1 is the ungated investigations and designs; syntheses and PoCs stay gated on their named inputs. Investigation route: Workhorse.
Queued: repo-health-code-pilot task 3925 (2026-10-30), wave-2 follow-on. The 2026-10-29 triage verified this issue and recorded 'write the investigation' as the next step; this task is that write — investigation doc PR under doc/, follow-up issues for buildable pieces, close with the doc link. Ordered by Drew ('queue unrun').
Task: turn task 3357's board-model sketch (2026-10-29) into the wave-pattern investigation doc under doc/ via PR, then follow-ups, summary, close
Expectation: effort/m — done = doc PR merged, follow-ups filed (routed via id: design: ID boards v1 #2054 synthesis per the sketch's §9 constraint), issue closed with the doc link
Task 3357's 2026-10-29 sketch is now the wave-pattern doc at doc/2026-10-30T19-35-00Z_investigation_boards_model/ (PR #2810, merged), re-verified against current main: no forum-board code in the tree (the only board matches are tic-tac-toe fixtures), web/ themes are terminal colour schemes unrelated to Theme objects, and the #2030 trust model is taken from its issue text (doc PR #2801 still open at write time). No change to the model.
Follow-ups #2812/#2813 are candidates for #2054 to route, not implementation go-aheads — per the sketch's §9 + program rules, nothing is commissioned before the #2054 synthesis review round.
Closed: investigation doc delivered in PR #2810 (merged as 3a0ecf7) — doc/2026-10-30T19-35-00Z_investigation_boards_model/. Follow-up candidates #2812/#2813 filed for the #2054 synthesis to route.
Activity
developing-today commentedon Oct 29, 2026
CODE-973
dezren39 commentedon Oct 29, 2026
Parent epic: #2056 — ID platform expansion (2026-10-28 directive).
dezren39 commentedon Oct 29, 2026
Intake review
LIST 15a investigation under epic #2056, feeding synthesis #2054. Filed by Drew 2026-10-28; not resolved by any merged PR. Suggested approach: bounded investigation write-up on this issue. Risk: theme format and moderation model are the two places a sketch can stay vague — the acceptance criteria name both.
— repo-fleet-monitor intake enrichment (protocol §5): acceptance criteria appended to the body where missing, labels normalized,
meta/enrichedapplied.dezren39 commentedon Oct 29, 2026
Top priority — ID program wave-1. Drew directed this be picked up in the next runs (2026-10-29): enqueued directly as triage task 3357 in repo-health-code-pilot at queue priority 20 (only breakage-class work at priority 10 outranks it). Wave-1 is the ungated investigations and designs; syntheses and PoCs stay gated on their named inputs. Investigation route: Workhorse.
9 remaining items
dezren39 commentedon Oct 30, 2026
Queued: repo-health-code-pilot task 3925 (2026-10-30), wave-2 follow-on. The 2026-10-29 triage verified this issue and recorded 'write the investigation' as the next step; this task is that write — investigation doc PR under doc/, follow-up issues for buildable pieces, close with the doc link. Ordered by Drew ('queue unrun').
dezren39 commentedon Oct 30, 2026
🤖 Agent note · picked up (write the investigation doc in this pass)
Merge pull request #2810 from developing-today/queue/3925-2052-boards
dezren39 commentedon Oct 30, 2026
🤖 Agent note · done (investigation doc delivered; PR merged)
Investigation write — boards model (#2052)
Task 3357's 2026-10-29 sketch is now the wave-pattern doc at
doc/2026-10-30T19-35-00Z_investigation_boards_model/(PR #2810, merged), re-verified against current main: no forum-board code in the tree (the onlyboardmatches are tic-tac-toe fixtures),web/themes are terminal colour schemes unrelated to Theme objects, and the #2030 trust model is taken from its issue text (doc PR #2801 still open at write time). No change to the model.Follow-ups #2812/#2813 are candidates for #2054 to route, not implementation go-aheads — per the sketch's §9 + program rules, nothing is commissioned before the #2054 synthesis review round.
dezren39 commentedon Oct 30, 2026
Closed: investigation doc delivered in PR #2810 (merged as 3a0ecf7) — doc/2026-10-30T19-35-00Z_investigation_boards_model/. Follow-up candidates #2812/#2813 filed for the #2054 synthesis to route.