Understand CausetSupport policy

Support policy

This page defines how the docs use production-support labels on What runs today?. It does not describe a paid SLA unless your design-partner or Cloud agreement explicitly includes one.


Support tiers

LabelMeaning
SupportedIntended for production workloads on Managed Causet Cloud with defined compatibility expectations. Breaking changes follow the deprecation policy below.
Supported for approved customersProduction-capable on Managed Causet Cloud for approved design partners and early-access customers with direct Causet support.
Supported for pilotsSuitable for controlled pilot workloads with Causet guidance. API and behavior may change more frequently than production-core capabilities.
Community or best effortSource-available SDKs without guaranteed response times. Issues via GitHub are welcome but not contractually supported.
Not supportedEvaluation, demos, or experimental packages — do not rely on these for production.

Supported versions

ComponentSource of truthCurrent verified version
CLIGitHub releasesv10.0.12
JavaScript / TypeScript SDKnpm + sdk-status.json0.2.0
Local Docker stackinstall.causet.io/docker-compose.ymlRolling latest image tag for local dev only

Docs synchronize copies of SDK status and local runtime manifests in this repository and validate them in CI.


Compatibility

  • SDK ↔ runtime: Use the SDK version published alongside your runtime release. @causet/sdk* 0.2.x targets the current management API and runtime intent submission paths documented in the TypeScript SDK guide.
  • CLI ↔ compiler: The installer bundles or resolves a matching causet-compiler binary. causet build runs a version compatibility check before compile.
  • Local Docker: The local stack is a development/evaluation environment. Capabilities may behave identically to Cloud for integration testing, but local Docker is not production-supported even when a feature works locally.

Deprecation policy

  • Primary SDK API: submitIntent() / submitIntentStream() (and language equivalents).
  • Breaking changes: Announced in release notes and reflected in What runs today? before production-core status is claimed.
  • 0.x SDK semver: Minor releases may add features; breaking changes bump the minor while the SDK remains in supported preview.

Issue channels

ChannelUse for
GitHub Issues — causet-sdksSDK bugs and integration questions
GitHub Issues — causet-cliCLI and local runtime issues
Design-partner / Cloud supportApproved customers — contact your Causet onboarding channel
causet.ioEarly access and design-partner requests

There is no guaranteed response-time SLA for open-source or community channels unless your contract states otherwise.


Security reporting

Report security issues privately through your design-partner or Cloud contact. Do not file public GitHub issues for undisclosed vulnerabilities.


Exclusions

  • Local Docker runtime as a production deployment target
  • Experimental SDK languages (PHP/Laravel, Go) until promoted in sdk-status.json
  • Preview replay tooling (forensic replay check, recovery stream replay, repair execution) on non-sandbox forks
  • Hidden legacy runtime docs under /runtime/* — internal architecture reference, not a public support surface