Roadmap
Jevstiller 0.1.0 is a Python library. The goal is a self-hosted proxy that speaks Jev’s API: point
TYPESAFE_BASE_URL at it and every service keeps its code and its own Jev key.
service A ─┐ ┌──────── Jevstiller (one container) ────────┐ service B ─┼─ TYPESAFE_BASE_URL ───► │ /v1/systemone → task per question │ ──► Jev service C ─┘ + own Jev key │ trained student answers, or forward to Jev │ └────────────────────────────────────────────┘Next up
Section titled “Next up”- Validate against live Jev. Replace the oracle numbers with real ones.
- Concurrency. Serve many callers per task and move training off the request path.
- Many tasks per process. Tasks keyed by their exact question, with a shared encoder.
- The proxy.
POST /v1/systemonewith Jev’s exact response shape, and pass-through for everything else. - Security. A key must be accepted by Jev before the student answers for it. Keys are never stored.
- Operations. Config file, health checks, Prometheus metrics, Docker images.
- Forward only the questions the student couldn’t answer.
- Distil Jev’s
noulandscorequestion types. - Postgres store and multiple replicas.
- Class-list changes, per-class thresholds, class-weighted budgets.
The full, checkbox-level plan is in DEPLOYMENT_PLAN.md.