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
Related:#2062 (design §4), #2317/#2318 (sibling slices), #2321 (the PoC that consumes this envelope)
Notes: Gateway request envelope: canonical CBOR bodies, verify_strict only, nonce window + ReplayGuard, deterministic idempotency IDs. The body carries a full ## Acceptance list (round-trip + tamper/stale/replay rejections, forgery fixture, valid-signature-from-non-minter rejection), so this pass is labels-only.
Risks: The verify-vs-verify_strict distinction and the idempotency-ID vs TigerBeetle monotonic-ID tension (§9.3) are the two places a quiet shortcut becomes a security or correctness hole.
Suggested approach: Reuse directory_auth.rs's Signed scheme as scoped; resolve the §9.3 tension explicitly in the implementation note; test the forgery fixture first.
🤖 Agent note · filed
Agent: fleet monitor (repo-fleet-monitor)
Session / ID: repo-fleet-monitor run 2026-10-29T18:12Z (13:12 CDT)
Found via: monitor reconciliation
Task: Duty 2 intake enrichment — labels normalized and meta/enriched applied; acceptance criteria appended to the body only where no acceptance section existed (original body preserved verbatim above it). Still-live check this pass: no merged PR or fix commit explicitly resolving this issue was found in this pass's search.
Expectation: see the effort label; done = the acceptance criteria are met.
agent-note:v1
state: triaged (coverage pass)
Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 40 (priority/normal). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
Found via: coverage pass 2026-11-03
Finding: F3 is still unimplemented on current main. Reusable primitives already exist in pkgs/id/src/directory_auth.rs (Signed, sign/verify, strict Ed25519 verification, 5-minute window and ReplayGuard), but there is no id-currency-wire crate or currency gateway request envelope/route. pkgs/id/src/currency_poc is a conversion executor/recovery PoC, not the issue→transfer gateway.
Scope and ordering: implement the shared domain-tagged canonical request-body encoding, deterministic idempotency-ID derivation and typed errors in the shared wire module; reuse directory_auth rather than reimplementing signatures. Design §4.6-4.7 places the route in the existing web server while preserving a single logical ledger writer. F3 has no hard dependency; the end-to-end F5 PoC depends on F1-F3, with F2 depending on F1 (id(currency): currency registry schema + ledger-u32 allocator (from #2062) #2317/id(currency): deterministic account factory + per-currency system accounts (from #2062) #2318). Explicitly resolve design §9.3's idempotency-ID vs TigerBeetle monotonic-ID tension in the implementation note. No external blocker prevents F3 from starting.
Next: implementation proceeds under this existing issue; no duplicate follow-up task was created.
Activity
developing-today commentedon Oct 29, 2026
CODE-1169
dezren39 commentedon Oct 29, 2026
Intake review
Related: #2062 (design §4), #2317/#2318 (sibling slices), #2321 (the PoC that consumes this envelope)
Notes: Gateway request envelope: canonical CBOR bodies, verify_strict only, nonce window + ReplayGuard, deterministic idempotency IDs. The body carries a full
## Acceptancelist (round-trip + tamper/stale/replay rejections, forgery fixture, valid-signature-from-non-minter rejection), so this pass is labels-only.Risks: The verify-vs-verify_strict distinction and the idempotency-ID vs TigerBeetle monotonic-ID tension (§9.3) are the two places a quiet shortcut becomes a security or correctness hole.
Suggested approach: Reuse directory_auth.rs's Signed scheme as scoped; resolve the §9.3 tension explicitly in the implementation note; test the forgery fixture first.
🤖 Agent note · filed
meta/enrichedapplied; acceptance criteria appended to the body only where no acceptance section existed (original body preserved verbatim above it). Still-live check this pass: no merged PR or fix commit explicitly resolving this issue was found in this pass's search.dezren39 commentedon Nov 3, 2026
🤖 Agent note · handed off
opencode; handing off to the laptop claimant, which polls for claimed, opencode-assigned, unbound tasks and launches a bound session.developing-today commentedon Nov 3, 2026
agent-note:v1
state: triaged (coverage pass)
Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 40 (priority/normal). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
Found via: coverage pass 2026-11-03
dezren39 commentedon Nov 3, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 3, 2026
🤖 Agent note · handed off
opencodedezren39 commentedon Nov 4, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 4, 2026
🤖 Agent note · triaged