---
title: Support and documentation ownership
description: Report a docs problem and follow the release checklist.
product: platform
lifecycle: stable
appliesTo: docs-site@v1
sourceArtifact: docs-maintenance@v1
owner: Sift docs
raw: /raw/platform/support.md
---

Email [hello@sift.wiki](mailto:hello@sift.wiki?subject=Docs%20feedback) with the page URL, public artifact version, expected result, actual result, and a sanitized error/request ID. Never include a token or private brain content.

## Maintainer release checklist

Authored guides explain workflows; generated JSON/Markdown owns exhaustive CLI and MCP fields. A release that changes SDK, CLI, MCP, OAuth, permission, or harness behavior must include:

1. the changed product-owned contract artifact;
2. every affected guide;
3. focused conformance evidence;
4. a docs-impact statement and lifecycle/support review;
5. approval from the interface owner and the named docs DRI.

The human DRI and backup must be recorded before any new Stable or Verified claim. Until named, “Sift docs” is only a routing placeholder and cannot approve such a promotion.