From 365f329ddc4a9efcd0eea04797b829f467ad47a3 Mon Sep 17 00:00:00 2001 From: Divya Date: Mon, 11 May 2026 15:30:47 +0530 Subject: [PATCH 1/2] docs: remove open-source client claim from how-training-works Co-Authored-By: Claude Opus 4.7 (1M context) --- join-use-case/how-training-works.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/join-use-case/how-training-works.mdx b/join-use-case/how-training-works.mdx index 5e9a59b..e3348b5 100644 --- a/join-use-case/how-training-works.mdx +++ b/join-use-case/how-training-works.mdx @@ -5,7 +5,7 @@ description: "What the tracebloc client does to your data and model in each use This page documents the training and inference pipeline that the tracebloc client runs for every supported use case. The goal is full transparency: you can read what happens step-by-step, write an equivalent script on your own machine against the same dataset, and compare metrics number-for-number against what the platform reports. -If something here does not match what you observe in your run, please [open a support ticket](mailto:support@tracebloc.io) — the source of truth is the open client code in [`tracebloc/tracebloc-client`](https://github.com/tracebloc/tracebloc-client). +If something here does not match what you observe in your run, please [open a support ticket](mailto:support@tracebloc.io) so we can investigate together. ## Shared lifecycle @@ -526,5 +526,5 @@ To validate a result you saw on the platform: -The platform code is open source at [`tracebloc/tracebloc-client`](https://github.com/tracebloc/tracebloc-client) — if a number on your end doesn't line up with what the platform reports, please [open a support ticket](mailto:support@tracebloc.io) so we can investigate together. +If a number on your end doesn't line up with what the platform reports, please [open a support ticket](mailto:support@tracebloc.io) so we can investigate together. From 7f97130bef7babcc602d803b44cdba835661fd72 Mon Sep 17 00:00:00 2001 From: Divya Date: Mon, 11 May 2026 15:33:53 +0530 Subject: [PATCH 2/2] docs: say "contact us" instead of "open a support ticket" Co-Authored-By: Claude Opus 4.7 (1M context) --- join-use-case/how-training-works.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/join-use-case/how-training-works.mdx b/join-use-case/how-training-works.mdx index e3348b5..ab0d252 100644 --- a/join-use-case/how-training-works.mdx +++ b/join-use-case/how-training-works.mdx @@ -5,7 +5,7 @@ description: "What the tracebloc client does to your data and model in each use This page documents the training and inference pipeline that the tracebloc client runs for every supported use case. The goal is full transparency: you can read what happens step-by-step, write an equivalent script on your own machine against the same dataset, and compare metrics number-for-number against what the platform reports. -If something here does not match what you observe in your run, please [open a support ticket](mailto:support@tracebloc.io) so we can investigate together. +If something here does not match what you observe in your run, please [contact us](mailto:support@tracebloc.io) so we can investigate together. ## Shared lifecycle @@ -499,7 +499,7 @@ Common reasons numbers move: - **Stateful layers.** Batch normalization's running statistics, dropout masks, and any other stochastic layer state depend on batch order and initialization, both of which are sensitive to the points above. - **Mixed precision.** If your local run uses different mixed-precision settings than the platform did, you'll see small differences from rounding alone. -If your local numbers land within a reasonable band of the platform's, the run reproduced. If they diverge by a meaningful margin, please [open a support ticket](mailto:support@tracebloc.io) — that signals a real mismatch (likely preprocessing, data-slice, or configuration drift) worth investigating together. +If your local numbers land within a reasonable band of the platform's, the run reproduced. If they diverge by a meaningful margin, please [contact us](mailto:support@tracebloc.io) — that signals a real mismatch (likely preprocessing, data-slice, or configuration drift) worth investigating together. To validate a result you saw on the platform: @@ -526,5 +526,5 @@ To validate a result you saw on the platform: -If a number on your end doesn't line up with what the platform reports, please [open a support ticket](mailto:support@tracebloc.io) so we can investigate together. +If a number on your end doesn't line up with what the platform reports, please [contact us](mailto:support@tracebloc.io) so we can investigate together.