Arc

The workaround was teaching us something

While teaching and developing educational material, I kept seeing the same quiet tax: instructors searching for the right version, rebuilding something that already existed, or beginning a lesson without the context left by the previous session. That observation is my account of the problem; it is not presented as a measured adoption study.

A shared folder looks like the obvious fix. But a folder can tell you where a file is, not whether it is current, how it belongs in a lesson, what happened when it met a classroom, or what should change next.

One loop, not another library

Arc now spans reusable activities and content packs, lesson composition, live classroom release, versioned student submissions, instructor review, revision requests, analytics and operational administration.

The useful abstraction is the loop underneath those features: content becomes a lesson; a lesson becomes an activity; activity produces work; review changes the next version. The portfolio reconstructs that loop instead of publishing private product screens or listing every feature.

Working across the seams

Arc was co-developed with another engineer. The repository shows substantial work from both contributors, so the case is deliberately explicit about that boundary.

My dated contributions cross layers: replacing loosely shaped controller data with typed view models, decomposing oversized portal controllers, restructuring application services, correcting authorization wiring and password handling, moving realtime behavior toward WebSocket-first delivery, building test and CI coverage, and making a collaborative flowchart work with touch and pointer input.

That breadth is the point of the case. I was not moving between unrelated subjects; I was following the same classroom workflow through every technical boundary it crossed.

Quality is part of the classroom workflow

The audited repository contains substantial automated test infrastructure. Authored browser tests explicitly exercise phone-sized layouts, both language directions and high zoom. That is evidence of deliberate validation work, not a claim that every test passes today or that every physical device is covered.

The production lesson is simpler: a classroom interaction that works only with a mouse, only left-to-right, or only on a developer laptop is not partially finished. It is a broken teaching tool.

Live, private, and still moving

Arc has a reachable public portal and active deployment configuration. The branch audited for this portfolio is ahead of the shared development branch, so I do not claim that every inspected feature is already running in production.

The product also contains real classroom and learner material. None of that is portfolio content. Names, submissions, recordings, uploads and operational records remain private; the artifact shown here is rebuilt from source structure with deliberately fictional data.