ADIL ECO · DEPLOYMENT AND TROUBLESHOOTING

Deploying a candidate, and fixing the first problems.

Guidance for qualified testers and developers following the programme. Neither the Eco V1.1 A3b model nor the SDK is publicly released: there is no download, package or installer, and nothing on this page announces one.

Before you deploy

  • Use the model, engine library, host and SDK from the same release. The SDKs refuse mismatched components and there is no compatibility fallback.
  • Pin the model by SHA-256. The engine verifies it before loading and refuses any other file.
  • Install the components in a directory your application owns and that other users cannot write to.
  • Set a context profile (4K default, 8K maximum), a request deadline and a maximum output length.
  • Classify every tool as read-only, state-changing or sensitive before registering it.
  • Plan for a memory budget with headroom above the measured figures.

Common errors

SymptomMeaningWhat to do
Cannot connect to the local service (HTTP path)Nothing is listening on the local address.Start the local service; check the port and the configured base URL.
Model not readyThe model is still loading, or the service exited.Wait until ready; if the service exited, read its error output.
Library or host refusedThe engine library or host is not the expected version 2 component set.Use the matching components from one release; do not point loader variables at other directories.
Model identity errorThe file does not match the pinned SHA-256.Re-obtain the file; do not disable the check.
Context length errorPrompt plus output exceed the 8,192-token limit.Shorten the input or lower the maximum output.
Output stopped at the limitFinish reason is length.Raise the maximum output length.
Invalid structured outputThe result was not valid JSON for your schema, or was truncated.Raise the output limit, simplify the schema, retry or handle the failure.
BusyThe session runs one operation at a time.Queue requests, or retry after a short delay.