Source-provenance and AI-authorship verification system for game engine and open-source project maintainers
A supply-chain verification runtime that traces code contributions back to human vs. AI origin, integrates into version-control gates, and certifies authorship for maintainers enforcing contribution policies.
The problem
Open-source and game-engine maintainers (Godot, Blender, Linux kernel) are blocking or requiring disclosure of AI-authored code contributions due to licensing, attribution, and quality-control concerns, but have no automated way to detect or verify authorship origin at commit time. Manual review is labor-intensive, error-prone, and creates bottlenecks for contributor onboarding.
Who has it: Open-source and game-engine maintainers and governance boards (Godot Foundation, Linux Foundation, Apache, Eclipse) managing 100+ annual contributions across 10+ core developers, facing contributor-provenance policy enforcement.
Why now: AI code generation tools (ChatGPT, Claude, Copilot) are now mainstream; maintainers face real legal, community, and governance pressure to enforce contribution policies. Platforms like GitHub lack native authorship-origin tracking. The indie-game and open-source communities (Godot's core market) are highly policy-sensitive and will adopt tooling that reduces maintainer friction while respecting contributor autonomy.
Where this came from
2 public sources behind this idea.
Unlock this idea and the whole database
Lifetime membership unlocks every idea, every execution kit, and Claude Code access.
- Every validated idea, in full
- The sources, competitors, pricing, and GTM behind each
- An execution build kit and a working demo
- Workspaces to plan and build with your team
- Co-founder matching from your saved ideas
- The full investor database (emails, stage, location)
- Claude Code access via the Eureka MCP
- New ideas added every week