Information, against the brief
Compare the title, date, venue, and contact instructions with the approved source.
Compare an event poster with its approved brief. Bring information gaps and visual concerns into one review, with evidence people can inspect.
Browser-only walkthrough. Fixed examples, no AI analysis.
13:00 — 17:00
STUDIO 04
24 Oct on the poster. 25 Oct in the brief.
A poster can look ready while one critical detail is still wrong. RayDev’s proposed workflow brings the source, the design, and the reviewer together.
Compare the title, date, venue, and contact instructions with the approved source.
Surface readability, placement, and missing elements for a person to inspect.
Keep each concern connected to a poster region and a source requirement. People make the final decision.
Select a concern to highlight its location and compare the evidence. Switch to the revised poster to see the corresponding example edit.
The outlined area is the selected evidence region. You can also select a region directly.
View the selected findingUse the approved details below on the final poster.
Synthetic brief. All names, locations, and event details are fictional.
Local demo state only. This does not approve the poster.
Return to the posterEach sample finding carries a category, source requirement, observed content, and normalized poster region. A review flag records only your choices in this browser session.
The intended MCP-based workflow connects inputs, model-assisted checks, and evidence. It keeps final approval with the team reviewing the work.
Bring the design and its source requirements together.
Evaluate information and visual concerns with model assistance.
Return structured observations tied to the source and poster region.
Inspect the evidence, resolve concerns, and decide what is ready.
We are a five-person team in an AI education program, exploring an MCP-based review system for event posters.
Try the sample reviewA synthetic poster, approved brief, and prewritten findings demonstrate the intended review experience.
Claude use is in planning and evaluation. An actual Claude API integration has not been implemented in this demo.
Review quality and practical value still need testing. We have no verified performance metrics or paying customers to report.
No. Every finding is a fixed demonstration example authored for this fictional event. Selecting a finding or switching versions changes the browser display; it does not call a model.
This version uses only the included synthetic samples. There is no file upload, server, account, or data collection form.
No. The review buttons demonstrate local review state. Final approval belongs to a person. RayDev does not make legal infringement determinations or automatically approve a poster.