Release status
Tedix is preparing a Cloud-first open-source beta. Invited testers will use Tedix Cloud to reach a first useful result and provide feedback. Source publication is being prepared separately; no public source repository or supported self-hosted release channel has launched. Self-hosting certification and broad contribution intake are deferred, not prerequisites for this beta.
Available today
| Surface | Current availability | What that means |
|---|---|---|
| Tedix Cloud | Private beta | Existing or invited organizations can use the managed service. There is no public self-service signup claim. |
| Standalone Tedix CLI | Public beta | Checksum-verified standalone downloads are available. Using organization features still requires access to a Tedix organization. |
| OSS source repository | Private release candidate | The complete-product export, license boundary, clean install, local demo, and Cloudflare-account deployment path are being validated privately. Anonymous clone and public contribution access are not available. |
| Stable self-hosted release | Not available | No supported stable source release or self-hosted support channel has launched. Private certification evidence is preparation, not a public support promise. |
The live CLI version and immutable checksums are published through
downloads.tedix.dev. The CLI being
public does not imply that the source repository or a stable self-hosted product
release is public.
Capability truth
| Capability | Current state | Evidence boundary |
|---|---|---|
| Durable Home conversation | Available in Cloud | An existing-organization run has been observed across two turns. That proves continuity for the named run, not permanent learning or new-user onboarding. |
| Governed Work Items and approvals | Available | Risk and authority are recorded; required approval cannot come from the requester. Medium-risk work may self-admit by design, and settlement does not certify correctness. |
| Earned-delegation enforcement | Bounded rollout | The deployment switch is armed, but enforcement requires a matching active organization policy. Read route authority events before claiming a particular action was enforced. |
| Provider-backed effect evidence | Provider-dependent | Treat only an explicit provider confirmation or reference as proof of the external effect. Dispatch, a tool response, or workflow settlement alone is insufficient. |
| Accumulating context and procedure | Available, limited | Tedix persists facts, rationale, evidence, and skills. It does not yet prove that the underlying model becomes a fundamentally better reasoner for a customer. |
| Public source | In preparation | The governed export is a private release candidate. No anonymous repository is available until the separately authorized publication and access check complete. |
| Supported self-hosting | Not available | Local and own-account paths are experimental evaluation surfaces, not a stable release or support commitment. |
How the source will be published
Tedix publishes a governed export, not the development repository. The old development repository and its history stay private. Publication produces a separate public repository whose contents are built, file by file, from an allow-list.
The export tooling ships with the public source, so the mechanism is auditable by anyone who reads it:
scripts/oss/public-files.jsonis the publication policy. Its selection mode is positive includes only — named exact paths, named roots, and the resolved descendants of the published workspaces. A file that is not selected by that policy is not published; nothing is published by default and then removed.scripts/oss/export.tsbuilds the export from one source commit. It validates the public surface and third-party provenance, selects the allowed tracked files, refuses any selected file that carries a private key or points at a secret provider, rewrites each publishedwrangler.jsoncto a sanitized public base with no account, zone, or resource identifiers, regenerates the derived metadata (installation inventory, worker type definitions, license reports, release evidence) from the sanitized tree, and records the source commit plus the hash of the exact selected file set inOSS_SOURCE.json.- The result is initialized as a fresh repository with a single bootstrap
commit on
main. Development history is never published.
This is a one-time bootstrap. After cutover, public main becomes authoritative
for product code and Tedix Cloud builds identify their public revision plus
private operational configuration. Maintainers may continue direct-to-main
iteration; publication does not require a PR or stable release per change.
The export command writes into a new local directory and pushes nothing. Publishing a certified export to the public repository is a separate, manually authorized step.
Privately certified does not mean publicly released
“Certified” in these docs means Tedix’s checks for the named runtime or release scope, not independent security certification. Read the accompanying evidence and its limits.
Tedix has exercised the release candidate through isolated local startup and a sanitized export. A formerly recorded Cloudflare-account rehearsal is now superseded: the remaining live alpha Workers predate the current installation manifest and do not provide current-release proof. A fresh current-main Cloudflare deployment remains required before any self-hosted release claim. That preparation does not grant anonymous source access, create a stable release, or establish a support commitment.
Preview documentation for installation manifests and source-tree operation is published now so prospective operators can review the intended contract. Source evaluation instructions become usable when the published export makes the referenced files available. A supported self-hosted release requires its own later installation and lifecycle validation.
Source-beta launch requirements
- publication rights, accurate AGPL/Apache-2.0/MIT and trademark statements, attribution and dependency-license review for the exact source;
- a sanitized, clean-checkout-validated bootstrap, source identity and managed
build traceability to public
main; - a usable Cloud signup or invitation path and an observed first useful result;
- clear beta limitations, feedback and private security-reporting routes;
- explicit owner authorization and verification of credential-free anonymous source access after publication.
A signed stable release, fresh-account self-hosting certification and automated contributor intake are not source-beta launch requirements. Contributor terms must be finalized before accepting external code. Source access does not promise contributor availability, self-hosting support or stable compatibility.
After launch, this page will name the authoritative public repository and the Cloud beta access path. Self-hosted support will be announced separately. Until then, do not interpret an in-progress export, private candidate evidence, or these preview guides as a stable self-hosted release.