Docs

The Architecture of Calm

Why Calm Matters

Productivity software has a noise problem. Badges demand attention. Notifications interrupt flow. Dashboards visualize anxiety. The implicit message is: you’re behind, and here’s a chart to prove it.

Loomline rejects this entirely.

There are no notifications. No badges (except the system-level ones macOS requires). No daily summaries, weekly reviews, or “you completed 7 tasks this week!” celebrations. No streak counters. No productivity scores.

The app opens. Your work is there. You do the work. You close the app. That’s it.

Information Architecture

Loomline’s information hierarchy is deliberately shallow:

Workspace
  └── Weave
        └── Section (## Heading)
              └── Thread (- [ ] Task)
                    └── Step (  - [ ] Subtask)
                          └── Note (> Blockquote)

Six levels. No folders within folders. No nested projects. No sub-workspaces. The hierarchy is deep enough to organize real work and shallow enough to navigate without getting lost.

This flatness is a feature. Deep hierarchies create organizational overhead — you spend time deciding where things go instead of doing the things. Loomline’s structure is: pick a workspace, pick a weave, start working.

Data Persistence

All data lives on your device. Your weaves are yours, stored locally, accessible offline, and as private as your hard drive. iCloud Sync is available to keep your weaves in sync across your Mac and iPad, but it is handled entirely by Apple’s infrastructure — we never operate sync servers or access your synced data.

This is a philosophical choice as much as a technical one. Building custom cloud sync introduces complexity (conflict resolution, offline states, sync indicators, accounts) that adds cognitive load. By using iCloud, sync stays invisible and your files remain plain markdown — portable, readable, and yours.

The Absence of AI

Loomline includes an “AI Actions” panel in the toolbar. This is a surface for potential AI-assisted writing features — summarization, expansion, tone adjustment. But the panel is a container, not a dependency. The app works completely without it.

The philosophical position: AI should be a tool you reach for, not an ambient presence. It shouldn’t suggest, autocomplete, or reorganize without being asked. Your weave is your thinking, and thinking shouldn’t be outsourced by default.

What the App Doesn’t Do

Loomline deliberately doesn’t:

  • Track time — Time tracking changes the relationship between you and your work. It makes you a resource to be optimized rather than a person doing meaningful things.
  • Set reminders — If you need to be reminded to work on something, maybe you don’t actually want to work on it. Loomline trusts you to open it when you’re ready.
  • Generate reports — Your weave is the report. Read it.
  • Integrate with other tools — Every integration is a dependency, and dependencies break. Loomline is self-contained by design.
  • Gamify anything — Points, badges, and streaks are manipulation dressed as motivation. Your work is its own reward, or it isn’t.

The Sound of Silence

Open Loomline. Notice what’s not happening. No loading spinners. No “syncing…” indicators. No “What would you like to do today?” prompts. No tips of the day.

The app is quiet because your mind shouldn’t have to be loud to use it.

This silence is the most carefully designed feature in the entire application. Every element that was considered and rejected — every notification, every dashboard, every social feature — contributes to the calm you experience by its absence.

The best tool is the one you forget you’re using.