Lattice.

Obsidian meets Grasshopper, for your actual life.

Mind-maps hold structure. Parametric tools hold relationships that compute. Nothing holds both, wrapped around the real work. Lattice is that missing fusion.

Everything sits as a node on one infinite canvas. A tree gives you the spine — life, domains, projects, sections, tasks — and you navigate it top-down. But the interesting truth runs sideways: arbitrary cross-links that ignore the hierarchy and carry a formula. Change a value on one node and it ripples to whatever depends on it, the way a Grasshopper slider recomputes a design.

One canvas where structure flows and relationships compute.

Three layers on one surface

• The structural tree. Everything roots under one LIFE node and branches into domains → projects → sections → tasks. This is the spine you navigate.
• Cross-cutting relationships. Any node links to any other, ignoring the tree. A Gearbox on the mechanics side couples to a Torque parameter on the electronics side because the physics says so.
• Life-level resources. Above every project sit pools — hours per week, budget, energy — and projects draw on them through weighted relationships. Spend more here, less is left there.

Capture first, organise second

On the phone, the text field is the whole app — no “which folder?” question before you’ve even typed. You dump the thought; a local AI co-pilot reads the whole graph and proposes two or three places it might belong. Accept, pick an alternative, or leave it in the inbox. Nothing is filed silently until the model has earned that trust.

A relationship is a component, not a note

Promote a link and a panel opens: input and output pockets, an editable, unit-aware formula such as τ = (P·η)/(ω·i), sliders for the free parameters, and a solve-direction toggle that decides which endpoint is the given and which is derived. The formula sits on the wire itself, so you can read the couplings across the whole canvas at a glance.

Live and in daily use.

• Infinite desktop canvas — pan/zoom graph of node cards with breadcrumb tree-navigation and nested sub-pages.
• Phone capture PWA — installs to the home screen; single field, voice and photo attach, works offline and syncs when it reconnects.
• Nodes as first-class objects — title, notes, kind, priority chips (P0–P3), status, attachments, and free-form metadata, all in one place.
• Two edge types — structural links and formula-bearing relationships, plus cross-page portals rendered as dotted wires.
• Countdowns & trackers — nodes can count down to a deadline, or carry an external reference (order, parcel, account) with a configurable fetch policy.
• On-box AI placement — a local LLM proposes where each capture belongs and detects explicit routing intent — no external API, no per-token cost.
• One-a-day digest — completions and ETA changes surface once, in the evening, instead of a stream of pings.
• Priority inheritance — sections roll up the priority of their children so the most urgent work stays visible.
• Soft-delete everywhere — nodes, edges and attachments go to a recoverable trash; nothing is ever silently lost.
• Visual state — fresh captures pulse until seen, completed nodes soften, P0 items flag red.

Where it’s heading next.