OpenAI 2026 hackathon

Mechanica — A Digital Museum of Ancient Chinese Machines

Four lost ancient Chinese machines reborn as physically-simulated, source-cited interactive exhibits — with a GPT-5.6 docent that refuses to hallucinate.

Team of 3 · 1 likes · 0 comments

Archive position — measured, not model output

1 like on Devpost

506 of the 7,856 archived projects have more likes, and 1,758 share exactly 1 — so this project's #1,425 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

Mechanica is a digital museum project that reconstructs ancient Chinese machines using historical texts and sketches, rendering them as physically-simulated, interactive 3D exhibits. The project uses AI (specifically OpenAI Codex) to build the software and integrates GPT-5.6 for a docent feature that refuses to hallucinate.

What changed

The description does not indicate any prior version or evolution of this project beyond its current form as a hackathon submission. It is presented as a one-time, self-contained build.

Single most important open question

Is there evidence of traction, revenue, or user adoption beyond the authors’ own account? The project is described as a single submission to a hackathon and lacks any indication of commercial use or market validation.

Back to contents

What The Product Actually Is

The description states that Mechanica is a digital museum of ancient Chinese machines. It builds 3D interactive exhibits from classical texts and sketches, using simulated physics rather than keyframed animation.

  • Each machine is dimensioned with versioned data and cited sources.
  • Users can interact with the machines: pull them apart, zoom in on components, and see dimensions and sources.
  • The project includes four machines:
    • Water-Powered Astronomical Clock Tower (水运仪象台)
    • Seismoscope (候风地动仪)
    • Odometer Drum Carriage (记里鼓车)
    • Pattern Loom (老官山提花机)
  • The system uses AI (Codex) to generate code and includes a GPT-5.6-powered docent that refuses to hallucinate.
  • It is built with technologies like React, Three.js, Node.js, Playwright, and serverless infrastructure.

Evidence

  • The description states the project is built using OpenAI Codex.
  • It lists specific tools used: React, Three.js, Playwright, Vercel, etc.
  • It describes how each machine is built from text and sketches.
  • It mentions a validator that checks geometry and motion cycles.
  • It includes a docent feature powered by GPT-5.6.

Inference

  • The project is a prototype or hackathon submission.
  • It uses AI-generated code, not human-written.
  • It is designed to be extensible with more machines.

Back to contents

Positioning & Claim Evolution

The description states that Mechanica aims to bring ancient machines back to life, allowing users to see them in action rather than just read about them. The project positions itself as a museum experience that uses simulation and historical data to reconstruct lost technologies.

  • It claims to be the first of its kind, using AI to build interactive 3D exhibits.
  • It emphasizes honesty in representation: no invented numbers, no keyframed animation, and a docent that refuses to hallucinate.
  • The project is described as a living exhibition stage, where machines rotate slowly under a spotlight.

Evidence

  • The tagline: “Four lost ancient Chinese machines reborn as physically-simulated, source-cited interactive exhibits — with a GPT-5.6 docent that refuses to hallucinate.”
  • The project is described as a museum of machines rebuilt from language and sketches.
  • It emphasizes the use of versioned data and citations.

Inference

  • The positioning is educational and historical.
  • It is not positioned for commercial or revenue-generating purposes.
  • It is a prototype, not a product in production.

Back to contents

Target Customer & ICP

The description does not explicitly define a target customer or ideal customer profile (ICP). However, it implies the project is aimed at educators, students, and history enthusiasts interested in ancient technology.

  • The docent feature suggests an educational use case.
  • The ability to explore machines as mechanical engineering exercises points to a STEM audience.
  • The museum format suggests a general public or classroom audience.

Evidence

  • The description mentions classroom mode for guided tours.
  • It describes the project as a way to teach about the difference between what is known and what is inferred.

Inference

  • The ICP likely includes educators, students, and museums.
  • No specific customer segments are named or described.

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 a hackathon submission with no indication of monetization.

Evidence

  • No mention of revenue, customers, or pricing.
  • The project is described as a single submission to a hackathon.

Inference

  • It is not a commercial product.
  • There is no evidence of any business model beyond the authors’ own use or educational demonstration.

Back to contents

Technical & Delivery Signals

The project uses AI (Codex) to generate code and includes a validator that checks mechanical integrity. It is built with modern web technologies like React, Three.js, and Playwright.

  • The build process involved:
    • OpenAI Codex for code generation.
    • A QA plan with 28 tasks.
    • Unit tests (267), browser scenarios (67), and a custom geometry validator.
  • It includes a poison test suite that deliberately corrupts data to ensure the validator detects failures.
  • The docent is constrained by a prompt contract and citation chips.

Evidence

  • The project was built using Codex, React, Three.js, Playwright, etc.
  • It includes unit tests, browser scenarios, and a custom validator.
  • It uses a prompt contract to prevent unsupported arithmetic or hallucinations.

Inference

  • The project is technically sophisticated for a hackathon submission.
  • It emphasizes correctness and validation in its design.

Back to contents

Traction & Maturity Signals

There is no evidence of traction, revenue, or adoption beyond the authors’ own description. The project is described as a single hackathon submission.

Evidence

  • No mention of users, customers, or market presence.
  • No data on usage, engagement, or performance.
  • It is presented as a one-time build for a hackathon.

Inference

  • The project has no demonstrated traction.
  • It is not a product in production or use by others.

Back to contents

Competitive Context

The description does not provide any information about competitors. It is unclear whether there are similar projects or platforms that attempt to reconstruct ancient machines or simulate historical technologies.

Evidence

  • No mention of competing products or platforms.
  • No reference to prior art or market analysis.

Inference

  • The project appears to be unique in its approach, but this cannot be confirmed without external data.

Back to contents

Key Risks & Red Flags

  • No commercial traction or revenue: The project is described as a hackathon submission with no indication of adoption or monetization.
  • Unproven scalability: While the system is designed to be extensible, there is no evidence it has been scaled beyond the initial four machines.
  • AI dependency: Heavy reliance on AI (Codex) for development raises questions about reproducibility and long-term maintainability.
  • Limited audience: The focus on ancient Chinese machines may limit its appeal or market size.

Evidence

  • No mention of users, customers, or revenue.
  • No evidence of product-market fit or scalability beyond the initial four machines.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the long-term vision for Mechanica beyond the hackathon submission?
  2. Are there plans to monetize or commercialize the project?
  3. How would you scale this system to include more machines or cultures?
  4. What are the limitations of using AI (Codex) for development, and how do you plan to address them?
  5. Is there any interest from museums, educators, or institutions in adopting or using this platform?
  6. How is data integrity maintained across different historical sources?

Back to contents

Investment/Partnership Verdict

Not evidenced.

There is no evidence of revenue, customers, or traction to support an investment or partnership decision. The project is described as a single hackathon submission with no indication of commercial viability or market validation.

Inference

  • This is a prototype, not a product in production.
  • No financial or commercial signals are present.
  • Any potential for investment or partnership would require further evidence of traction, scalability, and business model.

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.