backend-workflow-entry

To maintain backward compatibility for legacy backend entry calls, use an adapter that preserves original requests and delegates routing decisions to a modern workflow entry point. This ensures older systems interact with current infrastructure without requiring immediate code changes.

A legacy backend adapter is a compatibility layer that forwards deprecated backend entry methods to a modern workflow infrastructure. You need one when a legacy application must interact with current routing and sandbox systems without undergoing immediate code refactoring.

To route a legacy backend request to a modern workflow entry point, use a delegation adapter that preserves the original request format and forwards the workflow entry mode. The adapter ensures execution follows the route determined by the modern workflow entry skill.

Yes, you can use a backend adapter to forward requests without modifying the original call. The adapter preserves the original request, forwards the workflow entry mode, and delegates all routing and sandbox decisions to the workflow entry skill.

Yes, the backend workflow delegation adheres to the codex execution contract. The adapter ensures that execution follows the route determined by the workflow entry skill, maintaining compliance with the required execution standards.

The limitation of using a compatibility layer for legacy backend systems is that it does not process requests independently. It strictly delegates all routing and sandbox decisions to the workflow entry skill, meaning execution relies entirely on the delegated skill's availability.