OpenAI 2026 hackathon

GenAI Evidence Workbench

Reconstruct AI conversation exports into reproducible evidence paths—offline, privacy-preserving, and source-text-free.

Solo project by Hiroki Tamba · 0 likes · 1 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 #4,284 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

The description states that GenAI Evidence Workbench is a self-contained, public-facing demonstration of an offline forensic workflow for AI conversation exports. The project was built as part of the OpenAI 2026 hackathon and is presented as a reproducible, privacy-preserving tool that reconstructs structured evidence paths from flat JSON archives without using live data or external models at runtime.

Key commercial signals:

  • The product is described as a "public-safe" demonstration with no upload endpoint
  • It uses synthetic data and deterministic simulation for training/evaluation purposes
  • No revenue, customers, or traction are evidenced
  • The team size is listed as one person (Hiroki Tamba)
  • The project is positioned as an educational tool for forensic workflows in AI evidence handling

The single most important open question: What is the actual commercial intent behind this public demo? Is it a prototype for a future product, a proof-of-concept for partnerships, or purely an academic/educational exercise?

Back to contents

What The Product Actually Is

The description states that GenAI Evidence Workbench presents a four-stage evidence path:

  • Acquire — lock an abstract input and establish its byte-level hash
  • Restore — preserve branches, roles, timestamps, missing values, and event classes
  • Reconcile — account for duplicates, attachment references, and candidate relationships without treating them as proof of provenance or causation
  • Report — produce a reproducible manifest, data dictionary, and audit report

The public Build Week experience uses fixed synthetic counts and abstract nodes. It contains no upload endpoint and cannot receive live evidence.

The product is described as a responsive React and TypeScript site deployed with Codex Sites that combines:

  • a narrative chapter structure
  • an accessible bilingual interface
  • a deterministic four-stage synthetic simulator
  • an original 2D forensic AI analyst and mascot
  • a public-safe explanation of the offline forensic workflow

Back to contents

Positioning & Claim Evolution

The description states that GenAI Evidence Workbench began from a practical need for an offline and reproducible way to preserve structure in AI conversation exports. It was built as part of the OpenAI 2026 hackathon.

The project positions itself as:

  • A tool for reconstructing structured evidence paths from flat JSON archives
  • An offline, privacy-preserving solution that works without live data or external models
  • A reproducible workflow for forensic analysis of AI conversations
  • A public-safe demonstration that avoids revealing proprietary extraction logic

The claim evolution shows a progression from technical problem-solving (preserving structure in conversation exports) to product positioning (public-safe forensic workflow) to educational tooling (teaching workflow through fictional examples).

Back to contents

Target Customer & ICP

Not evidenced. The description does not identify specific target customers or ideal customer profiles.

Back to contents

Business Model & Pricing Evidence

Not evidenced. No information is provided about pricing, revenue streams, or business model.

Back to contents

Technical & Delivery Signals

The description states that the public experience is built with:

  • React and TypeScript
  • Codex Sites for deployment
  • GPT-5.6 through Codex for development assistance (not called at runtime)
  • ffmpeg, aiimage, text-to-speech, vinext technologies
  • A deterministic four-stage synthetic simulator
  • A bilingual interface

Key technical signals:

  • The system is deliberately separated into public and private components
  • No live evidence is sent to external models or vendors
  • The system uses byte-level hashing for input locking
  • The system preserves branches, roles, timestamps, missing values, and event classes
  • The system handles duplicates and attachment references without treating them as proof of causation

Back to contents

Traction & Maturity Signals

Not evidenced. No revenue, customer adoption, or traction data is provided beyond the author's own account.

Back to contents

Competitive Context

Not evidenced. No information is provided about competitors or market positioning.

Back to contents

Key Risks & Red Flags

  • The project is described as a public demo with no upload endpoint and no live evidence processing
  • The team size is listed as one person (Hiroki Tamba)
  • The system uses synthetic data rather than real-world inputs, which may limit its practical utility
  • The description states that the private production method remains offline and outside this submission
  • No vendor partnerships or endorsements are claimed
  • The project appears to be a prototype for a future product rather than a commercial offering

Back to contents

Diligence Questions To Ask The Founders

  1. What is the actual commercial intent behind this public demo? Is it a prototype for a future product, a proof-of-concept for partnerships, or purely an academic/educational exercise?
  2. What specific forensic workflows does this tool address in practice?
  3. How does the synthetic simulation translate to real-world use cases?
  4. What are the planned next steps beyond the controlled evaluation using synthetic exports?
  5. What is the timeline and roadmap for transitioning from this demo to a commercial product?
  6. Are there any existing partnerships or vendor relationships that will be leveraged in the future?

Back to contents

Investment/Partnership Verdict

Not evidenced. No information is provided about funding rounds, valuations, headcount, or investment status beyond the author's own account.

The description states that this project was submitted to the OpenAI 2026 hackathon and that the underlying private forensic workbench predates Build Week. The team size is listed as one person (Hiroki Tamba). No revenue, customers, or traction data are available beyond what the author states.

This appears to be a prototype demonstration rather than a commercial product. The project's positioning as a public-safe educational tool with no live data processing suggests it may be an early-stage concept or proof-of-concept for future development.

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.