Support Service Status
The only support content currently available is the self-service material in this documentation section. The repository and current preview material do not identify support personnel or a channel authorized to represent a real publisher.
| Capability | Current status |
|---|---|
| Self-service FAQ, troubleshooting, diagnostics, and known issues | Factual documentation available |
| Official support email | Not opened or verified |
| Ticket portal | Not specified |
| Service status page | Not specified |
| Support scope, response targets, and escalation | Not approved |
| Version lifecycle and security-update period | Not published |
| Private channel for security reports | Not opened or verified |
How to handle a problem now
- Stop any operation that could repeat a charge, message, resource creation, or file modification.
- Use Common Problems to determine whether the cause is local configuration, permissions, a third-party service, or product behavior.
- Use Diagnostics and Logs to prepare a minimal redacted reproduction locally. Do not upload the complete data directory.
- Review Known Issues for a boundary that is not yet released or supported.
- If the installer came from a third-party organization or developer, ask only through the channel that distributor explicitly publishes. That channel does not automatically represent this project's future official publisher.
For exposed credentials or an exploitable security issue, first contain the impact using Release Security Status. Do not post the issue in a public discussion.
Gates for formal support
Before public downloads open, the real publisher must at minimum:
- publish support and security entry points on an official domain it controls;
- complete bidirectional delivery tests for the email, form, or ticket system;
- define supported platforms, versions, issue types, response targets, and the internal escalation owner;
- define minimization, redaction, access, retention, and deletion rules for diagnostic material;
- approve consistent public Support, Privacy, Vulnerability Disclosure, and version-lifecycle policies.
Until those facts exist, no claim of “official support,” “security response,” or any service level should be made.