Docs

Weaves — The Source of Truth

What a Weave Is

A weave is a markdown document that is your project.

Not a description of your project. Not metadata about your project. The project itself. Everything Loomline knows about a weave — its tasks, its structure, its progress — it learns by reading the markdown you wrote.

Why Markdown

Markdown is plain text with minimal ceremony. It’s portable, readable without special software, and old enough to trust. When you write in markdown, you own your words completely. No proprietary format. No lock-in. If Loomline disappeared tomorrow, your weaves would still be readable in any text editor on earth.

But more importantly: markdown has just enough structure to be useful without being prescriptive. Headings create hierarchy. Checkboxes create tasks. Blockquotes create annotations. You don’t need to learn a schema — you just write, and the structure follows.

The Document Is the Database

This is the philosophical heart of Loomline.

When you write - [ ] Design the onboarding flow inside a weave, that line becomes a thread on the board. When you check it off in the board view, the markdown updates to - [x] Design the onboarding flow. The board didn’t create a separate task object — it read your document and reflected what it found.

This means:

  • You can reorganize your project by editing text
  • You can add tasks by typing a checkbox
  • You can annotate a task by writing a blockquote beneath it
  • You can nest subtasks by indenting

The document is always the authority. Every other view is a projection.

Anatomy of a Weave

A typical weave might look like this:

# Project Name

## Why
One sentence: what this project exists to accomplish.

## Focus
- [ ] The most important thing right now
- [ ] The second most important thing
- [ ] The third (and that's the limit)

## Design
- [ ] Create wireframes
  - [ ] Mobile layout
  - [ ] Desktop layout
- [ ] Choose color palette

## Engineering
- [x] Set up repository
- [ ] Build authentication flow

## Notes
Freeform writing. Context. Decisions. Whatever doesn't fit in a task.

Every ## Heading becomes a section. Every - [ ] becomes a thread. Every indented - [ ] becomes a step within that thread. The Focus section is special — it’s where your current work lives, limited to three items to enforce prioritization.

Thread Notes

A blockquote beneath a task becomes a “thread note” — context that travels with the task across views:

- [ ] Redesign the settings page
  - [ ] Audit current settings
  - [ ] Sketch new layout
> The current settings page has too many tabs. Users report confusion
> about where to find appearance options. Consider a single scrolling view.

This note appears in the thread detail panel on the board, giving you context without leaving the view you’re working in.

Moods

Every weave carries a mood — a self-reported state that helps you be honest about where you are:

  • Focused — You know what to do and you’re doing it
  • Exploring — You’re discovering, not yet converging
  • Stuck — Something is blocking progress
  • Flowing — Everything is clicking
  • Reviewing — Looking back at what’s been done
  • Neutral — No particular state

Moods aren’t tracked or graphed. They’re a mirror, not a metric. The point is self-awareness, not optimization.