Strust

Developer preview / Best effort

Support starts with a safe diagnostic boundary.

Strust is not generally available. This page states what can be supported today, what must stay out of email, and how to create a redacted diagnostic before asking for help.

SUPPORT SCOPE

Public release status

No Strust package is generally available yet. The download page is the authority for promoted platforms and available packages.

Developer-preview support

General product and installation coordination is best effort. There is no public support SLA. A signed design-partner agreement may define a protected route and narrower response commitment.

Evidence stays customer-controlled

Do not email source, raw fixtures, receipts, findings, credentials, or exploit details. Request a protected transfer path before sharing sensitive material.

Redacted support bundle

Inspect before you share.

The bundle contains Strust and runtime versions plus stable doctor check ids and statuses. It omits source, fixtures, reports, commands, paths, and credentials.

SAFE DIAGNOSTICCLI
strust doctor -c strust.toml \
  --support-bundle support.json --json

Its SHA-256 detects accidental changes; it is not a publisher signature. Read the JSON yourself before sending it.

NON-SENSITIVE COORDINATION

Contact Strust without attaching customer evidence.

The general address is for non-sensitive product coordination. Its domain mail routing has not yet been published and tested, and there is no public support SLA during the developer preview.