Time-Series & Tabular Foundation Models Datasheet v1.0¶
Structured numbers are not “text with commas.” Time series have physical ordering and temporal dependence; tables contain heterogeneous features, missingness, and different symmetries. Foundation models in these domains need their own representational physics.
Related: 01_GUT_GENERATIVE_AI_UNIFIED_ENGINEERING, 09_LOCAL_AI_INFERENCE_RUNTIME_DATASHEET, 12_REWARD_VERIFIER_JUDGE_DATASHEET.
PART A — TIME-SERIES FOUNDATION MODELS¶
1. Fundamental state¶
Multivariate time series:
Unlike text:
- position corresponds to physical time;
- values carry scale and units;
- sampling interval matters;
- trend, seasonality, and regime are properties of the underlying generative process.
2. Forecasting¶
History:
Horizon:
Point forecast:
Distributional forecast:
The second formulation is preferable when multiple futures are plausible.
3. Point-wise tokenization¶
Each timestamp becomes a token/embedding:
Sequence length:
Good for fine temporal granularity; expensive for long sequences.
4. Patch tokenization¶
Patch of length \(P\):
For integer \(1\le P\le T\), non-overlapping patches, and no padding, discard any incomplete trailing patch in this example. Padding or retaining it requires an explicit mask/policy. The number of full-patch tokens is:
Trade-off:
At fixed input length, larger non-overlapping patches coarsen the token/attention grid. Packing samples into patches can preserve every sample; information loss depends on the embedding or compression. Patching alone is not equivalent to downsampling the signal.
5. Multi-scale representation¶
Real-world processes contain multiple frequency bands.
A hierarchical representation may retain:
with:
Fine scales capture spikes; coarse scales capture trends and regimes.
Zeus 2026 uses a multiscale Transformer with a U-shaped hierarchy to balance point-level fidelity against long-sequence efficiency.
6. Normalization¶
A series may undergo an affine transform:
or local/instance-wise normalization. Fit statistics using training data or the available historical window only, following the model recipe; never use the forecast target window. Normalize per feature when required. For \(\sigma=0\), define a constant-feature rule or a positive scale floor, and apply the corresponding inverse transform consistently.
This helps transfer across series with different scales, but it can erase absolute meaning when magnitude itself is semantically important.
Rule¶
not merely optional preprocessing.
7. Covariates¶
Context may include:
A real forecasting problem is closer to:
Keep separate:
- observed covariates;
- known-future covariates;
- static features.
Use temporal or rolling-origin evaluation. At each forecast origin, preprocessing, imputation, feature selection, thresholds, and calibration may use only information available by that origin. A future timestamp does not make a measured covariate known in advance: use its forecast or a genuinely preannounced value, and record availability times.
8. Deterministic forecasting¶
MSE loss:
Well suited to mean prediction under specific assumptions.
Problem: it collapses a multimodal future into an average.
9. Quantile forecasting¶
For quantile \(\tau\):
Pinball loss:
Produces quantiles such as:
The two outer quantiles define \([q_{0.1},q_{0.9}]\), a prediction interval with nominal 80% coverage; \(q_{0.5}\) is the median. Coverage must be calibrated for the target domain. Check quantile ordering/crossing and empirical coverage by horizon and regime; declare any noncrossing adjustment and fit it without access to test outcomes.
10. Probabilistic forecasting¶
A model may parameterize a distribution:
or generate samples:
Metrics must evaluate the predictive distribution, not just mean error.
11. CRPS¶
The Continuous Ranked Probability Score compares a predicted distribution against the observation.
Conceptual form:
Lower is better.
12. Autoregressive forecasting¶
Problem:
so errors can accumulate across the horizon.
13. Direct / parallel forecasting¶
Predict the full horizon at once:
This avoids autoregressive error propagation, but the model still needs some other mechanism to represent dependencies within the forecast horizon.
14. Diffusion / flow time-series forecasting¶
Treat the future as a stochastic trajectory:
or use a flow formulation:
Useful for generating ensembles of plausible futures, especially in multimodal domains.
2026 snapshot: KiT applies a Diffusion Transformer plus flow matching to future financial OHLCV trajectories.
15. Masked time-series modeling¶
Mask interval \(M\):
Varying the mask pattern can induce different tasks:
- extrapolation;
- interpolation;
- imputation;
- abstraction.
Zeus uses Multi-Objective Temporal Masking to unify these tasks without task-specific fine-tuning.
16. Imputation¶
Given mask \(m_t\):
Missingness itself may be informative:
For multivariate series, masks must identify missingness per feature, for example \(m_{td}\). Filling with zero or the mean without an explicit mask can introduce false semantics.
17. Anomaly detection¶
Possible approaches:
Reconstruction residual¶
Forecast surprise¶
Representation distance¶
The threshold depends on the operating regime and the cost of false positives.
18. Classification¶
Convert the series into a global representation:
A multi-task foundation model attempts to make \(z\) transferable across domains.
19. Regime shift¶
The data-generating process changes:
For time series, drift may appear as:
- trend shift;
- volatility shift;
- seasonality shift;
- structural break;
- sensor recalibration.
Long context does not automatically fix the presence of old, now-irrelevant regimes.
20. Frequency domain¶
Discrete transform:
This exposes periodic structure, but nonstationary processes may require time-frequency or other local methods.
Do not elevate “decomposition” into a universal requirement.
21. Failure surfaces in TSFMs¶
- frequency aliasing;
- scale mismatch;
- irregular sampling;
- covariate leakage;
- misclassified known-future features;
- regime shift;
- persistence bias;
- horizon extrapolation collapse;
- underdispersed uncertainty;
- calibration failure;
- domain-pretraining mismatch.
A 2026 study of Chronos-2 and TimesFM-2.5 reports abrupt failures on selected synthetic regime-switch patterns and, for TimesFM-2.5, energy-release patterns. The authors suggest pretraining-data composition as a possible explanation without isolating it causally. These findings are specific to the tested models and generators; “foundation” does not imply universal capability.
PART B — TABULAR FOUNDATION MODELS¶
22. Tabular state¶
Supervised dataset:
Here \(D_{features}\) is the feature count, distinct from dataset \(D\). Features may be:
- continuous;
- categorical;
- ordinal;
- timestamps;
- missing;
- strings/IDs.
There is not necessarily a natural ordering of columns.
23. Feature tokenization¶
Each cell/feature may produce an embedding:
Column identity may be injected explicitly:
This resolves part of the heterogeneity problem.
24. Permutation considerations¶
For a dataset represented as a sequence of rows, an exchangeability assumption means:
for every allowed row permutation \(\pi\). This is symmetry of the joint distribution, not independence: rows that are i.i.d. conditional on a shared latent variable can be correlated and still exchangeable. Temporal or group structure may restrict which permutations preserve the distribution; the evaluation split must respect that structure.
Columns are not semantically exchangeable unless their identities are preserved.
The architecture must distinguish:
25. Missingness¶
Define a mask:
An ideal model receives:
Missingness may be MCAR, MAR, or MNAR; the mechanism changes the inference problem.
26. Prior-data fitted networks — PFN intuition¶
A TabPFN-style model is not simply “a Transformer trained on spreadsheets.”
During pretraining, the model learns over distributions of tasks, synthetic datasets, and priors:
At inference time:
is computed in context, without optimizing new weights for each dataset.
This resembles amortized Bayesian inference / meta-learning.
27. In-context supervised learning¶
The context contains pairs:
plus query:
The model returns:
The “prompt” is the training set itself.
28. Dataset size as context budget¶
Unlike an LLM:
Growth in samples and features increases memory/attention pressure.
TabPFN-2.5 expands the operating regime to tens of thousands of rows and thousands of features, but those limits remain architecturally relevant.
29. Classification vs regression¶
Classification:
Regression:
Regression must model scale, tails, and heteroscedasticity in ways classification does not.
30. Distillation to a deployable model¶
A foundation model may act as an expensive teacher:
Distill it into a smaller model:
TabPFN-2.5 introduces a distillation path to MLP/tree ensembles, separating amortized training-time intelligence from cheap runtime execution.
31. Tabular metrics¶
Classification:
- accuracy;
- ROC-AUC;
- PR-AUC;
- log loss;
- Brier score / calibration.
Regression:
- MAE;
- RMSE;
- R²;
- NLL/CRPS when probabilistic.
Comparisons across multiple datasets need robust ranks/aggregates, not just a raw arithmetic mean.
32. Tabular failure surfaces¶
- dataset too large/wide for context;
- high-cardinality categorical explosion;
- leakage;
- feature-semantics mismatch;
- missingness-mechanism shift;
- covariate shift;
- target shift;
- calibration drift;
- extrapolation outside support;
- IDs treated as ordinal numbers;
- temporal or group dependence that breaks the assumed permutation symmetry.
33. Time series vs tabular — do not mentally collapse them¶
Time series:
Classical i.i.d. tabular learning:
Time series have a clock and a forecast horizon; supervised tabular learning has a training set/context.
That is why the two domains share this file but are not treated as the same mathematics.
34. Runtime¶
Time series¶
Primary cost:
Tabular PFN¶
Cost:
In both cases, increasing “context data” does not change model weights, but it does increase inference cost.
See 09_LOCAL_AI_INFERENCE_RUNTIME_DATASHEET.
35. SOTA snapshot — 2026¶
Zeus¶
- tuning-free multi-task TSFM;
- point-wise tokenization;
- multiscale Transformer;
- Multi-Objective Temporal Masking;
- forecasting, probabilistic forecasting, imputation, anomaly detection, classification.
TabPFN-2.5¶
- substantial expansion of dataset/feature operating regime;
- strong in-context tabular prediction;
- deployment distillation to MLP/tree ensembles.
KiT¶
- flow-matching Diffusion Transformer for future financial trajectories;
- example of a continuous generative objective applied to forecasting.
The important message: time-series and tabular foundation models are diverging architecturally, not converging toward a simplistic “LLM for numbers.”
36. TSFM checklist¶
- Point-wise or patch tokenization?
- What sampling interval?
- Is normalization part of the recipe?
- Are there known-future covariates?
- Is the forecast point, quantile, or distributional?
- Autoregressive or parallel?
- What horizon was trained/evaluated?
- How are missing and irregularly sampled values handled?
- What regime shifts are expected?
- Are forecast samples calibrated?
- What is the footprint as series length grows?
37. Tabular FM checklist¶
- How are continuous and categorical features represented?
- Is column identity explicit?
- Is a missingness mask used?
- Is inference in-context or fine-tuned?
- What are the row/feature limits?
- Does row order matter to the implementation?
- Are predicted probabilities calibrated?
- Is there a distillation path for deployment?
- How are high-cardinality categoricals handled?
- Is there leakage risk in the context?
Snapshot references¶
- Zeus: Towards Tuning-Free Foundation Model for Time Series Analysis — https://proceedings.mlr.press/v306/fu26n.html
- TabPFN-2.5 — https://arxiv.org/abs/2511.08667
- KiT: Diffusion Transformer for financial time-series forecasting — https://arxiv.org/abs/2609.34507
- Causal Analysis for Time Series Foundation Models — https://arxiv.org/abs/2608.24303