Skip to content

id: investigate: boards — a modern phpBB on ID identity: no registration, copyable themes #2052

Closed

Description

@dezren39

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
  • Findings feed the boards v1 synthesis (id: design: ID boards v1 #2054) by link

Activity

  1. added
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    on Oct 29, 2026
  2. developing-today commented on Oct 29, 2026

    @developing-today
    Contributor
  3. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    Parent epic: #2056 — ID platform expansion (2026-10-28 directive).

  4. added
    effort/mMedium: expected under 1 day of work
    kind/questionQuestion or design decision to resolve
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    priority/highImportant and time-sensitive
    source/humanFiled directly by a human
    on Oct 29, 2026
  5. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    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/enriched applied.

  6. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    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.

  7. removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Oct 29, 2026
  8. 9 remaining items

  9. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    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').

  10. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Oct 30, 2026
  11. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up (write the investigation doc in this pass)

  12. added a commit that references this issue on Oct 30, 2026
  13. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    🤖 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 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.

  14. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)effort/mMedium: expected under 1 day of workkind/questionQuestion or design decision to resolvemeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/highImportant and time-sensitivesource/humanFiled directly by a human

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions