Enterprise Readiness

[franciscojavierarceo]

Problem statement / motivation

Enterprise Readiness groups the enhancements needed to operate vLLM Agentic API as a secure, predictable service for Responses and Messages workloads. The focus is authenticated state ownership, reliable execution, protocol compatibility, complete usage accounting, and repeatable release qualification.

Proposed solution

Track the work in the existing focused issues where available, with new issues for capabilities that did not yet have an owner. These are feature enhancements; completion is determined by the linked acceptance criteria and validation evidence.

Enhancement checklist

• Enforce user and tenant ownership for persisted state #107 — Authenticated user and tenant ownership for persisted state and continuation.
• Add bounded, validated Messages streaming and tool scheduling #313 — Bounded, validated Messages streaming and tool scheduling.
• Preserve request capabilities and transport metadata across execution paths #314 — Request capability and transport metadata preservation across execution paths.
• Complete the OpenAI-compatible Conversations API #155 — Standard Conversations API references, creation payloads, and resource operations.
• Support Approval path for MCP tools. #145 — Resumable MCP tool approval policies and enforcement.
• Add complete multi-round Messages usage accounting #315 — Complete multi-round Messages usage accounting.
• Add deployment, authentication, and persistence end-to-end verification #110 — Deployment, authentication, persistence, and protocol qualification through the actual service.

Delivery order

1. Establish authenticated ownership and predictable Messages lifecycle/resource behavior; develop the request capability contract alongside them.
2. Complete standard conversation workflows, approval-dependent tool workflows, and usage reporting for the supported deployment profiles.
3. Qualify those profiles through deterministic integration tests and documented engine coverage before declaring the initiative complete. Build the qualification harness throughout the work, not only at the end.

Shared multi-tenant operation depends on #107. Approval-dependent tools depend on #145. Metered multi-round Messages workloads depend on #315. Narrower deployment profiles can ship with explicit capability limits while this initiative remains open.

Completion criteria

• Every enhancement above meets its acceptance criteria, or an explicit scope decision updates this tracker and the roadmap.
• Supported Responses and Messages capabilities, resource limits, ownership rules, and failure behavior are documented.
• Repeatable release evidence distinguishes mock integration tests, recorded replay, and live-engine coverage, including unsupported scenarios.
• Single-tenant and supported shared deployments have documented upgrade and operational guidance.

Additional context

This initiative builds on #102 (hosted deployment), #211 (engine conformance), #241/#244 (streaming boundaries), and #279 (observability). Those workstreams retain their own scope. Existing fixes in #290 and #296 and Dynamo Messages recordings in #292 are inputs to the qualification work.

Additional search providers, file-search expansion, new upstream protocol adapters, and broader tool families remain separate capability work unless a supported enterprise deployment profile explicitly requires them.

Roadmap update: #317