Skip to content

id: investigate: embedded playable posts — HTML5 mini-games, async challenges, and forkable succession saves #2053

Closed

Description

@dezren39

LIST 15b. Boards should host little 'flash-game-type' things (HTML5 equivalents) that people build and post — and challenges: challenge someone to a game of chess over the system, played over time. Examples to design against: (1) the multiplayer eat-the-dots game where your dot grows as you eat others; (2) D&D-style role-playing threads; (3) succession games — the Dwarf Fortress pattern where one player takes the fortress for a set number of in-game years, then 'from this save point, it passes on to this person' — forkable and built in. Investigate: the embeddable game object, async turn/state passing, save-point forking in the graph, and how match attestation (LIST 10) plugs in. Deliverable: game-post model with the three examples walked through.

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 written investigation exists covering the embeddable game object and async turn/state model for challenges
  • The three design examples in the issue (multiplayer eat-the-dots, D&D-style threads, Dwarf-Fortress succession forks) are each 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 15b 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 per the program pattern. Risk: game-object design drifting from the board model in #2052 — cross-link findings early.

    — 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 3358 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 3926 (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 — playable posts (#2053)

    Task 3358's 2026-10-29 game-post model is now the wave-pattern doc at doc/2026-10-30T19-45-00Z_investigation_playable_posts/ (PR #2815, merged), re-verified against current main: tic-tac-toe .wasm + roc examples present, world capability/resource docs present, #2026/#2032 closed and #2037/#2050/#2054/#2266 open as scoped. No change to the model.

    Gate update for #2054: #2052's doc has also landed (PR #2810, merged) — both investigations this synthesis was waiting on are now wave-pattern docs. PoC #2266 remains the only open buildable from this issue; nothing new filed.

  14. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    Closed: investigation doc delivered in PR #2815 (merged as a7b66f9) — doc/2026-10-30T19-45-00Z_investigation_playable_posts/. PoC #2266 stays open; synthesis #2054 unblocked from this issue's side.

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