juniper-recurrence 0.1.1

FastAPI + CLI service wrapping the Δt-native LMU recurrence model on the juniper-service-core framework

juniper-recurrence

Project: Juniper — Cascade Correlation Neural Network Research Platform Application: juniper-recurrence (FastAPI + CLI service) Author: Paul Calnon License: MIT License Version: 0.1.0

FastAPI + CLI service that wraps the Δt-native Legendre Memory Unit regressor (juniper-recurrence-model) on the shared juniper-service-core framework. It loads 3-D windowed sequences (equities_seq, the WS-1 irregular-Δt contract) through juniper-data-client and trains / serves the LMU over HTTP.

This is the application layer (WS-4b): the first real consumer of service-core's create_app + TrainingLifecycle. The model, the data foundation, and the service framework ship separately; this package is the glue + the HTTP/CLI surface.

Install

pip install juniper-recurrence

All upstreams resolve from PyPI: juniper-service-core, juniper-model-core, juniper-recurrence-model, juniper-data-client, plus fastapi / uvicorn.

Run

# Serve the API (single worker, in-process state). Binds 0.0.0.0:8210 by default;
# set JUNIPER_RECURRENCE_HOST=127.0.0.1 for local-only.
juniper-recurrence serve
juniper-recurrence serve --host 127.0.0.1 --port 8210

Once running, the API exposes (every /v1/* route below requires X-API-Key when API keys are configured; health + docs are always exempt):

Route	Method	Behavior
/v1/health, /v1/health/ready	GET	Liveness / readiness (exempt).
/v1/train	POST	Train the LMU on a dataset (synchronous); returns the TrainResult.
/v1/training/status	GET	idle / trained + last metrics + training events.
/v1/predict	POST	Continuous predictions for inline X (+ dt) or a dataset ref.
/v1/model	GET	Current model topology + regression metrics.
/v1/dataset	GET	Descriptor of the trained-on dataset.
/docs	GET	OpenAPI / Swagger UI (exempt).

Training runs inline (a one-shot closed-form solve), so POST /v1/train returns the result in the response — no background jobs or WebSocket streams in v1.

# Train on a juniper-data dataset, then inspect the model.
curl -sX POST localhost:8210/v1/train \
  -H 'Content-Type: application/json' \
  -d '{"dataset": {"dataset_id": "<id>"}, "d": 16}'
curl -s localhost:8210/v1/model

Train (headless CLI)

# Fit the LMU on a dataset and persist it — no server.
juniper-recurrence train --dataset <id> --d 16 --out model.npz
juniper-recurrence train --name equities_seq_v1 --split train

Configuration

All settings read the JUNIPER_RECURRENCE_ environment namespace (e.g. JUNIPER_RECURRENCE_PORT). Secrets honor the Docker _FILE indirection (JUNIPER_RECURRENCE_API_KEYS_FILE, JUNIPER_DATA_API_KEY_FILE). When no API keys are configured, authentication is disabled (open access — development default).

Variable	Default	Purpose
JUNIPER_RECURRENCE_HOST	0.0.0.0	Bind host (container default; 127.0.0.1 locally).
JUNIPER_RECURRENCE_PORT	8210	Bind port (deploy maps host 8211 → container 8210).
JUNIPER_RECURRENCE_API_KEYS	(unset)	CSV or JSON-array of valid X-API-Key values.
JUNIPER_DATA_URL	http://localhost:8100	Upstream juniper-data base URL.
JUNIPER_DATA_API_KEY	(unset)	Outbound X-API-Key to juniper-data.

Development

pip install -e ".[test]"
pytest tests/ -v

Publishing

Releases are published to PyPI via GitHub Actions (.github/workflows/publish-recurrence-app.yml) on a juniper-recurrence-v* tag — TestPyPI first (with a --no-deps install verification), then PyPI, via OIDC trusted publishing (no API tokens). The model package (juniper-recurrence-model) publishes separately on juniper-recurrence-model-v* tags.

git tag juniper-recurrence-v0.1.0
git push origin juniper-recurrence-v0.1.0

Ecosystem

Part of the Juniper ML research platform. See the WS-4b build plan (notes/JUNIPER_RECURRENCE_WS4B_APP_BUILD_PLAN_2026-06-15.md in juniper-ml) for the design of record.