Know the project before you touch the code
Nebulai opens with a briefing: what the project does, how it is built, what is active, what is blocked, and what the team has learned so far.
Open on a project briefing
What it does, how it is built, what is active, what is blocked, what has been learned.
Keep what the work taught you
Evidence preserved without interrupting the task, compared against existing memory.
Follow how the work unfolded
Plenty of what decides whether work can move happens outside the repository. Nebulai keeps those events connected to it.
The project remembers after people leave
Engineers leave. Threads get buried. Sessions end. What they knew stays with the project.
Every coding session can make the project smarter
A Discovery is something learned while doing the work: hidden behaviour, technical debt, a security concern, an architectural constraint, an unexpected dependency. Nebulai captures it with evidence and files it in Project Memory.
A coding session turns up something real: an unbounded retry, a hidden coupling, a security concern.
Nebulai compares it against existing Project Memory so the same finding is not recorded twice.
Confirmed Discoveries stay attached to the work that found them, with evidence to the line.