Neurnav
Clarifies when, where, who, how, and what was written.
Start new thread
Neurnav Developer

Neurnav - Clarifies when, where, who, how, and what was written.

by•
People often assume products like this are easy wins. They’re not. Neurnav is slow to build, slightly irrational, and powered by obsession. It’s mostly just me (and a few friends) caring way too much about document diffs, version history, and where text actually comes from. From the outside, it probably looks like a bad idea. From the inside, it’s genuinely fun. I didn’t build Neurnav to chase numbers. I built it because I love experimenting and making tools that feel right. 😈

Add a comment

Replies

Best
Neurnav Developer
Maker
📌
Hey Product Hunt 👋 I’m the maker of Neurnav. This started as a slightly unhealthy obsession with documents. Version history that lies, AI edits that erase intent, and the constant “who changed this?” problem. Neurnav is my attempt to treat documents more seriously—like experiments. It’s slow to build, not very efficient, and probably not the smartest idea. But it’s fun. And I care way too much to stop. Would love honest feedback, questions, or “why would you do this?” comments 😈 Thanks for checking it out.
Neurnav Developer
Maker

🚀 Show HN: Neurnav

Because “Did you use AI?” is the wrong question

My university professors banned AI with the laziest argument ever:

“I can't tell if you wrote it or AI did.”

Okay.

So your entire evaluation system falls apart because you can’t verify authorship?

✅ That’s not an AI problem.

❌ That’s YOUR problem.

---

What really pisses me off 😤

They act like:

AI = no thinking

…is some kind of axiom.

  • Calculator ≠ “you don’t understand math”

  • Compiler ≠ “you don’t understand code”

  • So why is AI different?

---

🔥 The real question isn’t “did you use AI?”

It’s:

  • Can you explain your reasoning?

  • Can you defend your work?

  • Do you understand what you submitted?

---

🧠 So I built Neurnav

Every edit — human or AI — gets tracked with Git-level provenance.

You can see exactly who changed what, when, and why.

No more “I don’t trust this” BS from professors who are too lazy to ask better questions.

---

Why?

I was already doing this with local Git repos for my own sanity…

…but constantly creating repos and pushing to GitHub was painful.

So I wrapped Git into a product that non-technical people can actually use.

---

🧰 Tech stack

  • Next.js 15

  • One Git repo per document

  • Branching/merging UI

  • Provenance metadata in every commit

---

If your institution is still having braindead “AI yes or no” debates,

maybe transparency is the actual answer.

### ✉️ Feedback welcome.