NodemancyDocsMapLibraryCards

Documentation

How lenses, nodes and links work, and every way to get content in and out of one.

All 25 pages are written. The set is complete as an outline — which is not the same as finished. If something you needed isn't here, or a page says one thing and the app does another, that is worth knowing.

Start here

What this app is, and the shortest path to something on the canvas that is yours.

The three things everything else is made of, and why a lens carries a vocabulary that a folder cannot.

Four ways content gets in, and which one to reach for first.

Every new account gets its own copy of four example macro lenses. It is yours to edit, rename or delete.

The workshops

Three rooms that read a text you paste, with no account and no model. The one part of this you can try before you own anything.

WritingConcept

What the two rooms find, why neither calls a model, and the one place that method measurably runs out.

Getting content in

Every way nodes arrive, what each costs, and what happens to them once they land.

Download your lens as a skill, hand it to any model you already pay for, and paste what comes back. Free.

The metered lane: have the app call a model for you, either to write new nodes or to connect ones you have.

Exactly what Import accepts: the frontmatter keys it reads, the link syntax, and what it silently drops.

Why model-written content arrives grey, what clears it, and why the app asks who wrote something.

Shaping a lens

The taxonomy: how nodes get organised, coloured, and connected.

Create the categories a lens sorts its nodes into, and nest them into families when there are too many.

Plain links say 'connected'. Typed links make a claim — and a wrong one looks like data.

Build a guided path through a lens, then walk it one stop at a time.

Studying

Turning a graph into recall.

Generate cards from your nodes and review them on a spaced schedule.

Your data

Where it lives, who can see it, and how to get it out.

Private, friends, or public — plus named invites, and the node-level restriction that overrides all of them.

Keep a copy of your notes as markdown on your own machine, and choose which side wins.

ThemesHow-to

Pick a shipped palette or build and name your own.

A complete export whenever you want, and a deletion that is immediate and cannot be undone.

Hosted AI is off by default, restricted nodes never reach a model, and the one thing that deliberately crosses the line.

Until you set one, nobody can find or visit your palace — and nothing says so.

When something looks wrong

Symptoms you might arrive with. Each names the cause rather than only the fix, because most of these are silent.

Almost always a slug that was reconstructed from a name instead of copied. The failure is silent by design.

Undeclared groups, unknown kinds, stripped dates, and skipped duplicates — what each one means.

The metered lane needs a paid plan and hosted AI switched on. The free lane needs neither.

The palace is read-only: a lapsed subscription freezes writing and nothing else. Reading, reviewing and a full export all keep working, and free here means self-hosting rather than lapsed.

Grey and round means a model wrote it and you haven't read it yet. Opening it settles it.

It has other lenses inside it, which makes it a macro lens. Macro lenses hold lenses, not nodes.

Positions are remembered per browser, not per account — and layout is presentation, never your data.