C10 · Week 11: Fly by instruments
Observability turned on your own project.
instrument your final project with server-side telemetry and a live dashboard, then demo it by instruments alone: no clicking through your own UI — your group uses the app, you narrate what the dashboard shows
Add the observation layer to your in-flight A3, log it server-side, put a live dashboard on it — then demo blind: your classmates poke the deployed app during the session while you present only what the telemetry shows. If the dashboard can’t tell the story of a dozen concurrent users, that’s the finding, three weeks before the showcase asks the same question at scale.
The creepy-mirror riff — showing visitors exactly what your app learned about them — is optional flavour if your project suits it. The mandated artefact is the instrumentation, which outlives the crit: it’s the observability your A3 needs anyway, and it lets you debug the app and the agent through the same telemetry.
The spec
The brief on this page poses the problem and leaves room for your response. The spec is the fixed contract: what your tutor considers when judging whether that response meets the requirements. Some lines can be checked mechanically; the rest call for human judgement.
- your final project is instrumented with server-side telemetry, deployed by the cutoff
- a live dashboard shows what the app's users are doing right now
- you demo by instruments alone: your group uses the app, you narrate what the dashboard shows — no clicking through your own UI
- the instrumentation lands in the final-project repo and outlives the crit
- the repo shows the process — commits that grew with the work, a process overview in PROCESS.md, and the week's reflection in reflections/crit-10.md
- you can account for how you directed, grounded and corrected the work