Skip to content

id: design: ID currencies v1 #2043

Open

Description

@dezren39

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.

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. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  5. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    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:

    1. Snapshot signer for the developing-today deployment — issuer key or a dedicated service ID.
    2. Snapshot cadence — per-N issuances, time-based, or acceptance-triggered (the format supports all three).
    3. Issuer key-rotation mechanics (id: investigate: token issuance in the ID graph — per-ID issuance, issuer snapshots, authorized conversion rates #2041 abuse case 7): rotation object format, and which key generation(s) a counting view pins for pre-rotation definitions. The spec bounds mint damage via supply caps but does not settle rotation.
    4. Shared fold/index service for graph-native currencies, or purely client-side folds.
    5. Receipt interplay with id: investigate: tokens for real services — Steam-key grants, returns/refunds, revocation #2042: the spec's accept_payment receipt 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.
  6. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

    • Agent: queue worker (repo-worker-code), OpenChamber scheduled lane
    • Session / ID: ses_e5e68048783ffeEYpO14Ny2vPz / queue task 5731
    • Found via: repo-health-code-pilot atomic claim
    • 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.
  7. added
    queue/blockedQueue or user escalation state
    status/blockedQueue or user escalation state
    and removed
    queue/claimedQueue worker lifecycle state
    on Nov 1, 2026
  8. 33 remaining items

  9. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

    • Agent: fleet monitor (repo-fleet-monitor)
    • Session / ID: task 8586 · repo-fleet-monitor run 2026-11-03 20:12 CST
    • Found via: monitor reconciliation
    • 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.
  10. added
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 4, 2026
  11. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

    • Agent: queue worker (repo-worker-code), OpenChamber scheduled lane 02cafe76-eafd-4d0b-aaa6-2b7a737d68dc
    • Session / ID: ses_e5e5ab6c0c3ffeMl3QTY5Iseou / queue task 8586
    • Found via: repo-health-code-pilot atomic claim
    • 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.
  12. added
    user/escalatedQueue or user escalation state
    status/blockedQueue or user escalation state
    queue/blockedQueue or user escalation state
    and removed
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 4, 2026
  13. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · escalated

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)queue/blockedQueue or user escalation statesource/creatorFiled by the new-issue-creator jobstatus/blockedQueue or user escalation statetask/triageQueue packet kind: verify, reproduce, and route this itemuser/escalatedQueue or user escalation state

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions