Expose service readiness and cache state before scaling the API surface
Constraint: Industrializing the service path requires visibility into model/index availability and repeated-load behavior before adding heavier production features Rejected: Keep stateless per-request loading until later | Hides readiness problems and wastes time on repeated engine initialization Confidence: high Scope-risk: narrow Directive: Preserve /ready and /cache as low-cost operational probes even if the serving stack evolves behind them Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/src/service/app.py; /usr/local/miniconda3/bin/python /tmp/test_service_readiness.py; /usr/local/miniconda3/bin/python /tmp/test_service_cache.py Not-tested: Live FastAPI HTTP serving and concurrent request behavior remain pending
Showing
3 changed files
with
136 additions
and
10 deletions
-
Please register or sign in to post a comment