Submissions queue

Queue your lab artifacts for grading. Phase B v0 of the student-flow per the scoping memo.

Phase B v0. This surface queues your artifacts in your browser's local storage and shows them as queued (backend pending). The POST to the academy submission-api lands after the backend deploys behind portal.virtuscyberacademy.org/submission/ per the open whitebox-ops brief. Nothing leaves your browser yet. No fake grades.

Queue a new submission

How this works today. Your submission is hashed (SHA-256), a preview is stored in this browser's localStorage under the key va-submission-queue, and the row appears in the queue table below. The actual POST to the academy submission-api happens once the backend ships, the per-cohort enrollment table lands, and the JWT-mode middleware replaces the shared-secret BearerAuth.

Your queue

No submissions queued yet. Use the form above to stage your first artifact.

What is backend-gated

The student-flow scoping memo's §3 names the missing backend + infra pieces. Until they land, this surface keeps everything client-side.

I1. submission-api reverse-proxied behind portal.virtuscyberacademy.org/submission/ (whitebox-ops brief pending).
B1. per-cohort enrollment tables on submission-api (students, cohorts, cohort_enrollments, cohort_modules); memo §10 Round 1.
B2. JWT-mode auth on submission-api against the portal JWKS (replacing the shared-secret BearerAuth); memo §10 Round 1.
B3. Decision on which service owns the enrollment table (portal-api already has cohort_roles; submission-api spec calls out separate cohort_enrollments).