Repository navigation
Home
Matthew Feroz edited this page Oct 14, 2026
·
6 revisions
Heval is a web workspace for comparing coding agents on the same programming tasks. The website coordinates the work; a connected Linux worker runs the evaluation. Heval collects verifier outcomes and turns them into private reports that the owner can choose to publish.
Stakeholder status reports are posted once and not edited afterward.
- October 13, 2026: End of Sprint 1, overall AMBER; prepared October 14.
- October 6, 2026: Sprint 1 week 1, overall GREEN.
- Sprint 2: October 14-27, hosted acceptance and reproducible release.
- Recovery validation: completed Sprint 1 reconnect/cancellation evidence.
- Prototypes: eleven captures of the actual public UI, a route/navigation diagram, controls, and recovery states.
- How an evaluation works: a numbered example, sequence diagram, component responsibilities, and failure behavior.
- Sprint 1: the two-week work plan, issues, completion criteria, and project board.
- Week 5 submission notes: assignment summary and Canvas-ready text.
- Solution overview: purpose, users, hosting, data boundaries, and decisions.
- Technology stack: technologies and their responsibilities.
- Architecture diagrams: context, containers, and execution sequence.
- Automation: existing CI, release checks, and evaluation automation.
| Date | Feedback or finding | Change and evidence |
|---|---|---|
| 2026-09-23 | Initial architecture baseline | Context/container diagrams and solution/stack/automation pages |
| 2026-09-30 | The author reports week 4 feedback was to explain how the system works better | Added a concrete run walkthrough and sequence diagram; identified the component responsible for each step; explained reconnects, cancellation, and private/public reports |
| 2026-09-30 | Public source advanced beyond the original baseline | Checked public revision 3567263; updated CLI version, live monitoring, configurable run resources, and CI descriptions; removed developer-specific machine details and obsolete product limits |
| 2026-09-30 | Initial drawn prototypes did not match the application's visual layout | Replaced the mockups with eleven collaborative-preview captures of the public React UI; added source links and documented simulated state and synthetic results |
The feedback above is the author's paraphrase, not a claimed quotation from the instructor. No additional week 4 comments were supplied.
Source documentation describes implementation at the linked revision. It does not prove that every deployment or installed worker runs that revision. Prototype values are illustrative, not benchmark results.