developer-delphi-rest-dataware-orchestrator

Routing REST DataWare tasks in Delphi requires classifying the inquiry and delegating it through a canonical sequence of sub-skills (expert, estrutura, roteiro). This orchestrator validates requests and directs them to the appropriate server, client, or driver configuration without embedding implementation details.

The canonical REST DataWare sequence flows from expert to estrutura to roteiro. This progression centralizes decision-making and streamlines guidance for RDW APIs, servers, drivers, and security configurations.

Yes, the orchestrator applies across REST DataWare authentication and driver configurations. It acts as a central entry point to locate and delegate these specific RDW tasks to the appropriate Delphi sub-skills.

To start orchestrating a REST DataWare scenario, describe the specific RDW task or server setup issue. The orchestrator validates the request and routes it to the correct Delphi sub-skill based on classification rules.

No, the REST DataWare orchestrator deliberately avoids embedding implementation details. It strictly classifies and routes inquiries to specialized sub-skills, ensuring the actual API implementation logic is handled by the targeted Delphi components.

You need an orchestrator for Delphi REST DataWare workflows when you require centralized decision-making for component routing. It is necessary when managing multiple RDW tasks across server setups, client implementations, and security configurations.