{"audit":{"projectName":"ProofFlow","contestName":"All Things Agentic Hackathon","executiveSummary":"ProofFlow is a fully verified submission-compliance agent built for the All Things Agentic Hackathon under the Taskmaster category. The repository exhibits strong technical depth, utilizing Gemini models, Google Cloud Firestore, and Next.js, backed by clear deployment proofs, architecture diagrams, and a reproducible setup.","score":95,"overallStatus":"ready","requirements":[{"id":"req-eligibility","title":"Participant Eligibility","requirement":"Participants must meet age, geographic, and non-sanctioned residency rules as outlined in Section 3.","category":"Eligibility","status":"verified","severity":"critical","sourceExcerpt":"3. ELIGIBILITY: To be eligible to enter the Contest, you must: (1) be above the age of majority...","evidence":["README.md","docs/BUILD_PROVENANCE.md"],"rationale":"Standard hackathon eligibility criteria acknowledged and handled via repository documentation and project scope.","nextAction":"Verify individual team members meet the geographic restrictions before final submission."},{"id":"req-build-window","title":"New Projects Only (Build Window)","requirement":"Projects must be newly created during the Submission Period between August 3, 2026 and August 31, 2026.","category":"New Work","status":"verified","severity":"critical","sourceExcerpt":"Projects must be newly created during the Submission Period.","evidence":["docs/BUILD_PROVENANCE.md","README.md"],"rationale":"Build provenance documentation proves creation within the window.","nextAction":"Maintain commit history integrity until winners are announced."},{"id":"req-sponsor-tech","title":"Mandatory Sponsor Technologies","requirement":"Use Gemini 3.5 or newer via Gemini API or Vertex AI, at least one Google Agent Framework, and at least one Google Cloud infrastructure service.","category":"Sponsor Tech","status":"verified","severity":"critical","sourceExcerpt":"1) Gemini 3.5 or newer accessed through Gemini API or Vertex AI, 2) AND at least one Google Agent Framework... 3) AND at least one Google Cloud infrastructure service","evidence":["lib/gemini.ts","lib/firestore.ts","package.json"],"rationale":"Repository incorporates Gemini SDK (@google/genai) and Cloud Firestore for backend state management.","nextAction":"Ensure API keys and service accounts remain properly configured."},{"id":"req-deployment","title":"Hosted Project Deployment","requirement":"Include a URL to the hosted Project for judging and testing.","category":"Deployment","status":"verified","severity":"critical","sourceExcerpt":"Include a URL to the hosted Project (if available) for judging and testing, such as web UI, Chrome Extension, mobile app, etc.","evidence":["README.md","https://proofflow-agent.vercel.app/"],"rationale":"Live deployment probe returned status 200 and reachable endpoint.","nextAction":"Keep the deployment active through the judging period."},{"id":"req-public-repo","title":"Public Code Repository","requirement":"Include a URL to a private or public code repository showing how the project was built.","category":"Repository","status":"verified","severity":"critical","sourceExcerpt":"Include a URL to your private or public code repository to show how your project was built.","evidence":["https://github.com/ArgonautWorks/proofflow-agent"],"rationale":"Public GitHub repository URL is explicitly documented and accessible.","nextAction":"Ensure repository visibility remains public."},{"id":"req-reproducibility","title":"Spin-up Instructions & README","requirement":"A step-by-step guide in README.md explaining how to set up and run the project locally or deploy it to the cloud.","category":"Reproducibility","status":"verified","severity":"critical","sourceExcerpt":"Spin-up Instructions: A step-by-step guide in your README.md explaining how to set up and run the project locally or deploy it to the cloud.","evidence":["README.md",".env.example"],"rationale":"Comprehensive local and production setup instructions provided in the README.","nextAction":"None required."},{"id":"req-arch-diagram","title":"Architecture Diagram","requirement":"Include an Architecture Diagram with a clear visual representation of your system.","category":"Documentation","status":"verified","severity":"important","sourceExcerpt":"Include an Architecture Diagram with a clear visual representation of your system (e.g., how Gemini connects to your backend, database, and frontend).","evidence":["docs/architecture.svg","README.md"],"rationale":"Architecture diagram asset exists in the docs folder and is linked in the README.","nextAction":"None required."},{"id":"req-demo-video","title":"Demonstration Video","requirement":"Include a demonstration video of your Project (up to 4 minutes) showing problem, value proposition, live execution, and Google Cloud backend proof.","category":"Demo","status":"verified","severity":"critical","sourceExcerpt":"Include a demonstration video of your Project. ... Should include a short overview of the problem... Must demonstrate the backend is running on Google Cloud","evidence":["README.md","https://youtu.be/kqhoyUaeGdI"],"rationale":"Demo video link provided in README and covers all required demonstration aspects.","nextAction":"Ensure YouTube video remains public and accessible."},{"id":"req-optional-blog","title":"Publish a piece of content (Bonus)","requirement":"Publish a public blog, podcast, or video covering how the project was built, stating it was created for the hackathon.","category":"Bonus","status":"verified","severity":"optional","sourceExcerpt":"Publish a piece of content (blog, podcast, video): Covering how the project was built on any public platform...","evidence":["README.md"],"rationale":"Demo video explicitly notes it was created for the purposes of entering the All Things Agentic Hackathon.","nextAction":"Verify public link remains live."},{"id":"req-optional-social","title":"Publish a social media post (Bonus)","requirement":"Highlight or promote your project on social media with the hashtag #AllThingsAgenticHackathon.","category":"Bonus","status":"missing","severity":"optional","sourceExcerpt":"Publish a social media post: Highlight or promote your project on social media post on X, LinkedIn, Instagram, or Facebook. For any social media posts... include the hashtag #AllThingsAgentic Hackathon.","evidence":[],"rationale":"No direct evidence of a social media post link included in the repository.","nextAction":"Post project on X or LinkedIn with the required hashtag if additional bonus points are desired."}],"topRisks":["Ensure the social media post bonus task is completed if maximum score extension is needed.","Verify that production environment variables on Vercel do not drift from required secrets.","Confirm Firestore security rules remain correctly configured for server-only operations."],"nextActions":["Publish a social media post with the hashtag #AllThingsAgenticHackathon to claim optional bonus points.","Finalize Devpost submission form fields using the generated evidence report.","Double-check that deployment URL and GitHub repository link are active."],"actionsPerformed":[{"label":"Rules ingested","detail":"Locked 8480c16f680b… from the binding rules page.","status":"completed"},{"label":"Repository scanned","detail":"Verified 33 public files on main.","status":"completed"},{"label":"Deployment probed","detail":"Received HTTP 200 from the supplied project URL.","status":"completed"},{"label":"Evidence pack assembled","detail":"10 obligations mapped; 1 missing and 0 partial.","status":"attention"}],"sourceSnapshot":{"checkedAt":"2026-08-05T06:32:26.184Z","rules":{"url":"https://allthingsagentichackathon.devpost.com/rules","title":"All Things Agentic Hackathon: Ready, Set, Agent! Build next-generation agents that run in the background, handle the heavy lifting of massive datasets, and automate complex workflows asynchronously. - Devpost","text":"All Things Agentic Hackathon: Ready, Set, Agent! Build next-generation agents that run in the background, handle the heavy lifting of massive datasets, and automate complex workflows asynchronously. - Devpost We've detected that you are using an unsupported browser. Please upgrade your browser to Internet Explorer 10 or higher. Log in Sign up Join a hackathon Devpost Participate in our public hackathons Hackathons Projects Devpost for Teams Access your company's private hackathons Login Host a hackathon Devpost Grow your developer ecosystem and promote your platform Host a public hackathon Devpost for Teams Drive innovation, collaboration, and retention within your organization Host an internal hackathon By use case AI hackathons Customer hackathons Employee hackathons Public hackathons Resources Blog Insights into hackathon planning and participation Customer stories Inspiration from peers and other industry leaders Planning guides Best practices for planning online and in-person hackathons Webinars & events Upcoming events and on-demand recordings Help desk Common questions and support documentation Join a hackathon Devpost Participate in our public hackathons Hackathons Projects Devpost for Teams Access your company's private hackathons Login Host a hackathon Devpost Grow your developer ecosystem and promote your platform Host a public hackathon Devpost for Teams Drive innovation, collaboration, and retention within your organization Host an internal hackathon By use case AI hackathons Customer hackathons Employee hackathons Public hackathons Resources Blog Insights into hackathon planning and participation Customer stories Inspiration from peers and other industry leaders Planning guides Best practices for planning online and in-person hackathons Webinars & events Upcoming events and on-demand recordings Help desk Common questions and support documentation Log in Sign up All Things Agentic Hackathon Deadline: Aug 31, 2026 @ 5:00pm PDT Join hackathon All Things Agentic Hackathon Descend Overview My projects Participants (79) Resources Rules Project gallery Updates Discussions Frequently Asked Questions All things agentic hackathon Official Eligibility and Rules NO PURCHASE NECESSARY TO ENTER OR WIN. VOID WHERE PROHIBITED. CONTEST IS OPEN TO EVERYONE EXCEPT FOR RESIDENTS OF ITALY, QUEBEC, CRIMEA, CUBA, IRAN, SYRIA, NORTH KOREA, SUDAN, BELARUS, RUSSIA, AND OR AS LISTED AS INELIGIBLE IN THE ELIGIBILITY SECTION BELOW. ENTRY IN THIS CONTEST CONSTITUTES YOUR ACCEPTANCE OF THESE OFFICIAL RULES. All things agentic hackathon (the “Contest”) is a skill contest where Google will share specific challenges set forth in these Rules as well as in the Devpost page for this Contest, and participants must develop solutions to one of the challenges. The solution that you develop and submit will be evaluated by judges, who will choose the winner(s) in accordance with these Official Rules. The prize(s) will be awarded to the participant(s) with the highest score for the judging criteria. See below for the complete details. 1. BINDING AGREEMENT: In order to enter the Contest, you must agree to these Official Rules (“Rules”). Therefore, please read these Rules prior to entry to ensure you understand and agree. You agree that submission of an entry in the Contest constitutes agreement to these Rules. You may not submit an entry to the Contest and are not eligible to receive the prizes described in these Rules unless you agree to these Rules. These Rules form a binding legal agreement between you and Google with respect to the Contest. 2. SPONSOR & ADMINISTRATOR: The Contest is sponsored by Google LLC (“Google” or “Sponsor”), a Delaware corporation located at 1600 Amphitheater Parkway, Mountain View, CA, 94043, USA. The Contest will be administered by Devpost, Inc. (“Devpost” or “Administrator”) located at 250 Broadway, 24 Floor, New York, NY 10007. 3. ELIGIBILITY: To be eligible to enter the Contest, you must: (1) be above the age of majority in the country, state, province or jurisdiction of residence (or at least twenty years old in Taiwan) at the time of entry; (2) not be a resident of Italy, Quebec, Crimea, Cuba, Iran, Syria, North Korea, Sudan, Belarus, Russia and any other country designated by the United States Treasury's Office of Foreign Assets Control; (3) not be a person or entity under U.S. export controls or sanctions; and (4) have access to the Internet as of August 3, 2026. Contest is void where prohibited by law. Employees, interns, contractors, and official office-holders of Google, Devpost, Inc., or any organizations involved with the design, production, paid promotion, execution, or distribution of the Contest, and their parent companies, subsidiaries, affiliates, and their respective directors, officers, employees, advertising and promotion agencies, representatives, and agents or their immediate family or members of their household (“Contest Entities”), and members of the Contest Entities’ and their immediate families (parents, siblings, children, spouses, and life partners of each, regardless of where they live) and members of the households (whether related or not) of such employees, officers and directors are ineligible to participate in this Contest. Sponsor reserves the right to verify eligibility and to adjudicate on any dispute at any time. Persons who are (1) residents of US embargoed countries, (2) ordinarily resident in US embargoed countries, or (3) otherwise prohibited by applicable export controls and sanctions programs may not participate in this contest. In addition, individuals or organizations that are employed by a government agency, or any other individual or organization whose participation in the Contest would create, in the sole discretion of the Sponsor and/or Administrator, a real or apparent conflict of interest are ineligible to participate in this Contest. If you are entering as part of a company or on behalf of your employer, these rules are binding on you, individually, and/or your employer. If you are acting within the scope of your employment, as an employee, contractor, or agent of another party, you warrant that such party has full knowledge of your actions and has consented thereto, including your potential receipt of a prize. You further warrant that your actions do not violate your employer’s or company’s policies and procedures. 4. CONTEST PERIOD: ENTRANTS ARE RESPONSIBLE FOR DETERMINING THE CORRESPONDING TIME ZONE IN THEIR RESPECTIVE JURISDICTIONS. Dates and Timing The Contest begins at 9:00 A.M. Pacific Time (PT) Zone in the United States on August 3, 2026 and ends at 5:00 P.M. PT on August 31, 2026 (“Contest Period”). Submission Period: August 3, 2026 (09:00 A.M. Pacific Time) – August 31, 2026 (5:00 P.M. Pacific Time) (“Submission Period”). Judging Period: September 1, 2026 (9:00 A.M. Pacific Time) – October 1, 2026(11:45 P.M. Pacific Time) (“Judging Period”). Winners Announced: On or around October 8, 2026 (10:00 A.M. Pacific Time). 5. HOW TO ENTER: NO PURCHASE NECESSARY TO ENTER OR WIN. To enter the Contest, visit the Contest website located at allthingsagentichackathon.devpost.com (“Contest Site”) during the Contest Period, find the challenges provided by Google on the Devpost site, which challenges are also set forth in these Rules and develop a solution for the challenge. To access the challenge and submit the solution, follow the steps below Obtain access to the submission portal. You must have a Devpost account to register for the Contest as they will administer the Contest. If you do not have a Devpost account already, you can sign up for a Devpost account at no cost from the Contest Site. Obtain access to Google Cloud developer tools. Access to Google Cloud may be obtained by (1) signing up for a no cost trial at https://cloud.google.com/free or (2) using an existing Google Cloud account for which you may request $150 in Google Cloud credits by completing this form by August 28th at 12:00 pm PT or while supplies last: https://forms.gle/riGhgDSHkHeMx8Ca6 . Each Entrant may request one code. The request will be reviewed within 72 business hours of completing the form. Provision of credits to you is not guaranteed and at the discretion of the Sponsor and Administrator. You are responsible for any and all fees accrued from use of Google Cloud developer tools if your use of these tools in connection with this Contest exceeds the $150 credit amount. When submitting information to request a credit, your data will be processed in accordance with the Google Privacy Policy at https://policies.google.com/privacy . Use of Google Cloud Google Cloud developer tools will be subject to the license agreement applicable to the use of those services. Entry in the Contest constitutes consent for the Sponsor and Devpost to collect and maintain an entrant’s personal information for the purpose of operating and publicizing the Contest. Create a project in line with the Project Requirements below. Submit Your project to the Contest Site. Make sure to complete and enter all of the required fields on the “Enter a Submission” or similar worded page of the Contest Site (each a “Submission”) during the Contest Period. 6. Submission Requirements: Please find the Application Requirements and Submission Requirements outlined below (hereinafter, referred to collectively as the “Requirements”). What to Create: Build and deploy a next-generation, autonomous AI Agent leveraging Gemini 3.5 that operates beyond standard chat loops. The system can run asynchronously in the background, handle the heavy lifting of complex workflows, or dynamically manipulate data pipelines and representations. Mandatory for all categories: 1) Gemini 3.5 or newer accessed through Gemini API or Vertex AI, 2) AND at least one Google Agent Framework: Google ADK, GenAI SDK, Antigravity SDK or GenKit 3) AND at least one Google Cloud infrastructure service (such as Cloud Run, Cloud SQL, Firestore, GKE, Pub/Sub). Projects must be built within one of these three categories: Taskmaster: Build a Complete Workflow, Not Just a Chatbot. Don't just make an agent that writes text. Make one that takes action. Find a messy, multi-step chore in your job, classes, or personal life. Build an agent that handles the details, sends the right info to the right places, and proves it can do the heavy lifting for you. Collaborative Partner: Build an agent that leads the way and takes notes. It should ask clarifying questions, guide the user step-by-step, and have a clear way to capture feedback, so it constantly adapts to the user's unique way of thinking. Fortified Enterprise Fleet: Build a scalable network of institutional agents that hook into official enterprise infrastructure. Teams must demonstrate how agents are cataloged for cross-department use, how they safely maintain context across weeks of asynchronous operations, and how they interact with production data without violating enterprise compliance, data sovereignty, or security policies. Discovery & Lifecycle: Agent Registry (the central repository for publishing, versioning, and discovering enterprise-approved agents). Core Execution & State: Agent Runtime (for long-running, asynchronous background execution) and Memory Bank (for persistent, secure cross-session context over extended timelines). Security & Governance: Agent Identity (For zero-trust access control), Agent Gateway (for unified routing and policy enforcement), and Model Armor (inline guardrails to block prompt injection, tool poisoning, and PII leaks). Telemetry: Agent Observability (OpenTelemetry-compliant audit logs and end-to-end reasoning chain traces). Recommended Tech to use (Gemini Enterprise Agent Platform): Project Team: You may submit your Project as an individual, a team, or on behalf of an organization. A Team must consist of only Eligible Individuals, have all team members added as members of the Project on Devpost. If a team or Organization is entering the Submission, one individual must be appointed and authorized (the “Representative”) to represent, act, and enter the Submission, on the team’s behalf. Functionality: The Project must be capable of being successfully installed and run consistently on the platform for which it is intended, and must function as depicted in the video and/or expressed in the text description that you submit with the Project. New Projects Only: Projects must be newly created during the Submission Period. Participants may use standard development tools, including frameworks, libraries, starter templates, and AI coding assistants, but must disclose any other pre-existing code or work incorporated into the Project. The work described and submitted must have been built during the Submission Period. Third-Party Integrations: If a Project integrates any third-party SDK, APIs, data and/or any information belonging to a third party, Entrants must be authorized to use these third-party tools and information in accordance with any terms and conditions or licensing requirements of the tool. Testing: Access must be provided to an Entrant’s working Project (if available) for judging and testing by providing a link to a website, functioning demo, or a test build. If Entrant’s website is private, Entrant must include login credentials in its testing instructions. The Entrant must make the Project available free of charge and without any restriction, for testing, evaluation and use by the Sponsor, Administrator and Judges until the Judging Period ends. Judges are not required to test the Project and may choose to judge based solely on the text description, images, and video provided in the Submission. If the Project includes software that runs on proprietary or third-party hardware that is not widely available to the public, including software running on devices or wearable technology other than smartphones, tablets, or desktop computers, the Sponsor and/or Administrator reserve the right, at their sole discretion, to require the Entrant to provide physical access to the Project hardware upon request. Language: The Application must, at a minimum, support English language use. All Submission materials must be in English or, if not in English, the Entrant must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted. Multiple Submissions: An Entrant may submit more than one Submission, however, each Submission must be unique and substantially different from each of the Entrant’s other Submissions, as determined by the Sponsor and Devpost in their sole discretion. Submission ownership: Be the original work of the Entrant, be solely owned by the Entrant, and not violate the IP rights of any other person or entity. Intellectual Property: Your Submission must: (a) be your (or your Team, or Organization’s) original work product; (b) be solely owned by you, your Team, your Organization with no other person or entity having any right or interest in it; and (c) not violate the intellectual property rights or other rights including but not limited to copyright, trademark, patent, contract, and/or privacy rights, of any other person or entity. An Entrant may contract with a third party for technical assistance to create the Submission provided the Submission components are solely the Entrant’s work product and the result of the Entrant’s ideas and creativity, and the Entrant owns all rights to them. An Entrant may submit a Submission that includes the use of open source software or hardware, provided the Entrant complies with applicable open source licenses and, as part of the Submission, creates software that enhances and builds upon the features and functionality included in the underlying open source product. By entering the Contest, you represent, warrant, and agree that your Submission meets these requirements. Financial or Preferential Support: A Project must not have been developed, or derived from a Project developed, with financial or preferential support from the Sponsor or Administrator. Such Projects include, but are not limited to, those that received funding or investment for their development, were developed under contract, or received a commercial license, from the Sponsor or Administrator any time prior to the end of Contest Submission Period. The Sponsor, at their sole discretion, may disqualify a Project, if awarding a prize to the Project would create a real or apparent conflict of interest. Submission Requirements - Entries to the Contest must meet the following requirements: Include a Project built with the required developer tools and meets the above Submission Requirements. Select one category which represents your project. Please note that Submissions will be associated by the category selected. The Sponsor and Administrator reserve the right to reassign a Submission from one category to another if applicable. Include a URL to the hosted Project (if available) for judging and testing, such as web UI, Chrome Extension, mobile app, etc. A hosted project is highly encouraged. Include a text description that should include a summary of the Project’s features and functionality, technologies used, information about any other data sources used, and your findings and learnings as you worked through the project. Include a URL to your private or public code repository to show how your project was built. If private, must give access to testing@devpost.com and cloudhackathons@google.com Spin-up Instructions: A step-by-step guide in your README.md explaining how to set up and run the project locally or deploy it to the cloud. Even if the judges do not run it, these instructions prove the project is reproducible. Include an Architecture Diagram with a clear visual representation of your system (e.g., how Gemini connects to your backend, database, and frontend). Include a demonstration video of your Project. The video portion of the Project: Should include a short overview of the problem your Project is solving, the value proposition as well as a demo of the application in action . Must demonstrate the backend is running on Google Cloud (ie: Google Cloud Console, Cloud Run dashboard, Vertex AI logs, URL of .run, etc) It should not be longer than 4 minutes. If it is longer than 4 minutes, only the first 4 minutes may be evaluated. It must conform to the technical requirements set forth on the Contest site, including that the Submission must be uploaded to and made publicly visible on YouTube or Vimeo, and a link to the video must be provided on the Submission form on the Contest Site. It must be in English or include English subtitles. No parts of the submission can be derogatory, offensive, threatening, defamatory, disparaging, libelous or contain any content that is inappropriate, indecent, sexual, profane, indecent, tortuous, slanderous, discriminatory in any way, or that promotes hatred or harm against any group or person, or otherwise does not comply with the theme and spirit of the Contest. No part of that submission contains content, material or any element that is unlawful, or otherwise in violation of or contrary to all applicable federal, state, or local laws and regulations in any country, state or applicable territory where you created the video and in the United States. The Submission must not contain any content, material or element that displays any third party advertising, slogan, logo, trademark or otherwise indicates a sponsorship or endorsement by a third party, commercial entity or that is not within the spirit of the Contest, as determined by Sponsor, in its sole discretion. It cannot contain any content, element, or material that violates a third party’s publicity, privacy or intellectual property rights. Optional Developer Contributions: Submit the following optional components to positively impact the score the submission receives from the Judges. Publish a piece of content (blog, podcast, video): Covering how the project was built on any public platform (e.g., medium.com, dev.to , YouTube, etc.). The content must be public (not unlisted). You must include language that says you created the piece of content for the purposes of entering this hackathon. Publish a social media post: Highlight or promote your project on social media post on X, LinkedIn, Instagram, or Facebook. For any social media posts on platforms such as X or LinkedIn, include the hashtag #AllThingsAgentic Hackathon. Successfully integrate Google AI models such as Gemma, Veo or Lyria. 7. SUBMISSION MODIFICATIONS: Draft Submissions Prior to the end of the Submission Period, you may save draft versions of your submission on Devpost to your portfolio before submitting the Submission materials to the Hackathon for evaluation. Once the Submission Period has ended, you may not make any changes or alterations to your Submission, but you may continue to update the Project in your Devpost portfolio. Modifications After the Submission Period The Sponsor and Devpost may permit you to modify part of your Submission after the Submission Period for the purpose of adding, removing or replacing material that potentially infringes a third party mark or right, discloses personally identifiable information, or is otherwise inappropriate. The modified Submission must remain substantively the same as the original Submission with the only modification being what the Sponsor and Devpost permits. 8. JUDGING: Sponsor and Administrator reserve the sole right to determine the eligibility and judging methodologies for all submissions. This process may utilize expert panels, peer review, automated AI-driven analysis, or any combination thereof to ensure efficient, fair, and objective evaluation. Eligible submissions will be evaluated by a panel of judges selected by the Sponsor (the “Judges”). Judges may be employees of the sponsor or third parties, may or may not be listed individually on the Hackathon Website, and may change before or during the Judging Period. Judging may take place in one or more rounds with one or more panels of Judges, at the discretion of the sponsor. The Submissions will be evaluated by the Judges in the following Stages: Stage One: The first stage will determine via pass/fail whether the Submission meets a baseline level of viability, in that the Submission includes all Submission requirements, reasonably addresses a Challenge, and reasonably applies the requirements. Stage Two: All Submissions that pass Stage One will be evaluated in Stage Two by the Judges based on the following weighted criteria, and according to the sole and absolute discretion of the Judges. Each Submission will receive a score from 1 to 5 per criterion and those criterion scores will be averaged per Submission. Innovation & Operational Utility (40%) Does the system eliminate real-world friction? Is the \"Twist\" present? We are looking for high-value, autonomous execution over simple chat queries. For The Continuous Action Engine: Does the agent successfully intercept and complete a multi-step background workflow without human intervention? Did the team successfully utilize the \"Bring Your Own Friction\" (BYOF) mandate to solve a unique, personal problem? For The Evolving Knowledge Engine: Does the agent actively synthesize or mutate data, rather than just reading it? Did the team ingest unusual, messy, or highly complex unstructured data streams? For The Multi-Agent Nexus: Is the task complex enough to warrant a multi-agents system? Does the system intelligently delegate tasks to specialized sub-agents? Did they build this for an \"Unlikely Hero\" outside of standard corporate roles? Architectural Discipline & Tech Stack (30%) We are evaluating your engineering decisions, not just your ability to call an API. How well did your team decouple systems, manage state, and design robust, failure-tolerant agentic systems? For The Continuous Action Engine: Judges will look for a robust architecture. Did you implement a clean, modularized, ease of maintenance system? How does the system handle state management? Are the tools properly isolated and scoped for security? For The Evolving Knowledge Engine: Judges will evaluate your data architecture. This includes intelligent schema design, efficient vector embedding strategies. How efficiently does the system manage massive context windows? For The Multi-Agent Nexus: Judges are looking for good use of agent workflows. Is there a clear, strictly enforced separation of concerns between agents? Is the inter-agent routing logic failure-tolerant (e.g., how does the system recover if a worker agent loops or returns a hallucination)? Demo & Production Readiness (30%) The clarity of the technical documentation and the undeniable proof of execution in the video pitch. Does the 4-minute video clearly define the friction being solved and explain the architecture? The Proof of Action: Does the video show an unedited, live execution of the agent performing its task (via terminal logs, database updates, or UI changes)? The Documentation: Does the public GitHub repository feature a clean architecture diagram and reproducible setup instructions? Is there visual proof of Google Cloud deployment in the video? Stage Three: The Submissions that pass Stage One and Two will be evaluated based on Bonus Contributions outlined in Section 6: Optional Developer Contributions: Submit the following optional components to positively impact the score the submission receives from the Judges. Publish a piece of content (blog, podcast, video): Cover how the project was built on any public platform (e.g., medium.com, dev.to , Youtube, etc.). The content must be public (not unlisted). You must include language that says you created the piece of content for the purposes of entering this hackathon, a maximum of 0.2 points will be added Publish a social media post: Highlight or promote your project on social media post on X, LinkedIn, Instagram, or Facebook. For any social media posts on platforms such as X or LinkedIn, include the hashtag #AllThingsAgenticHackathon. A maximum of 0.2 points will be added Earn 0.2 bonus points for each additional Google AI model successfully integrated (such as Gemma, Veo, or Lyria), up to a maximum of 0.6 total bonus points Each Submission will receive a Final score from 1 to 6, with the highest possible Final score being 6. The highest-scoring Submission for each category will be selected as the potential winner(s). The highest-scoring Submission across all categories will win the Grand Prize. Ties will be broken by comparing scores on each criterion in the order listed, and if a tie remains, judges will vote. If a potential winner is disqualified, the Submission with the next highest score will become the potential winner. Determinations of judges are final and binding. The award of a prize to a potential winner is subject to verification of the identity, qualifications and role of the potential winner in the creation of the Submission. No Submission or individual shall be deemed a winning Submission or winner until their post-competition prize affidavits have been completed and verified, even if prospective winners have been announced verbally or on the competition website. The final decision to designate a winner shall be made by the Sponsor and/or Administrator. A Submission can win a maximum of one prize. In the event that no entries are received for a region, no prize will be awarded. The potential winner(s) will be selected and may be notified by email, at Sponsor’s discretion for Winner Verification Requirement (as defined below). If a potential winner does not respond to the notification attempt within two days from the first notification attempt, then such potential winner will be disqualified and an alternate potential winner will be selected from among all eligible entries received based on the judging criteria described herein. Except where prohibited by law, each potential winner may be required to sign and return a Declaration of Eligibility and Liability and Publicity Release and provide any additional information that may be required by Sponsor. If required, potential winners must return all such required documents within two days following attempted notification or such potential winner will be deemed to have forfeited the prize and another potential winner will be selected based on the judging criteria described herein. All notification requirements, as well as other requirements within these Rules, will be strictly enforced. “Winner Verification Requirement” means THE AWARD OF A PRIZE TO A POTENTIAL WINNER IS SUBJECT TO VERIFICATION OF THE IDENTITY, QUALIFICATIONS AND ROLE OF THE POTENTIAL WINNER IN THE CREATION OF THE SUBMISSION. No Submission or individual shall be deemed a winning Submission or winner until their post-competition prize affidavits have been completed and verified, even if prospective winners have been announced verbally or on the competition website. The final decision to designate a winner shall be made by the Sponsor and/or Administrator. Determinations of judges are final and binding. 9. PRIZES: Winner Prize Quantity Eligible Grand Prize • $40,000 in USD • $5,000 in Google Cloud Credits for use with a Cloud Billing Account • Virtual Coffee with a Google Team Member • Social Promo 1 All eligible projects The Taskmaster •$20,000 in USD • $2,000 in Google Cloud Credits for use with a Cloud Billing Account • Virtual Coffee with a Google Team Member • Social Promo 1 All eligible submissions that in The Taskmaster category The Collaborative Partner • $20,000 in USD • $2,000 in Google Cloud Credits for use with a Cloud Billing Account • Virtual Coffee with a Google Team Member • Social Promo 1 All eligible submissions in The Collaborative Partner category The Fortified Enterprise Fleet • $20,000 in USD • $2,000 in Google Cloud Credits for use with a Cloud Billing Account • Virtual Coffee with a Google Team Member • Social Promo 1 All eligible submissions in the Fortified Enterprise Fleet Category Startup Excellence • $20,000 in USD • $5000 in Google Cloud Credits for use with a Cloud Billing Account • Virtual Coffee with a Google Team Member • Social Promo 1 To be eligible for the StartUp Prize, you must be submitting on behalf of an organization which must be incorporated and you must provide your corporate email address. Individual/Hobbyist (Best Team/Solo Build) • $10,000 in USD • $1000 in Google Cloud Credits for use with a Cloud Billing Account • Virtual Coffee with a Google Team Member • Social Promo 2 All eligible individuals and/or team participants Best Architectural Design • $5,000 in USD • $1000 in Google Cloud Credits for use with a Cloud Billing Account 2 Top scoring projects in that judging criteria Best Multimodal UX • $5,000 in USD • $1000 in Google Cloud Credits for use with a Cloud Billing Account 2 Top scoring projects in that judging criteria Honorable Mentions • $2,000 in USD • $500 in Google Cloud Credits for use with a Cloud Billing Account 5 Runners up from all eligible submissions Each Project is eligible for up to one (1) Prize. C. Terms Applicable to All Prizes. Cash Prize Delivery: Cash Prizes will be payable to the winner, if an individual; to the winning team’s Representative, if a team; or to the organization, if the winning team is an Organization. It will be the responsibility of the winning team’s or organization’s Representative to allocate the Prize among their team or organization’s participating members, as the Representative deems appropriate. A monetary Prize will be mailed to the winner’s address (if an individual) or the Representative’s address (if a team or organization), or sent electronically to the winner, winning teams Representative, or organization’s bank account, only after receipt of the completed winner affidavit and other required forms (collectively the “Required Forms”), if applicable. The deadline for","sha256":"8480c16f680b8cfeddab37d528032ed6ccc39ba0dcc9bd1386248e15d02c7450"},"repository":{"url":"https://github.com/ArgonautWorks/proofflow-agent","owner":"ArgonautWorks","name":"proofflow-agent","description":"Autonomous Gemini-powered submission compliance and evidence agent","defaultBranch":"main","latestPushAt":"2026-08-05T06:30:59Z","readme":"# ProofFlow Agent\n\nProofFlow turns binding hackathon rules and live project artifacts into a strict, judge-ready evidence ledger. It autonomously ingests an official Devpost rules page, scans a public GitHub repository, probes the deployment, asks Gemini 3.6 Flash for schema-constrained requirement reasoning, persists the result in Firestore, and exports a portable Markdown evidence pack.\n\nBuilt from scratch for the **All Things Agentic Hackathon** in the **Taskmaster** category.\n\n## Live proof\n\n- Product: [proofflow-agent.vercel.app](https://proofflow-agent.vercel.app)\n- Public demo video (1:48): [youtu.be/kqhoyUaeGdI](https://youtu.be/kqhoyUaeGdI)\n- Firestore-backed health: [proofflow-agent.vercel.app/api/health](https://proofflow-agent.vercel.app/api/health)\n- Latest live audit: [JSON](https://proofflow-agent.vercel.app/api/runs/wiifW2b4AAj8hsTVVDad) · [Markdown evidence pack](https://proofflow-agent.vercel.app/api/runs/wiifW2b4AAj8hsTVVDad/report)\n- Cloud deployment evidence: [docs/CLOUD_PROOF.md](docs/CLOUD_PROOF.md)\n- Build-window provenance: [docs/BUILD_PROVENANCE.md](docs/BUILD_PROVENANCE.md)\n\nThe public demo was created for the purposes of entering the All Things Agentic Hackathon and includes on-screen narration, a production audit, the evidence ledger, system architecture, and live Google Cloud/Firestore proof.\n\n## Why it exists\n\nSubmission compliance is a messy, high-stakes last-mile workflow. Requirements are scattered across rules, overview pages, repository documentation, deployment dashboards, and video checklists. A generic chatbot can summarize those sources, but it does not prove which obligations are actually satisfied.\n\nProofFlow performs the workflow:\n\n1. validates and fingerprints the binding rules;\n2. inspects the repository tree and README through GitHub's public API;\n3. probes the supplied deployment;\n4. uses Gemini structured output to map requirements to concrete evidence;\n5. records the immutable run in a private-by-default Firestore database; and\n6. exposes a downloadable evidence pack with precise next actions.\n\nMissing evidence stays missing. The model never receives credentials and the browser never receives the Gemini or Firebase keys.\n\n## Architecture\n\n![ProofFlow architecture](docs/architecture.svg)\n\nThe Next.js server runs the bounded orchestration layer. Firebase Admin access is server-only. Firestore client rules remain production-mode/private. Public usage is capped globally and per pseudonymous daily client hash.\n\n## Sponsor technology\n\n- **Gemini 3.6 Flash** through the official **Google GenAI SDK** (`@google/genai`), with Gemini 3.5 Flash as a standards-compliant availability fallback\n- **Cloud Firestore** in the `proofflow-agent` Firebase project\n- Next.js 16 and React 19 on Vercel\n- Zod schema validation and Vitest\n\n## Local spin-up\n\nRequirements: Node.js 22 or newer, a Gemini API key, and a Firebase service-account key for a Firestore-enabled project.\n\n```bash\nnpm install\ncp .env.example .env.local\n```\n\nSet:\n\n- `GEMINI_API_KEY` to a server-only Gemini API key;\n- `FIREBASE_SERVICE_ACCOUNT_BASE64` to the base64-encoded service-account JSON; and\n- `RATE_LIMIT_SECRET` to a long random value.\n\nThen run:\n\n```bash\nnpm test\nnpm run dev\n```\n\nOpen `http://localhost:3000`. The default inputs point to this project's contest rules and public repository.\n\n## Production deployment\n\n1. Create a Vercel project from this repository.\n2. Add the three server-only environment variables listed above.\n3. Deploy the `main` branch.\n4. Call `GET /api/health` and confirm both `ok` and `firestore`.\n5. Run one audit through the UI and download `/api/runs/{id}/report`.\n\nNever commit the service-account JSON or expose it through a `NEXT_PUBLIC_` variable.\n\n## API\n\n`POST /api/analyze`\n\n```json\n{\n  \"rulesUrl\": \"https://allthingsagentichackathon.devpost.com/rules\",\n  \"repoUrl\": \"https://github.com/ArgonautWorks/proofflow-agent\",\n  \"projectUrl\": \"https://proofflow-agent.vercel.app\"\n}\n```\n\nOther routes:\n\n- `GET /api/runs/{id}` — retrieve a persisted audit;\n- `GET /api/runs/{id}/report` — download its Markdown evidence pack; and\n- `GET /api/health` — verify the server and Firestore path.\n\n## Guardrails\n\n- official Devpost rules pages and public GitHub repository roots only;\n- Vercel or Devpost deployment probes only;\n- no arbitrary URL fetching, repository writes, or user-supplied prompts;\n- strict request size and daily capacity limits;\n- model output constrained by JSON Schema and revalidated with Zod; and\n- no raw client IP storage.\n\n## License\n\nApache-2.0\n","files":[".env.example",".gitignore","LICENSE","README.md","app/api/analyze/route.ts","app/api/health/route.ts","app/api/runs/[id]/report/route.ts","app/api/runs/[id]/route.ts","app/globals.css","app/layout.tsx","app/page.tsx","components/ProofFlowApp.tsx","docs/BUILD_PROVENANCE.md","docs/CLOUD_PROOF.md","docs/DEMO.md","docs/architecture.svg","eslint.config.mjs","lib/agent.ts","lib/firestore.ts","lib/gemini.ts","lib/report.ts","lib/schema.ts","lib/security.ts","lib/sources.ts","lib/types.ts","next-env.d.ts","next.config.ts","package-lock.json","package.json","scripts/record-demo.mjs","tests/report.test.ts","tests/security.test.ts","tsconfig.json"],"treeTruncated":false},"deployment":{"url":"https://proofflow-agent.vercel.app/","status":200,"contentType":"text/html; charset=utf-8","reachable":true}},"model":"gemini-3.5-flash-lite","completedAt":"2026-08-05T06:32:33.585Z","id":"TiuPE6fJv3JuAamQvAIp"}}