Trust & methodology
Corrections
How BestAIAgent.in actually records corrections: dated changelog entries and lastReviewed updates, not a separate fictional correction log.
This site doesn't maintain a separate correction log with its own severity taxonomy and lifecycle states — that system was described on an earlier version of this page but was never actually built. The real mechanism is simpler and already public.
Where corrections actually show up
- The changelog — /changelog records real, dated releases, and carries a standing disclosure that historical entries may describe systems (like the old scoring model) that were later retired — so a reader doesn't mistake an old release note for a current capability.
- A page's own `lastReviewed` date — when an authority page's content is corrected, its
lastReviewedfield is updated as part of that same change, in the same commit. - Entity re-verification — if an evidence record turns out to be wrong, it's re-fetched and re-hashed, and the entity's evidence trail shows the new
retrievedAtdate.
How to report a suspected error
This is a source-controlled, static site (see the README's "What this is, and isn't" section) — the most direct way to report or fix an error is a GitHub issue or pull request against the public repository, following CONTRIBUTING.md.
Related methodology pages
Source receipts
- Internal —
app/changelog/page.tsx. The real, live corrections/disclosure mechanism this page points to. - Internal —
CONTRIBUTING.md. The real contribution/correction path.
Last reviewed
- Page last reviewed: 2026-09-02