The Iteratione Protocol

Mission Objective

Computer Science education relies heavily on file I/O and strict algorithmic logic. But local environments drift. "It works on my machine" is the most common excuse in FCIT labs. Iteratione standardizes the evaluation pipeline, acting as a deterministic pre-compiler before official grading.

System Architecture

The platform is closed-source to protect grading integrity, but operates on an open-architecture philosophy. It is designed around an asynchronous, queue-based execution model to handle concurrent student submissions safely.

• Redis-backed BullMQ handles job scheduling. This ensures the server doesn't crash the night before a deadline when 100 students hit submit simultaneously.
• Node.js spawns ephemeral, isolated Docker containers for every single code execution.
• Our engine injects hidden input.txt files via Docker bind mounts and extracts outputs for surgical diff comparisons.

Rules of Engagement

By using this platform, you are running untrusted Java code on our servers. To keep the infrastructure alive, hard limits are enforced at the Docker daemon level.

• Execution time is strictly capped at 2000ms to automatically kill infinite loops.
• Memory is hard-capped at 256MB per container process.
• Network access inside the sandbox is completely disabled to prevent outbound attacks.

Changelog