Spike LiteLLM standalone and SDK parity for the commodity gateway #41

New issue

Closed

opened 2026-07-23 05:32:28 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-23 05:32:28 +00:00

Member

Parent: #40

Prove whether LiteLLM Proxy standalone mode or LiteLLM SDK embedding can replace the current commodity inference gateway while Agent Proxy keeps its own identity, policy, correlation, context-safety, structural detection, and event-emission responsibilities.

Dependencies:

None

Acceptance criteria:

Compare standalone and SDK mode against the current OpenAI-compatible surface, streaming, model discovery, provider routing, retry, fallback, keys, budgets, cost accounting, and observability hooks.
Document the selected integration boundary and any gaps that block cutover.
Produce executable parity fixtures for the retained request-path behaviors.
Do not delete or weaken current reliability behavior until parity is demonstrated.
Link the results to the architecture v2 and trajectory contract v1 documents.

Historical gateway issues may be cited as evidence only. Do not reopen or repurpose them.

Parent: #40 Prove whether LiteLLM Proxy standalone mode or LiteLLM SDK embedding can replace the current commodity inference gateway while Agent Proxy keeps its own identity, policy, correlation, context-safety, structural detection, and event-emission responsibilities. Dependencies: - None Acceptance criteria: - Compare standalone and SDK mode against the current OpenAI-compatible surface, streaming, model discovery, provider routing, retry, fallback, keys, budgets, cost accounting, and observability hooks. - Document the selected integration boundary and any gaps that block cutover. - Produce executable parity fixtures for the retained request-path behaviors. - Do not delete or weaken current reliability behavior until parity is demonstrated. - Link the results to the architecture v2 and trajectory contract v1 documents. Historical gateway issues may be cited as evidence only. Do not reopen or repurpose them.

coilyco-ops referenced this issue

2026-07-23 05:37:21 +00:00

Reset Agent Proxy as a LiteLLM-backed trajectory and observability platform #40

coilyco-ops referenced this issue from a commit

2026-07-24 18:40:47 +00:00

feat: select standalone LiteLLM boundary (closes #41)

coilyco-ops closed this issue

2026-07-24 18:40:48 +00:00

coilyco-ops referenced this issue

2026-07-24 19:07:01 +00:00

[interactive] Deploy trajectory ledger, evaluate LiteLLM, and verify first activation #56

coilyco-ops referenced this issue