Project Grapevine uses WebMCP to connect AI agents with people, aerial drones and operational systems, turning live ground truth into coordinated disaster response while keeping humans in control.
Aggregate33.5
Leverage9
Execution7.5
Impact9
Creativity8
Each criterion 1–10, equally weighted; aggregate is their sum. Ranking is the pipeline's consolidated output.
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 76%
Leverage
8 /10
Live structured updates from people, sensors, drones, and operational systems are central to reliable coordination; generic UI driving would be too slow and brittle for shared changing state.
Evidence cited
About text describes agent coordination over live field reports, sensors, and supply logistics.
Packet lists multiple connected operational surfaces including ops center, field inbox, warehouse inventory, and partner directory.
Frame sheets and four gallery images are submitted.
Execution
7 /10
The simulation is clearly scoped and the packet describes a coherent multi-surface scenario, but the absence of transcript and inability to confirm real integrations limits certainty.
Evidence cited
Description explicitly labels it a fictional simulation.
Facts report live demo, public repository, and four gallery images.
Frame sheets show the claimed operational surfaces per packet evidence.
Impact
9 /10
Disaster responders face a high-stakes, concrete coordination problem where timely ground truth and logistics decisions have major human value.
Evidence cited
Inspiration is tied to Hurricane Helene relief logistics and changing road/bridge conditions.
Scenario connects responders, volunteers, sensors, and supply trucks while retaining human control.
Creativity
9 /10
The ambitious multi-actor disaster-response simulation is memorable and explores WebMCP as coordination infrastructure rather than a single-app assistant.
Evidence cited
Connects people, aerial drones, agents, and operational systems.
Pursues a consequential, live-ground-truth scenario across several interfaces.
Reviewer B (round 2)
confidence 66%
Leverage
8 /10
Structured shared state is central to coordinating heterogeneous disaster-response inputs and agent actions; generic UI driving would be materially less reliable, though the simulation could conceptually be built with other APIs.
Evidence cited
Pitch explicitly connects AI agents with people, aerial drones, and operational systems.
About text describes live ground truth, field inbox, warehouse inventory, and an operations center sharing state.
Execution
7 /10
The packet presents a coherent, intentionally scoped fictional simulation with multiple operational surfaces, but the supplied evidence has no transcript and the visual frame evidence was not usable for detailed verification.
Evidence cited
Public repository and live demo are reported alive.
Devpost lists multiple coordinated product surfaces and a concrete disaster scenario.
Impact
9 /10
Disaster logistics is a consequential, real problem with a clear audience of responders and relief coordinators; timely shared ground truth could create substantial value.
Evidence cited
Origin story cites Hurricane Helene logistics failures in western Appalachia.
Scenario addresses changing roads, bridges, field reports, and supply-truck routing.
Creativity
8 /10
The combination of WebMCP, human control, field reports, sensors, drones, and relief logistics is an ambitious and memorable application beyond a conventional CRUD demo.
Evidence cited
Human-agent-disaster-response framing is unusually specific.
Concept treats agents and people as contributors to a live operational network.
03 Review highlights
Standouts across reviewers
Strong human-impact scenario and multi-actor coordination model.
Treats WebMCP as shared operational infrastructure.
Explicitly fictional simulation; real-world integration and reliability are unverified.
No transcript or clear end-to-end response outcome.
Project is explicitly a fictional simulation rather than a deployed response system.
No transcript and limited directly verifiable execution evidence.
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
Contact sheets from the ?s 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
