Phase 2 of 3 · Implementation

Phase 2 — Deploy, watch, and make sure the class can get in

Put the service in front of real students, watch it under load, and keep it reachable so access is a class right — not a lucky connection.

Next

What this phase is for

✓ Deploy the Phase 1 service as the student-facing path.

✓ Watch it closely enough to know it still works when several people use it.

✓ Make sure every OCS student can get access — not only the team that built the rack.

Deployment Monitoring Classroom access Shared fairness

How the work shows up

Deployment

Treat the rack as a service the school can point at — not a one-team experiment that vanishes after a demo.

Monitoring

Notice when answers stall, when memory gets tight, or when the stream drops, before a whole class feels it.

Many people at once

Classroom use is the test. The service should remain usable when several students are mid-assignment together.

Every student has a path in

Access is the impact. If some students still need a paid tool because they cannot reach OCS Intelligence LLM, the question is unfinished.

Done when

→ The live service is the one students are told to use, not a screenshot of a local run.

→ We can see whether it is healthy when more than one person is on it.

→ Getting a key and reaching the stream is a normal student step, not a favor.

Research question 2 · Secondary — only answerable once RQ1's service exists

Once the service exists, how do we keep it fair, visible, and usable when many students need it at once?

Fairness Every OCS student should be able to reach the same service, not a lucky few on the same LAN.

Load A small class wave — about five people at once — should not empty VRAM, crash the API, or drag token speed to a crawl.

Trust Deployment and monitoring prove the promise: it works as intended, and it is still there when the room fills up.

Research endpoint: Answered when ~5 concurrent users hold steady without OOM, a hard crash, or token speed falling to a crawl, and every OCS student — not just the builders — can get a key.

Priorities for this phase

P0 The live service is the one students are told to use, not a screenshot of a local run.

P0 Every OCS student can get a key — not only the team that built the rack.

P1 Dashboards or logs show whether the service is healthy when more than one person is on it.

If this phase works

A full period can share one donated brain instead of sixteen private subscriptions.

Teachers can assign AI-supported work without asking who paid this month.

OCS tracks lab and cloud operating costs against the value of shared student access.

Literature

Resource	Type	What it means
TTFT, TPS, ITL	Metrics	Time to first token, tokens per second, and inter-token latency — the numbers we track to know the service still feels fast under load.
OCS Intelligence issue #4	Tracker	GitHub issue that tracks literature, metrics, and serving goals for this project.