vøiddo on devpost · updated 2026-05-14
three active builds for cash-prize hackathons. each carries a public app or a public repo, screenshots, a demo, and an honest scope. judging happens on the work, not the pitch.
01 active builds
each card links to the local proof page (screenshots, demo, audit notes) and to the hackathon overview on devpost.com.
a no-code message coach built end-to-end inside medo. paste a thread, get a calmer rewrite, see the rule. tells lite carries the public app, support page, and demo reel.
a defensive incident agent that refuses unsupported claims. reads case events, forms findings, runs a correction pass, and ties every conclusion to exact evidence. precision and recall stay visible.
a launch-readiness agent for the hour before shipping. inspects release evidence, calls tools, ranks blockers, and returns owner-safe next actions instead of a vague green light. if a required mcp is blocked, the report says blocked.
02 how this surface works
each linked project carries a runnable slice or a public proof page before the devpost submission goes in. no mocks, no fake demos, no invented metrics.
scope rule
each entry on this page maps to an active hackathon with a confirmed deadline and a confirmed prize. when one closes, we move it to a results page — we do not retroactively claim wins.
media
screenshots and demo videos are produced from real runs, not mockups. when a clip is a scripted browser capture rather than a narrated demo, the page says so on the same surface.
cross-link
this hub also lives one click from /reddit/ (our devvit apps surface), the root portal, and the per-project proof pages above.
future builds
scout output is tracked locally and seeded into this board as new active hackathons close in on a deadline. splunk agentic ops, devnetwork ai/ml, eazo, and others are queued but not surfaced until a working slice exists.