RFC-0002 §8.1. Collect + confirm the data schema for all four tabular/time tasks (not silent inference).
The column-type schema is required by the contract and load-bearing downstream (DB types, per-column validation, and the model's num_feature_points at training). Today the CLI silently infers it, and inference has real gaps (leading-zero code 007→7; dates/booleans→text; 5,000-row sample cap).
- Infer a proposal, then show the
column:TYPE map for the user to confirm or amend — never a silent guess. Surface the risky cases (id-like INT, empty-in-sample columns). Keep flag/CI working with an explicit acknowledgement.
Design-of-record: RFC-0002 (#174). Part of the data-ingest redesign epic.
RFC-0002 §8.1. Collect + confirm the data schema for all four tabular/time tasks (not silent inference).
The column-type schema is required by the contract and load-bearing downstream (DB types, per-column validation, and the model's
num_feature_pointsat training). Today the CLI silently infers it, and inference has real gaps (leading-zero code007→7; dates/booleans→text; 5,000-row sample cap).column:TYPEmap for the user to confirm or amend — never a silent guess. Surface the risky cases (id-like INT, empty-in-sample columns). Keep flag/CI working with an explicit acknowledgement.Design-of-record: RFC-0002 (#174). Part of the data-ingest redesign epic.