Keep documentation tied to the code it describes.
Documentation stays tied to the code it explains. Echelar finds stale claims, proposes focused updates, and verifies them against the new default-branch commit after the team ships.
Documentation checked against the code it describes. Drift comes back as a pull request.
Echelar evaluates your docs against the repository at the exact commit, flags what drifted, and proposes a documentation-only pull request for a person to approve. The docs that pass are what its agents read first.
- Main changes
- Claims evaluated at the commit
- Drift flagged
- Documentation-only pull request
- Grounded at the new head
Thirty minutes with the founder. One repository, read-only, is all it needs.
Why documentation drifts
Onboarding docs describe last year's architecture
New people learn the wrong system first.
Nobody trusts the wiki, so nobody reads it
The truth lives in two heads and one Slack thread.
Docs drift the day they are written
No commit ever fails because the docs went stale.
Demonstration
Demonstration on a fictional Acme repository — authored data.
How Echelar checks documentation against the code
- The agents read the same docs
- Documentation that passed is what the Reviewer and every Session read first. Claims that fell out of date are marked stale and set aside — which is why drift is worth catching.
- Evaluated at the exact commit
- Each documented claim is checked against the repository as it is at that commit, not as it used to be — review policy, conventions, architecture boundaries, validation.
- Proposals, not edits
- When docs drift, Echelar proposes a documentation-only pull request. A person approves it like any other change.
- Grounded means the merged code passed
- The repository shows as grounded only after the new default-branch head passes evaluation. Opening a pull request earns nothing on its own.
Documentation upkeep, before and after Echelar
| Without Echelar | With Echelar | |
|---|---|---|
| How drift is found | Someone notices, eventually. Usually a new hire. | The default-branch head is evaluated against the docs that describe it. |
| Who updates the docs | Whoever notices, if anyone. | A documentation-only pull request, ready for review. |
| What up to date means | Last edited three months ago. | Checked against the code on main, as of now. |
Same job, on your repository.
Get a docs-drift report on one repositoryDocumentation drift FAQ
What is in the drift report?
Each criterion — review policy, conventions, architecture boundaries, validation, vocabulary — marked pass, fail, or unknown at the current commit, with the evidence for each, plus a proposed documentation-only pull request for what failed.
Which files count as documentation?
The sources your repository declares — typically README, ARCHITECTURE, CONTRIBUTING, ADRs, a docs folder — mapped to criteria in a small manifest. Unmapped criteria show as unknown, never as passed.
Our docs live in Notion or Confluence. Does this apply?
Start with the in-repository documentation the agents actually read. External wikis are outside the evaluation today.
What if the code changes an hour later?
The new head is evaluated again. Grounded is never carried forward.
What does it cost?
Echelar is launching now. Early teams work directly with the founder and agree pricing together.
Bring the real one.
One repository: a read-only evaluation of its documentation at the current commit, and a proposed documentation-only pull request you can take or leave.
Not ready to book? Read how access and approvals work first.