Saxo broker follow-ups — 2026-04-12¶
This page tracks the human follow-up queue around Saxo Ticket #16633 and preserves the
lightweight code-audit result that originally created this file.
Current state¶
- Q1 and Q2 are effectively closed from the operator side.
- Q3 (
COB routing) is still the unresolved blocker on the Saxo support thread. - IBKR parity collection is already in progress and is intended to become attachment material for the follow-up mail.
- If Saxo remains silent, the next scheduled checkpoints are:
- follow-up mail on
2026-04-15 - higher escalation on
2026-04-22
Follow-up tracker¶
| Follow-up item | Owner | Status | Due / trigger | Current evidence | Next action |
|---|---|---|---|---|---|
Q1 understanding fixed (multileg bid/ask is Indicative) |
session owner | done | 2026-04-08 | reflected in saxo_ticket_16633_email_draft_ja.md and saxo_escalation_checklist.md |
no further action unless Saxo contradicts the current understanding |
Q2 understanding fixed (OpenAPI current behavior / constraints) |
session owner | done | 2026-04-08 | same evidence set as Q1 | keep only as context for the next reply |
| Q3 explicit COB routing answer | Saxo Japan / session owner | pending | open since 2026-04-08 | cob_routing_comparison.md documents why this remains the decisive unanswered point |
ask the question again in the follow-up mail if still unanswered |
| Follow-up mail with evidence bundle | session owner | pending | 2026-04-15 if no reply by then | draft exists in saxo_ticket_16633_email_draft_ja.md; attachment plan exists in saxo_escalation_checklist.md |
send the draft with combo bid observations, CR deviation material, and parity data if available |
| Final escalation to higher support / compliance path | session owner | pending | 2026-04-22 if Q3 is still unanswered | checklist already records this as the 14-day escalation point | escalate only after the 2026-04-15 follow-up is sent and logged |
| IBKR parity evidence collection | Codex / Claude shadow lane | in progress | started 2026-04-12 | R5#13-R5#16 added mock generator, join pipeline, and parity tests; live parity still needs the password-reset blocker cleared | keep collecting parity-ready artifacts so the follow-up mail can attach real comparisons |
Code-audit snapshot¶
Scanned aegis_v3/aegis/broker/saxo/** for TODO:, FIXME:, XXX:, and HACK: markers.
| file:line | marker | one-line quote | suggested owner |
|---|---|---|---|
| none | none | rg -n "TODO:|FIXME:|XXX:|HACK:" aegis_v3/aegis/broker/saxo returned no matches. |
Codex lane |
Operator notes¶
- This page is intentionally limited to facts that already exist in WORK_LOG or adjacent runbooks.
- Exact ticket filing timestamp is still not pinned in the current logs; do not retroactively invent it here.
- If the parity attachment is still unavailable at follow-up time, write
[needs input from session owner]in the outbound mail rather than implying the data exists.