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
{{ message }}
Repository navigation
id: design: currency as the centralised exception — how the hosted (Workers) edition reaches the currency service #2066
Source: the TigerBeetle investigation (on #2040) + the Cloudflare Workers fit investigation (on #2044). TigerBeetle cannot run in isolates, so in an otherwise serverless ID architecture, currency is deliberately centralised. Design the boundary: the gateway's API shape for hosted and native clients, and which currency operations (issue/transfer/convert/balance) each edition may perform.
Program: Drew's 2026-10-28 directive (full text: hatch-personal memory/topics/id-program-2026-10-28.md). Parent epic: #2056.
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 markdown design doc is linked from this issue defining the currency boundary for the hosted (Workers) edition: the gateway API shape for hosted and native clients.
The doc states which currency operations (issue / transfer / convert / balance) each edition may perform, and through which path.
The centralised-currency exception is justified against the otherwise-serverless ID architecture, with the TigerBeetle-can't-run-in-isolates constraint cited.
Anything buildable that falls out of the design is filed as follow-up issues linked here.
Related: parent epic #2056; source investigations #2040 (TigerBeetle) and #2044 (Workers fit); feeds the currencies v1 synthesis #2043 and the conversion/control-plane designs #2062/#2063.
Notes: part of the 2026-10-28 ID program batch filed this morning; a design deliverable, not a build — the endpoint is a reviewed design doc plus follow-ups, per the program pattern in the body.
Risks: the gateway shape decided here constrains #2062 (control plane) and #2063 (conversion engine); sequence or cross-check those designs before any build.
Suggested approach: Workhorse-grade design pass per the program route guidance; escalate to Specialist/Summit only for the synthesis step.
— Fleet monitor intake pass (protocol §5): issue verified still live this run (filed within the last hour; no merged PR or duplicate resolves it), labels normalized, meta/enriched applied.
Top priority — ID program wave-1. Drew directed this be picked up in the next runs (2026-10-29): enqueued directly as triage task 3368 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.
Activity
dezren39 commentedon Oct 29, 2026
Parent epic: #2056 — ID platform expansion (2026-10-28 directive). Filed as batch 2 from PREPARED-ACTIONS.md.
developing-today commentedon Oct 29, 2026
CODE-987
dezren39 commentedon Oct 29, 2026
Intake review
Related: parent epic #2056; source investigations #2040 (TigerBeetle) and #2044 (Workers fit); feeds the currencies v1 synthesis #2043 and the conversion/control-plane designs #2062/#2063.
Notes: part of the 2026-10-28 ID program batch filed this morning; a design deliverable, not a build — the endpoint is a reviewed design doc plus follow-ups, per the program pattern in the body.
Risks: the gateway shape decided here constrains #2062 (control plane) and #2063 (conversion engine); sequence or cross-check those designs before any build.
Suggested approach: Workhorse-grade design pass per the program route guidance; escalate to Specialist/Summit only for the synthesis step.
— Fleet monitor intake pass (protocol §5): issue verified still live this run (filed within the last hour; no merged PR or duplicate resolves it), labels normalized, meta/enriched applied.
dezren39 commentedon Oct 29, 2026
Top priority — ID program wave-1. Drew directed this be picked up in the next runs (2026-10-29): enqueued directly as triage task 3368 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.
27 remaining items
dezren39 commentedon Oct 29, 2026
🤖 Agent note · picked up
dezren39 commentedon Oct 29, 2026
🤖 Agent note · parked
dezren39 commentedon Oct 29, 2026
🤖 Agent note · done (triaged)
awaiting_cicheckpoint)doc/2026-10-29T12-20-00Z_design_currency_centralised_exception/in PR doc: currency as the centralised exception — hosted boundary design (#2066) #2297 (docs-only, 1 file;basic: proxy port fallbacksPASS on head ffba169; CodeRabbit completed; Codex review no findings; MERGEABLE/CLEAN). Acceptance boxes ticked; buildable follow-up routed as id: poc: currency gateway boundary — UserDO snapshot cache, signed transfer + hold, idempotent retry across hibernation #2298 (gated PoC). PR doc: currency as the centralised exception — hosted boundary design (#2066) #2297 is in themainmerge queue at position 2 and has NOT landed — the repo-wide merge queue is stalled by the Actions runner jam tracked in ci: Actions check runs stuck in queued across PRs — no runner pickup since ~05:00Z 2026-10-28 #1599 (no merge tomainsince 10:57:51Z; 10 queue entries allAWAITING_CHECKS; merge_group jobs queued with no runner pickup). This is the third pass parked on that same wait, so the task is being completed as triaged rather than parked again.