docs: drop "active use case" from prereqs#65
Merged
Conversation
A use case can only be created after data has been ingested, since the platform needs the dataset's real schema and stats to define one. The prior wording sent newcomers to the web app to create a use case before they had a dataset, which is impossible. Closes #64 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2 tasks
saqlainsyed007
approved these changes
May 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A use case can only be created after data has been ingested — the platform needs the dataset's real schema and stats to define one. The prior wording sent newcomers to the web app to create a use case before they had a dataset, which is impossible. They'd get stuck before ever installing this package.
The full end-to-end quickstart that walks the corrected journey (sign up → install client → ingest → create use case → run experiments) belongs to #46 once its blockers (#44, #45, tracebloc/client#86) clear next sprint. This PR is just the one-line correction.
Closes #64
Test plan
🤖 Generated with Claude Code
Note
Low Risk
Low risk: documentation-only change that clarifies prerequisites without affecting runtime behavior.
Overview
Updates
Readme.mdprerequisites to remove the requirement that a tracebloc account have an active use case, leaving signup as the only account-related prerequisite.Reviewed by Cursor Bugbot for commit d547470. Bugbot is set up for automated code reviews on this repo. Configure here.