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
LIST 11 synthesis. Merge the three currency investigations (TigerBeetle, issuance-in-graph, real-services lifecycle) into currencies v1: token model, ledger boundary, conversion authorisation, and the open-source boundary (most of this software is to be released open source). The token's own name stays TBD (candidates: id bucks, d3v, dt, 2d, d2d). Specialist/Summit-grade synthesis.
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.
For the #2043 synthesis — open questions routed from the #2251 spec (queue task 3406)
The graph token spec (PR #2741, doc/2026-10-30T13-25-00Z_design_graph_token_formats_snapshot_anchoring.md, §7) deliberately does not decide the following; they are synthesis inputs for this issue, which remains gated on #2042 as well:
Snapshot signer for the developing-today deployment — issuer key or a dedicated service ID.
Snapshot cadence — per-N issuances, time-based, or acceptance-triggered (the format supports all three).
Task: Revalidate id: design: ID currencies v1 #2043 and produce the requested design record plus phased implementation packets if the live issue and route support this queue task.
Next: Verify synthesis inputs and current ownership/routing; block as packet_defect if the task conflicts with the issue's live specialist/synthesis direction.
Task: Claim evaporated — task 8586 returned to queued and unclaimed in repo-health-code-pilot after the holding run ended without a terminal verb (checkpoint stage: handed_off). Labels reset to the truth: queue/queued + status/needs-triage. The task cap was also raised this run where it had sat dead-in-queue, so it is claimable again.
Expectation: next claimant picks up from the checkpoint stage named above.
Task: Revalidate id: design: ID currencies v1 #2043 and route this safety-net triage against fresh GitHub state; prior triage notes indicate the synthesis is merged and the remaining gate is Drew’s policy decisions.
Next: Verify current PR/design/follow-up state and latest issue activity, then record the terminal triage verdict without duplicating existing work.
Blocker: six explicit policy choices in the merged design require Drew: public currency name; supply cap; recovery-key mandate for anchored currencies; emergency platform-revoke authority; grant/hold terms; and open-source boundary. No ruling is present in the issue activity since the design summary. These are genuine owner decisions, not worker-resolvable work.
Next: Drew records the six rulings; then the orchestrator can route the dependent implementation phases. Restored user/escalated, status/blocked, and queue/blocked; removed this claim’s in-flight labels.
Activity
developing-today commentedon Oct 29, 2026
CODE-964
dezren39 commentedon Oct 29, 2026
Parent epic: #2056 — ID platform expansion (2026-10-28 directive).
dezren39 commentedon Oct 29, 2026
🤖 Agent note · handed off
dezren39 commentedon Oct 30, 2026
For the #2043 synthesis — open questions routed from the #2251 spec (queue task 3406)
The graph token spec (PR #2741,
doc/2026-10-30T13-25-00Z_design_graph_token_formats_snapshot_anchoring.md, §7) deliberately does not decide the following; they are synthesis inputs for this issue, which remains gated on #2042 as well:accept_paymentreceipt names the payment and the effect taken; the reversal/refund vocabulary is left to the id: investigate: tokens for real services — Steam-key grants, returns/refunds, revocation #2042 design.dezren39 commentedon Nov 1, 2026
🤖 Agent note · picked up
33 remaining items
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 4, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 4, 2026
🤖 Agent note · escalated
fc1d656e7e1c869a28658a0cff7f85d55cd43834) anddoc/2026-11-01_design_id2043.mdis present on main. The design has phased follow-ups already tracked (id: implement: pkgs/id currency client API — the §7 app-facing function surface from #2041 (gated on #2251 spec) #2803, id: poc: currency gateway boundary — UserDO snapshot cache, signed transfer + hold, idempotent retry across hibernation #2298, id(currency): gateway verification flow + revocation-set check for RateAuthorisation (Phase 2 of #2290) #3801, id(currency): quote issuance + binding for RateAuthorisation (Phase 3 of #2290) #3802, id: PoC: conversion executor — linked transfer pairs, write-ahead intent, recovery scanner #2289, id: decide: grant refund window length and whether pending tokens are spendable #2296, id: design: RateAuthorisation as a signed ID-graph object — schema, signing, revocation #2290, id: design: conversion engine — linked transfer pairs, rate authorisation, liquidity accounts #2063, id: design: issuer key rotation and compromise recovery for currency issuers (from #2041) #2804); no duplicate packet was added.user/escalated,status/blocked, andqueue/blocked; removed this claim’s in-flight labels.