nectar
- what it is
- + a memory layer for your codebase
- granularity
- + per file per symbol possible later
- how identity starts
- + minted fresh not derived
- what it serves
- + meaning-based recall
compare
nectar and aura
How does nectar compare to aura? aura is the clearest predecessor to nectar's idea of stable identity, and we credit it openly. It keeps a thread that says this is the same function, separate from a hash of what the function currently is. nectar lifts that split from functions to files and points it at memory. Close in idea, aimed at a different target, not competition.
What aura is
aura is a version-control system built around function-level identity. It separates a function's identity anchor, a persistent thread that survives renames, moves, and edits, from its content hash, which changes on every edit and links to the anchor as a version. Its own framing is that neither alone is enough: the hash makes edits comparable, the anchor makes history continuous. That is exactly the insight nectar is built on.
What nectar borrows from aura
nectar's two-part model, a stable identity plus a content hash for versions, is aura's model, and we credit it directly. The "neither alone is enough" framing is aura's, and it is the reason nectar refuses to key identity on file contents.
Where nectar is different
| nectar | aura | |
|---|---|---|
| what it is | yes. a memory layer for your codebase | partial. version control |
| granularity | yes. per file per symbol possible later | partial. per function |
| how identity starts | yes. minted fresh not derived | partial. derived from structure at first sight |
| what it serves | honeycomb advantage. meaning-based recall | partial. behavior proof and rewind |
Capability comparison, not a benchmark. From aura's public materials and our survey, captured 2026-06.
The same pattern, a different job.
aura proves and rewinds behavior. nectar recalls the right file by meaning. Minting the identity rather than deriving it trades global de-duplication for simplicity and collision-freedom, and leans on your own store's tenancy to keep things scoped. The insight is shared; the machine we built around it is not.
See how nectar worksCommon questions
What is aura?
A version-control system built around function-level identity: a persistent anchor that survives renames and moves, separate from a content hash that changes on every edit and links to the anchor as a version.
What does nectar borrow from aura?
Its two-part model, a stable identity plus a content hash for versions. We credit it directly, and it is why nectar refuses to key identity on file contents.
How is nectar different from aura?
Same identity pattern, different application. aura proves and rewinds function behavior; nectar recalls the right file by meaning, per file, with identity minted fresh.
Identity that survives your refactors.
nectar keeps recall pointed at the right file even when the tree changes. Install it with the rest of the stack.
Windows (PowerShell): irm https://get.theapiary.sh/install.ps1 | iex
Download