OpenAI 2026 hackathon

Visual SOP Proof

GPT-5.6 turns logistics procedure footage into timestamped, evidence-bound audit assistance.

Solo project by sinichi motohasi · 0 likes · 0 comments

Archive position — measured, not model output

0 likes on Devpost

2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #7,579 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

What the company appears to be

Visual SOP Proof is a self-reported iOS application that uses GPT-5.6 and video footage to validate logistics standard operating procedures (SOPs). It processes a PDF SOP and a short inspection video, then generates timestamped evidence-based reports with Markdown/PDF exports.

What changed

The project was submitted as part of the OpenAI 2026 hackathon. The author describes it as an MVP covering one five-step logistics scenario (label confirmation, QR scan, package-damage inspection, sealing, and completion confirmation). It includes a local-key proxy, strict validation logic, deterministic replay, and offline functionality.

The single most important open question

Is there any evidence of real-world adoption or traction beyond the hackathon submission? The description does not indicate whether this has been tested in production environments or used by actual logistics teams.

Back to contents

What The Product Actually Is

The description states that Visual SOP Proof is an iOS app that accepts a PDF SOP and a 30–60 second package-inspection video. It uses GPT-5.6 to convert the procedure into observable checks, evaluates timestamped frames, and returns results for each step. The app shows supporting evidence, missing views, uncertainty, and human-review reasons, then exports Markdown and PDF reports with input hashes.

It is described as an MVP covering one five-step logistics scenario: label confirmation, QR scan, package-damage inspection, sealing, and completion confirmation.

Evidence

  • The author states that the app uses GPT-5.6.
  • It accepts a PDF SOP and a short video.
  • It returns timestamped results for each step.
  • It exports Markdown/PDF reports with input hashes.
  • It supports iOS SwiftUI, AVFoundation, PDFKit, and UIKit.

Inference The system is built to support a specific workflow in logistics inspection, using AI to bridge the gap between written SOPs and visual evidence.

Back to contents

Positioning & Claim Evolution

The author states that warehouses often have written SOPs and camera footage but the two are disconnected. Manual video review is expensive, and generic AI summaries can overstate what happened. Visual SOP Proof aims to preserve the difference between “there is no evidence in these frames” and “the worker did not perform the action.”

Evidence

  • The inspiration is described as a disconnect between written SOPs and video footage.
  • The system distinguishes between “no evidence” and “contradicted.”
  • It emphasizes honesty in evidence contracts.

Inference The positioning is to offer a more accurate, audit-ready alternative to generic AI summaries by focusing on explicit evidence and uncertainty semantics.

Back to contents

Target Customer & ICP

The description does not clearly identify the target customer or ideal customer profile (ICP). It mentions logistics inspection workflows but does not name specific industries or roles.

Evidence

  • The MVP covers one five-step logistics scenario.
  • It is built for warehouse inspection processes.

Inference It appears to be aimed at logistics or operations teams in warehouses, but no explicit customer segment is named.

Back to contents

Business Model & Pricing Evidence

There is no evidence of a business model or pricing structure in the description. The project is presented as an MVP from a hackathon submission.

Evidence

  • No mention of revenue, pricing, or monetization.
  • It is described as an MVP for a hackathon.

Inference No commercial model is evident beyond the author’s own account of building it for a competition.

Back to contents

Technical & Delivery Signals

The app uses SwiftUI, PDFKit, AVFoundation, CryptoKit, and UIKit. A Python proxy calls OpenAI Responses API with GPT-5.6 and strict JSON schemas. The model can cite only app-generated frame IDs. All returned step and frame references are validated before showing or exporting a result.

Evidence

  • Built with Swift, SwiftUI, AVFoundation, PDFKit.
  • Uses Python proxy to call OpenAI API.
  • Model uses strict JSON schema and frame ID citations.
  • Includes validation logic for all results.
  • Local-key proxy with no API secret in the app.
  • Automated iOS and proxy tests.

Inference The system is built with a focus on security, validation, and reproducibility. It includes offline capabilities and deterministic replay.

Back to contents

Traction & Maturity Signals

There is no evidence of traction or adoption beyond the hackathon submission. The project is described as an MVP and has not been tested in production environments.

Evidence

  • Submitted to OpenAI 2026 hackathon.
  • Described as MVP covering one five-step scenario.
  • No mention of customers, revenue, or usage data.

Inference No real-world traction is evident. The system is early-stage and not yet deployed in operational settings.

Back to contents

Competitive Context

The description does not provide any information about competitors or the competitive landscape. It does not reference existing tools for logistics SOP validation or AI video analysis.

Evidence

  • No mention of competitors.
  • No comparison to other tools or platforms.

Inference No competitive context is provided, and it is unclear how this solution compares to existing alternatives in the market.

Back to contents

Key Risks & Red Flags

  • Unproven commercial viability: The system is described as an MVP from a hackathon with no evidence of traction.
  • Limited scope: Only one five-step logistics scenario is covered.
  • No pricing or monetization model: No indication of how this would be sold or used commercially.
  • Self-reported validation: The author states that the system was reviewed by independent parties, but no external verification exists.

Evidence

  • MVP from a hackathon.
  • No revenue, customers, or usage data.
  • No pricing or business model described.
  • Validation is self-reported.

Inference The project has not been validated in real-world use and lacks commercial readiness.

Back to contents

Diligence Questions To Ask The Founders

  1. What specific logistics environments or industries are you targeting for deployment?
  2. How do you plan to scale beyond the single five-step scenario?
  3. Are there any plans to integrate with existing warehouse management systems (WMS)?
  4. What is your roadmap for monetization and commercial adoption?
  5. Have you conducted any user testing or feedback collection from actual warehouse workers?

Back to contents

Investment/Partnership Verdict

Not evidenced.

The description does not provide sufficient evidence of traction, revenue, customers, or a clear business model to support an investment or partnership decision. The project is described as an MVP from a hackathon and lacks any indication of real-world use or commercial viability.

Confidence Low. This analysis is based entirely on the self-reported description provided by the author. No external verification or historical data are available.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.