# Research Notes: Local-First Writing

## Question

Can a local-first Markdown workspace feel calm enough for long research sessions while still preserving standard Markdown files?

## Observations

- Writers need low-friction capture.
- Researchers need stable references.
- Developers need code snippets and tables.

> The file format should stay portable even if Sapling renders extra affordances.

## References

- [Local-first software](https://www.inkandswitch.com/local-first/)
- https://example.com/research/local-markdown

## Extract

```text
Source text remains canonical.
Rendered styling is a view over that source.
```

## Evidence Table

| Evidence | Interpretation |
| -------- | -------------- |
| Fast active-line changes | Hybrid editing remains viable |
| Dirty-line rendering | Styling can stay bounded |
| Native selection ranges | Cursor behavior stays predictable |

## Open Questions

- [ ] What is the smallest useful image milestone?
- [ ] Should tables eventually use overlay layout?
- [x] Should source remain standard Markdown?

