Week 5 submission notes

Prepared September 30, 2026 for the three assignments due September 29. GitHub artifacts are dated honestly; no submission date has been backdated. All three Canvas submissions are complete. The browser connection was restored and each submission receipt and saved text was checked. Canvas marks the September 30 submissions late relative to the September 29 deadline.

UI prototypes

Completed artifact: Prototypes. Eleven captures of the actual public React UI cover Home, setup, connected computers, evaluation configuration, model selection, the run summary, live/offline monitoring, reports/sharing, and Studio. A route diagram explains navigation. Each section links to its implementing components. These replaced the initial drawn mockups after review found they did not follow Heval's layout closely enough. Only authentication and Convex responses were simulated; report data comes from the repository's synthetic demo fixture. A capture manifest records routes, source revision, and PNG hashes.

Canvas-ready confirmation:

I posted Heval's initial UI screen images and navigation diagram to the public project wiki's Prototypes page: https://github.com/MatthewFeroz/heval/wiki/Prototypes. The designs cover Home, worker setup, evaluation configuration, monitoring, reports, and Studio, with notes explaining controls and recovery states.

Architecture update

Completed artifact: How an evaluation works, with revised Solution overview, Architecture diagrams, Technology stack, Automation, and the Home review record.

The author reported that week 4 feedback was to explain how the system works better. The update adds a concrete six-trial example, numbered lifecycle with component/state ownership, submission-to-publication sequence diagram, and recovery table. It clarifies that the browser coordinates work, Convex persists/authorizes it, and an outbound Linux daemon plus detached supervisor run Harbor/Docker and upload sanitized results. It separates provisional telemetry, verifier evidence, local raw artifacts, private drafts, published revisions, and presentation exports. Public source revision 3567263 also corrects outdated version/limit/CI statements and removes developer-specific environment details.

Canvas-ready description:

I updated Heval's architecture wiki to explain how the system works more clearly, addressing the week 4 feedback. I added a concrete evaluation example, a numbered lifecycle identifying each component's responsibility, a sequence diagram, and a recovery table for browser closure, worker disconnects, delayed monitoring, and cancellation. I clarified the browser/Convex/Linux worker/Harbor boundaries, how verifier results become private reports, and how owners publish or revoke report revisions. I also refreshed stack and automation details against the current public source. The walkthrough is at https://github.com/MatthewFeroz/heval/wiki/How-an-Evaluation-Works.

Sprint planning

Completed: four detailed issues, each assigned to @MatthewFeroz and the Sprint 1 milestone, imported into a public Heval project in Todo. A separate saved Sprint 1 board filters to the milestone. The unrelated project and its views remain unchanged. Dates are September 30 through October 13; commitment is 28 hours plus 4 hours contingency.

• Issue #9: first-run workflow
• Issue #10: reconnect and cancellation
• Issue #11: private/public reports
• Issue #12: reproducibility and release evidence

Sprint plan · Milestone · Board

Automatic repository issue import is enabled with filter is:issue is:open for MatthewFeroz/heval. Removing issue #12 from the project and updating it verified automatic re-import without manual addition. All four sprint issues remain in Todo.

Canvas-ready confirmation:

I planned Heval's two-week Sprint 1 for September 30 through October 13. Four GitHub issues have detailed descriptions and completion criteria, are assigned to Matthew Feroz, and belong to the sprint milestone. I imported them into the public Heval project and created a separate Sprint 1 board filtered to that milestone, preserving other views. Automatic repository issue import is enabled. The plan is at https://github.com/MatthewFeroz/heval/wiki/Sprint-1 and the board is at https://github.com/users/MatthewFeroz/projects/2/views/2.

Canvas submission receipts

Each assignment displays Submitted. Its saved text was opened through Submission Details and verified against the intended message. Times below are exactly as Canvas displayed them.

Assignment	Canvas assignment	Receipt
UI prototypes	701029	September 30 at 6:16pm, late
Update the architecture	701030	September 30 at 6:16pm, late
Sprint planning	701026	September 30 at 6:17pm, late

The supplied assignment 701015 was the already-submitted week 4 architecture assignment. It was left unchanged. The course's October 13 status update is labeled End-of-Sprint-1, so the sprint milestone, issue descriptions, board name/filter, and wiki use Sprint 1. The former Sprint-3 wiki link remains as a pointer to the corrected plan.

Native auto-add is enabled for open issues in MatthewFeroz/heval, and automatic re-import of updated issue #12 was verified. No assignment-completion step remains pending.

Validation of the assignment artifacts

Eleven UI screenshots were captured through the collaborative browser and visually inspected. A separate navigation SVG was checked against the implemented links, rendered to PNG with the checkout's existing Sharp dependency, and visually inspected. Image hashes and local/source links were checked. Source links are pinned to public revision 3567263. GitHub queries confirmed the four issue assignees/milestones, imported Todo items, public project, and saved board layout/filter. Documentation and prototype work does not constitute a new application deployment or live evaluation test. The sprint issues remain planned work.