# Swimm — tools that shaped CodeVetter

> Canonical page: https://codevetter.com/inspiration/swimm

Documentation is more useful when it remains connected to code.

## What we admire

Swimm’s code-coupled documentation addresses a familiar problem: prose that was once correct slowly drifts away from the implementation. Keeping a document near the source it explains makes that drift easier to notice.

## The principle that stayed

A useful explanation needs both a stable narrative and a checkable source reference. Generated knowledge should expose stale links rather than silently sounding current.

## Where CodeVetter stands

CodeVetter’s canonical docs live in the repo; Repo Unpack cites a pinned commit and source paths. We do not use Swimm or claim automatic documentation maintenance.

## Sources

- [Swimm on code-coupled docs](https://swimm.io/blog/advanced-documentation-editor-how-to-create-code-coupled-docs-in-seconds) — the creator's own source
- [CodeVetter codebase-context research](https://github.com/Codevetter/codevetter/blob/main/docs/knowledge/codebase-context-tools-landscape.md) — the CodeVetter project record

This is independent appreciation, not endorsement, partnership, code reuse, or feature parity.

## Public product links

- [CodeVetter](https://codevetter.com/)
- [Download](https://codevetter.com/download)
- [Documentation](https://codevetter.com/docs/)
- [Source](https://github.com/Codevetter/codevetter)