Uh oh!
There was an error while loading. Please reload this page.
docs(rfc-0002): tracebloc data ingest — flow, terminology & task taxonomy - #174
Merged
Conversation
…nomy Draft RFC capturing the ingest-UX redesign discussed with Lukas: - Invert the flow: ask for the DATA first, sniff the family from the layout, then offer only the compatible tasks — instead of the current task-first 16-item wall shown before anything is known about the data. - Accept a flexible input path (a bare .csv for tabular/time, a directory otherwise) — today every family requires a directory, even tabular. - Never "upload/push/stage" in user copy — the data stays on the user's own infrastructure; "ingest" umbrella, "copy into your storage" for the move. Rename --category -> --task (required), --intent -> --split. - Reduce ceremony: one environment, so drop "Connect to your workspace" and the cluster/PVC fields; Kubernetes behind --verbose. - The 15 ML tasks with data-scientist-facing names + one-liners (HF / scikit-learn / Papers With Code research); the label column is task-specific (skipped for the self-supervised text tasks). - The taxonomy contract: the task list is duplicated in 5 places across 3 repos with one enforced edge; make the schema enum the single source of truth + cross-repo drift checks. - Phased delivery incl. wiring the 5 CLI-pending text tasks so the CLI matches the platform. Grounded in a code-level audit of CLI develop + the ingestor + the backend. Supersedes the copy in #173 where they conflict. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
LukasWodkaforce-pushed
the
docs/rfc-0002-data-ingest-flow
branch
from
July 7, 2026 16:34
8d077a3 to
2293a30Compare…abel column task-specific Per discussion with Lukas: settle the Phase-1 prompt order (train/test → name → path → task), make the file-or-folder mental model explicit (point at your data in whatever shape it has; the "Found ..." echo removes the confusion), and move the label column fully into the task-specific questions. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…5-task input matrix Rewrite the label section: three shapes (class/target/absent), precise per-family wording (never the ambiguous "label to predict"), and pick-from-real-headers + exact-match-or-hard-fail validation that closes the data-ingestors#340 case-mismatch silent-NULL-label bug. Add the full task-specific input matrix for all 15 tasks. New reconciliation open questions (drop vestigial --label-column for sidecar-labeled vision, forecasting timestamp gap, target_size placement, schema-for-regression). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Per Lukas: drop --label-column for sidecar-labeled vision (object detection/keypoint/segmentation); forecasting gets a first-class timestamp prompt + preflight; normalize --target-size to file_options; surface inferred schema for confirmation on the regression family. Task display names remain under review (decoupled from the wire task_id). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
saadqbal
approved these changes
Jul 8, 2026
Uh oh!
There was an error while loading. Please reload this page.
saadqbal
commented
Jul 8, 2026
Collaborator
/fr-pass |
This was referenced Jul 8, 2026
Closed
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 freeto 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.
RFC 0002 —
tracebloc data ingest: flow, terminology & task taxonomyDraft RFC (status: for discussion) capturing the ingest-UX redesign. Renders at
docs/rfcs/0002-data-ingest-flow.md.The core move: invert the flow. Today the CLI asks for the ML task first — a 16-item wall shown before it knows anything about the data — and requires a directory (never a file). The RFC proposes: ask for the data first, sniff the family from the layout, then offer only the compatible tasks. A
.csv⇒ tabular/time;images/⇒ image;texts/⇒ text.Also in scope:
--category→--task(required, hidden alias),--intent→--split,--namedefaults from the path basename.--verbose.Grounded in a code-level audit of CLI
develop+ the ingestor + the backend. Open questions are in §12; the phased delivery is §11. Please review the flow inversion (§5) and the terminology map (§6) first — those drive everything else.🤖 Generated with Claude Code