Evergreen
Documentation that maintains itself.
In the constellation
Evergreen highlighted in the live map — hover or tap any node to explore.
The gap
Documentation rots the moment code moves. Every engineering org pays a standing tax in stale docs, broken links, and contradictions nobody catches until they bite. “Someone should update the docs” never scales.
The reason it never gets fixed is economics: keeping docs true means re-checking them constantly — too expensive to do by hand, or with a frontier model on every change.
What Evergreen is
Evergreen is documentation that maintains itself. A persistent AI guild-person watches your sources of truth and continuously repairs the docs — references, terms, structure, and facts — so the corpus is always true.
It works because of two things almost nobody else has: an integrity engine (Anchor) that guarantees references stay valid, and a cost split that routes the constant re-checking to cheap rails, reserving expensive judgment for the few calls that need it.
What it does
Drift detection
The moment a symbol is renamed or a contract changes, Evergreen flags every doc that just went stale.
Reference repair
Broken links and moved targets are fixed automatically — in a reviewable plan — by the integrity engine.
Contradiction flagging
Surfaces places where two documents now disagree: the errors humans never catch by hand.
Provenance on every change
Each fix carries its reasoning, so trust is auditable — not magic.
The line between judgment and machinery
AccelMars draws one hard line through every product: what an AI decides, and what runs deterministically. Evergreen sits on the boundary — and keeps the two honest.
What the AI judges
- Whether a change makes a doc stale
- How to rewrite prose to match new reality
- Which contradictions actually matter
What stays deterministic
- Reference integrity — every link stays valid
- Structure & format conformance
- The audit trail of what changed
Continuous maintenance is ruinous on a frontier model and cheap on tiered rails — which is exactly why Evergreen is economical for us and uneconomical for everyone else.
Who it’s for
- Engineering orgs drowning in stale internal docs
- Teams where a wrong doc causes real incidents
- Anyone maintaining a large, fast-moving knowledge base
Planned — the flagship of the second ring, and the wedge that proves the self-maintaining loop.