Emit bounded request lifecycle trajectory events #55

Closed
opened 2026-07-24 18:58:18 +00:00 by coilyco-ops · 0 comments
Member

Goal

Connect the current OpenAI-compatible request path to the landed contract-v1 bounded emitter without adding storage waits or body capture to model latency.

Acceptance criteria

  • Add an opt-in request-event emitter backed by the configured durable trajectory store and bounded queue.
  • Emit metadata-only action.proposed and terminal execution events for chat and legacy completion requests.
  • Preserve request, Ward, agent-session, repository, issue, workflow, model, token, finish, and normalized outcome evidence when available.
  • Never retain prompts, responses, tools, raw diagnostics, or upstream bodies through this path.
  • Keep emission non-blocking and report queue or persistence failures without crashing request handling.
  • Preserve current gateway behavior and keep deployment enablement off until durable storage is configured.
  • Add focused tests and update the shipped feature inventory.
## Goal Connect the current OpenAI-compatible request path to the landed contract-v1 bounded emitter without adding storage waits or body capture to model latency. ## Acceptance criteria * Add an opt-in request-event emitter backed by the configured durable trajectory store and bounded queue. * Emit metadata-only `action.proposed` and terminal execution events for chat and legacy completion requests. * Preserve request, Ward, agent-session, repository, issue, workflow, model, token, finish, and normalized outcome evidence when available. * Never retain prompts, responses, tools, raw diagnostics, or upstream bodies through this path. * Keep emission non-blocking and report queue or persistence failures without crashing request handling. * Preserve current gateway behavior and keep deployment enablement off until durable storage is configured. * Add focused tests and update the shipped feature inventory.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agent-proxy#55
No description provided.