-
Notifications
You must be signed in to change notification settings - Fork 2
Campaign map: Gateway deep modules & Codex↔Chat #441
Copy link
Copy link
Open
3 / 33 of 3 issues completedLabels
P1Priority 1: current iteration goalPriority 1: current iteration goalcampaign:gateway-chatGateway deep modules and Codex↔Chat bridgeGateway deep modules and Codex↔Chat bridgeenhancementNew feature or requestNew feature or requestwayfinder:mapWayfinder campaign mapWayfinder campaign map
Description
Activity
Metadata
Metadata
Assignees
Labels
P1Priority 1: current iteration goalPriority 1: current iteration goalcampaign:gateway-chatGateway deep modules and Codex↔Chat bridgeGateway deep modules and Codex↔Chat bridgeenhancementNew feature or requestNew feature or requestwayfinder:mapWayfinder campaign mapWayfinder campaign map
Notes
Campaign: Gateway Deep Modules & Codex↔Chat Bridge.
Label:
campaign:gateway-chat.No version number until the standard Chat floor is green.
Two tracks after this map exists:
codex_proxy.pyand deepenprotocol_translation.pyso Codex Responses can ride third-party Chat Completions without a second adapter.Hard gates only:
codex_proxy.pystays the process entry and re-export facade. Extracted modules must not import it. Official passthrough stays unchanged. No hidden Responses / Official / model / Provider fallback.Decisions-so-far
upstream_plumbing.py.gateway_sse.pyowns framing/commit/terminal only, not Chat codec semantics._responses_request_to_chat_completion_bodystays a thin wrapper overprotocol_translation.Fog
v0.1.9is tagged.Work packages
Track 0 — 0.1.9 closeout (parallel with Track 1 after WP0)
mainv0.1.9or a written beta4-is-final decisionTrack 1 — Gateway modules + Chat bridge
protocol_translationbehindprepare_exchangeand land the standard Chat floorChild tickets