Where we stand
Compliance verdict against the Best Apps & Agents track. The stamp mirrors Verdikt's real product output: one word, four meta fields, no ambiguity.
The submission window opened 2026-08-26. Everything under src/pap_pipeline/ lands after that date; everything under src/docgen/ predates it. That split is mechanically provable (see the boundary tests on the Code board).
All five submission rules are met: the repo is public with an MIT license, the demo is live at https://verdikt.aismith.ai, and the video is published on YouTube.
Against the four criteria
The Devpost rubric, verbatim, with Verdikt's answer under each. This is the page the judges came here to read.
Every topic, one click away
Rules, architecture, reuse split, checklist, timeline, open items: each behind its own tab. Pick one to inspect.
Five rules, one card each
Every rule from the Devpost brief mapped to a card. Click one to see the how and the evidence (file paths, tests, or docs that back the claim).
AI-in, deterministic-out
Prior work vs submission-window work
The hackathon rules allow reuse. They require honesty about the split. Verdikt's is mechanical: two packages, one-way dependency, boundary tests enforce direction.
Submission tasks
What has to be true on 2026-10-30 for the Devpost submission to be complete. Green rows are done; amber rows are planned with a date.
Submission-window log
Dated events from window-open to submission-close.
Submission status
Submitted on Devpost on 2026-10-18. Anything still open would be listed here with a why-blocked and a plan.