id: PoC: game-post with async turn passing — tic-tac-toe as a board post, signed turns, concession result, save-point fork (from #2053)

From the #2053 investigation (embedded playable posts)

Investigation #2053 (queue task 3358, result posted on that issue 2026-10-29) designed the game-post model: a board post carrying a world/app package reference + mode (live-session | async-turns | succession), turns as signed events, save-point objects with handoff/fork semantics, and #2037 attestation as an opt-in plug-in. This issue is the proof of concept for the async-turns mode — not the permanent feature (program rule, epic #2056).

PoC scope

Using the existing tic-tac-toe example (pkgs/id/examples/tic-tac-toe) as the game package:

A game-post object referencing the package (hash + version), mode async-turns, two player IDs, attestation mode concession.
A challenge flow: post → challenge-acceptance object by the second player → alternating signed turn objects, each naming the prior state frontier — played fully asynchronously (no live session; the two sides sync between turns).
Game end emits the id: investigate: match-result attestation — mutual concession, witness adjudication, offline play #2037 pair of signed result claims; agreeing claims compute agreed (per the id: investigate: match-result attestation — mutual concession, witness adjudication, offline play #2037 model / id: PoC: mutual-concession match attestation on the tic-tac-toe example — genesis agreement + dual signed result claims, offline-first (from #2037) #2248 PoC shapes if it lands first — coordinate, do not duplicate).
A save-point + fork demonstration: from a mid-game frontier, a third ID forks a continuation; both lines proceed independently and the fork object preserves attribution to the original line.

Out of scope

Live-session (real-time) games, succession handoff chains (the fork primitive here is their foundation; the chain policy is #2054's), board UI, sandbox policy changes.

Acceptance criteria

PoC demonstrates scope points 1–4 with the object shapes documented in the PR/issue
Findings note posted on this issue: what the PoC proved about the game-post model, what it did not
No production game-post feature claimed or merged under this issue

Program: ID platform expansion, epic #2056. Parent investigation: #2053. Related: #2052 (boards), #2054 (boards v1 synthesis), #2037/#2248 (attestation), #2026 (app packaging).

CODE-1129

Agent note — picked up (queue task 3421, openchamber scheduled lane)

Claimed 2026-10-30 ~11:54Z for revalidation. Fresh GitHub check: issue OPEN (priority/high), no PR references it, no live branch. This is a 120m PoC-build task (async-turn tic-tac-toe proving the #2053 game-post model), beyond this ~30m lane — parking untouched (no branch, no worktree, no edits).

Agent note — parked untouched (needs a full-budget shift)

Queue task 3421 re-parked with zero state: no branch, no worktree, no edits. Next lane starts clean.
Resume brief: packet revalidated 2026-10-30 ~11:56Z — issue OPEN, PR search shows no owning PR, no queue/3421 or 2266 branch on the laptop clone. Deliverable is a working PoC (four scope points on the issue, object shapes documented) plus a findings note of what it proved and did not prove — a single build shift, not a short-lane slice. Note the acceptance guardrail: no production game-post feature under this issue.
Labels: issue carried queue/queued + status/needs-triage, so this pass sets the parked end-state directly (queue/parked + status/parked + work/assigned, queued/needs-triage removed).
Lane note: laptop gh hosts.yml token was stale in this session; notes posted with transient GH_TOKEN from vault key github-cli.hosts-yml.

🤖 Agent note · picked up

Agent: queue worker (repo-worker-code), OpenChamber scheduled lane 7b47536b-c162-444c-be8a-3a9538cc4cb5
Session / ID: queue task 7320
Found via: atomic queue claim
Task: Triage issue id: PoC: game-post with async turn passing — tic-tac-toe as a board post, signed turns, concession result, save-point fork (from #2053) #2266, the signed async tic-tac-toe game-post PoC.
Scope: Verify what exists at current main versus what is missing; packet says leave the existing user/escalated state as-is.
Next: Freshly inspect issue and current code before making a triage determination.

🤖 Agent note · triaged

Verified on: fresh origin/main 5fbb1b3 in /home/user/git/fleet/7320.
Already built: PR test(id): PoC — game-post with async turn passing on tic-tac-toe (#2266) #2755 is MERGED at 62f5829 and changed only pkgs/id/tests/game_post_async_turns_poc.rs. Its tests model signed game.post/challenge.accept objects, alternating async turns, mutual-concession result agreement, and save-point/fork behavior.
Adjacent production support: pkgs/id/src/boards.rs:76 documents a typed reference to a signed game-post object and explicitly says game execution is out of scope. pkgs/id/src/world/tests.rs:4794 exercises alternating signed tic-tac-toe moves through the world path, separately.
Not built: a production game-post lifecycle/handler integrating challenges, async turns, concession, and save-point/fork behavior. Those protocol behaviors remain in the test-only PoC.
Disposition: this PoC slice is landed; id: PoC: game-post with async turn passing — tic-tac-toe as a board post, signed turns, concession result, save-point fork (from #2053) #2266 remains OPEN for the production-scope/ownership decision. Per packet, user/escalated is retained unchanged and no new follow-up is enqueued.
Verification: read-only issue/PR/source-state verification; no local tests run.

🤖 Agent note · done

Agent: queue worker (repo-worker-code), OpenChamber scheduled lane 7b47536b-c162-444c-be8a-3a9538cc4cb5
Session / ID: queue task 7320
Outcome: Triaged. The signed async game-post flow is a merged test-only PoC in PR test(id): PoC — game-post with async turn passing on tic-tac-toe (#2266) #2755; production game execution remains explicitly out of scope.
Issue state: id: PoC: game-post with async turn passing — tic-tac-toe as a board post, signed turns, concession result, save-point fork (from #2053) #2266 remains OPEN; user/escalated retained as requested. Lifecycle labels for this task were cleared.
Artifacts: PR test(id): PoC — game-post with async turn passing on tic-tac-toe (#2266) #2755 merged at 62f5829; source verification worktree /home/user/git/fleet/7320 at 5fbb1b3. No code changed.
Bookkeeping: sandbox backlog and sweep log deferred to fleet reconciliation.

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-z
Session / ID: task 12044
Found via: queue claim
Task: Triage issue id: PoC: game-post with async turn passing — tic-tac-toe as a board post, signed turns, concession result, save-point fork (from #2053) #2266 — handed off to the opencode execution lane per §1b (assigned_lane=opencode); claimant launches the bound opencode session
Expectation: triage; done = claimant records what remains against current state, converts any actionable remainder to a scoped fix packet, or closes with merged-PR evidence if fully satisfied
Links: issue id: PoC: game-post with async turn passing — tic-tac-toe as a board post, signed turns, concession result, save-point fork (from #2053) #2266

Navigation Menu

Repository navigation

id: PoC: game-post with async turn passing — tic-tac-toe as a board post, signed turns, concession result, save-point fork (from #2053) #2266

From the #2053 investigation (embedded playable posts)

PoC scope

Out of scope

Acceptance criteria

36 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

id: PoC: game-post with async turn passing — tic-tac-toe as a board post, signed turns, concession result, save-point fork (from #2053) #2266

Description

From the #2053 investigation (embedded playable posts)

PoC scope

Out of scope

Acceptance criteria

Activity

developing-today commented on Oct 29, 2026

dezren39 commented on Oct 30, 2026

dezren39 commented on Oct 30, 2026

36 remaining items

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 4, 2026

developing-today commented on Nov 8, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions