#Docs Maintenance Policy

Clients update on their own schedules; interfaces and options change constantly. This page explains how we keep integration docs current, and how to report outdated content.

#Last verified

Client integration docs are governed by their "last verified" status: on that date someone walked through the doc end-to-end in the real client, confirming steps and screenshots match reality.

The "last updated" stamp in the footer is a different thing — it comes from Git commit time and refreshes even for a typo fix. To judge whether content keeps up with client versions, look at verification.

#Verification cycle

The target is at least one verification every 30 days. Each pass checks:

Major client releases trigger early verification without waiting for the cycle.

#Scope

The policy applies to the Agents and ChatBot integration docs.

Billing, error codes and API endpoint docs are outside the cycle — they track ByteSeek platform changes and are updated in step.

#Reporting outdated content

If a doc no longer matches reality, contact in-site support, or submit an issue following the Troubleshooting template. Please include the client version — the same doc can behave completely differently across versions.

#Related

• Quickstart — choose a client integration
• Troubleshooting — locate problems by symptom