Origin, access model, eligibility, and substitution are reviewer diagnostics, not judging criteria. Authentication requirements are not penalized.
02 The two blind reviews
Two independent reviewers scored this project blind, from a sanitized evidence packet.
Scores are shown separately so the reasoning stays inspectable. A withheld score means the reviewers differed by more than two points.
Reviewer A (round 1)
confidence 90%
Leverage
9 /10
Stable block identities, render errors, equation numbering, references, comments, and surgical updates make agent collaboration materially different from copy-paste chat editing.
Evidence cited
Transcript demonstrates structured error returned with block ID and suggested fix, followed by targeted update and immediate rerender.
About text lists 15 imperative tools and a declarative form for live document structure.
Execution
9 /10
The narrated demo shows a complete, coherent core loop from seeded compile error through repair, insertion, reference resolution, and commenting, with matching UI evidence.
Evidence cited
151-second video transcript explicitly narrates error, fix, product-rule insertion, numbering, label/reference resolution, and margin comment.
Frame sheets show split source/preview editor and changing render states.
Impact
8 /10
Technical writers, students, researchers, and mathematicians face exactly the stale-snapshot and compile-error friction addressed here.
Evidence cited
About text describes copy-paste debugging workflow and live renderer catching syntax slips.
Demo uses a concrete alpha/alpa error and product-rule equation.
Creativity
8 /10
The block-identity and live-render-aware coauthoring model is a strong original interaction for technical writing.
Evidence cited
Agent edits blocks rather than replacing a document string.
Equation labels and references remain live and resolvable.
Reviewer B (round 2)
confidence 94%
Leverage
9 /10
WebMCP gives the agent precise access to live structured document state and render errors, enabling targeted repairs and insertions that are substantially safer than copy-paste or generic UI driving.
Evidence cited
Transcript shows get_render_errors identifying a typo and update_block fixing only the affected block.
Transcript shows insertion of numbered equations, labels, references, comments, and undo.
The 151-second video transcript and frames demonstrate a complete central workflow: seeded compile error, structured diagnosis, precise repair, immediate rerender, insertion with references, and agent attribution.
Evidence cited
Video transcript explicitly narrates error detection, targeted fix, successful rerender, equation numbering, labels, and references.
Frame sheets show the live editor/render workflow.
Screenshot confirms the product presentation and split workspace.
Impact
8 /10
Technical writers and mathematicians face real copy-paste and compile-debug friction; a shared live structured document directly addresses it.
Evidence cited
About text identifies stale snapshots and LaTeX syntax/compile errors as the problem.
Demonstrated workflow repairs the exact affected block and preserves existing work.
Creativity
9 /10
Treating LaTeX as a live structured document with stable block identities, render diagnostics, equation references, and agent-authored margin comments is a deep, memorable interaction model.
Evidence cited
15 imperative tools plus a declarative form expose document semantics rather than raw text.
Agent can inspect, repair, insert, reference, comment, and undo in one shared workspace.
03 Review highlights
Standouts across reviewers
Structured render-error repair loop
Stable identities preserve author control
Excellent end-to-end video evidence.
WebMCP is central to precise structured editing rather than a bolt-on.
04 Evidence
What each artifact proves is labeled on the artifact itself. A Devpost page capture is packaging evidence, not proof the product runs;
video frames are evidence from the submitted demo, not live verification.
Probe captures come from Stage 2 interactive testing of the live product by a reviewer.
EX-01 Devpost page capture · packaging evidence, not runtime proof
· sourceEX-02 Live probe at Stage 2 · observed product behavior, reviewer-drivenEX-03 Live probe after interaction · observed product behavior
EX-V Submitted demo video — “Lemma: a live LaTeX workspace co-authored with an agent.”
Contact sheets from the 151s video the team submitted. This is what reviewers were shown;
it demonstrates the product in motion but is not independent verification.
· watch the original
EX-V1 Sheet 1 of 3 · reported video evidenceEX-V2 Sheet 2 of 3 · reported video evidenceEX-V3 Sheet 3 of 3 · reported video evidence
