PRECOG

Predictive Configuration & Trainability Engine

Vision document · scientific specification · research roadmap

Reproduce CI status MIT License Python 3.10+
Contents

0Methodological disclaimer

All numerical values cited in this document (Recall@10 ≥ 90%, Spearman ρ ≥ 0.90, compute reduction ≥ 70%, data reduction, prediction error ≤ 5–10%, etc.) are experimental targets to be demonstrated, not results already obtained. The ablation tables shown as examples are expected templates, not real measurements. This document is a research specification, not a results report.


1Executive Summary

PRECOG is a research system aiming to transform the classic hyperparameter optimization (HPO) problem into a trainability prediction problem: from an untrained model, dataset statistics, and a hardware environment, PRECOG seeks to predict — before any training on real data — a distribution of learning configurations likely to lead to fast, stable, and data-efficient convergence.

PRECOG does not replace final training. It precedes and guides the configuration search, drastically reducing the number of full training runs needed to find a good configuration.

The project's central statement is:

PRECOG does not search for the best hyperparameters after training many configurations; it seeks to learn the relationship between a model's initial state, the properties of the problem, and the learning conditions, in order to predict — before any real training — which configurations have the highest probability of leading to fast, efficient convergence.

PRECOG is designed as a hybrid architecture combining six complementary families of methods (zero-cost proxies, NEAR-style expressivity analysis, initialization theory, meta-learning, Bayesian optimization, adaptive short validation), organized in a closed continuous-improvement loop built on a meta-dataset of experiments.


2Motivation

Classic hyperparameter optimization (grid search, random search, Bayesian Optimization, Hyperband, PBT, etc.) essentially proceeds by expensive trial and error: every candidate configuration must be partially or fully trained to be evaluated. This cost becomes prohibitive as models grow.

Part of the recent literature (zero-cost proxies, training-free NAS, NEAR) shows that it is possible to extract informative signals about the potential quality of an architecture or configuration without full training, sometimes from a single mini-batch. These results remain fragmentary, however: no proxy is universally dominant, cross-domain generalization (vision → NLP → LLM) remains uncertain, and this work almost always focuses on ranking architectures rather than fully predicting a learning configuration (learning rate, batch size, initialization, scheduler, etc.).

PRECOG starts from the hypothesis that these signals, combined with each other and enriched by experience accumulated across many past training runs (meta-learning), can be exploited to build a configuration predictor, not merely an architecture ranking.


3Scientific Problem

3.1Informal formulation

Given an untrained model M, a dataset D (characterized only by its statistics, without training on it), and a hardware environment H, can we predict a learning configuration θ (fine-grained architecture, initialization, optimizer, learning rate, batch size, regularization, scheduler) that maximizes the probability of reaching a target performance, while minimizing the compute, time, and amount of data needed?

3.2Mathematical formulation

$$ \theta^* = \arg\max_{\theta} \; P\big(\text{Convergence} \geq \text{Target} \mid M, D, H, \theta\big) $$

PRECOG seeks to approximate:

$$ P(\theta^* \mid M, D, H) $$

without updating the real model's weights on real data (see §5 for the strict definition of "without training").

3.3What PRECOG is not


4Research Hypotheses

Each of these hypotheses must be tested and potentially refuted by the protocols described in §14.


5Operational Definition of "Without Training" — the Three Modes

This is the project's most important methodological constraint: it must be unambiguous.

Mode Description Real model weight update Usage
PURE-PRECOG Analysis of the untrained model and the dataset (statistics, forward passes without learning, zero-cost computations, Jacobian, etc.) ΔW = 0 Reference mode for the project's central promise
PROBE Very short, controlled training (e.g. 50–1000 steps, 0.1–1% of the total budget) ΔW ≠ 0, but bounded and logged Validation/refinement of a PURE prediction
FULL TRAINING Complete training ΔW ≠ 0, unrestricted Ground-truth generation, never used to "cheat" on the prediction

Contract rule (Zero-Training Contract): any benchmark claiming PRECOG's central promise ("predict without training") must be carried out exclusively in PURE mode. PROBE mode is an explicitly, separately measured extension: it must always be possible to answer the question "how much does PROBE add over PURE alone, for what additional cost?".

In PURE mode, the operations allowed on the dataset are limited to descriptive statistics (size, dimensionality, approximate entropy, class imbalance, redundancy, estimated noise) and, if needed, to forward passes without backpropagation or weight updates (to measure activations/Jacobian). No optimizer.step() loop is permitted.


6Positioning Relative to the State of the Art

Line of work Contribution to PRECOG Acknowledged limitation
Zero-Cost Proxies (training-free NAS) Fast signals (SynFlow, SNIP, GraSP, Jacob-Cov…) from a mini-batch No proxy dominates everywhere; correlations vary widely by domain
NEAR (effective rank of activations) Training-free expressivity signal, useful for choosing activation/initialization A single signal, insufficient to predict a full configuration
Initialization theory / dynamical isometry Framework for understanding signal and gradient propagation Results mostly established on simplified cases (deep linear networks)
Meta-learning for HPO Reuse of past experiments as a prior Strongly depends on the quality and diversity of the meta-dataset
Bayesian Optimization, Hyperband, BOHB, PBT, ASHA, Vizier, Optuna Efficient search engines under a budget Generally start from a weak or null prior; evaluation cost still high without a pre-training signal
Freeze-thaw BO / learning-curve prediction Progressive resource allocation, early stopping Already requires partial training observations

PRECOG positions itself as an upstream prediction layer for these search engines: they remain used as exploration arms, fed by a far more informed prior.


7Fundamental Principles

  1. Observe before testing. Any information exploitable without training must be exploited before spending compute.
  2. Never depend on a single signal. Each family of signals compensates for another's weaknesses (see §9).
  3. Predict distributions, not values. PRECOG returns a probable region with a confidence level, never a point value presented as certain.
  4. Learn conditional functions, not constants. E.g. LR* = f(Model, Dataset, Initialization, BatchSize, Optimizer), not "LR = 0.001".
  5. Measurable economy. PRECOG only has value if its total cost (analysis + any probes) remains far below the cost of classic HPO.
  6. Learn from its mistakes. Every gap between prediction and ground truth is valuable data, kept and exploited, not a result to ignore.
  7. Correlation ≠ causation. Relationships exploited in production must, as much as possible, be validated by controlled tests.
  8. Generalization above all. A high score on an already-seen benchmark has no scientific value until it is reproduced on tasks, architectures, and datasets never encountered before.

8Full Architecture

flowchart TD
    P[PRECOG] --> ME[Model Encoder]
    P --> DE[Data Encoder]
    P --> HE[Hardware Encoder]
    ME --> TR[Task Representation]
    DE --> TR
    HE --> TR
    TR --> TE[Trainability Engine]
    TE --> ZC["Zero-Cost Proxies"]
    TE --> NEAR["NEAR"]
    TE --> INIT["Initialization / Gradient / Jacobian"]
    ZC --> RD[Regime Detector]
    NEAR --> RD
    INIT --> RD
    RD --> MKB["Meta-Knowledge Base<br/>(meta-dataset + task embeddings)"]
    MKB --> MP["Meta-Predictor<br/>(multi-head ensemble)"]
    MP --> PRED["Prediction<br/>(distribution)"]
    MP --> UNC["Uncertainty<br/>(calibrated)"]
    PRED --> HD[Hyperparameter Distribution]
    UNC --> HD
    HD --> PS["Pareto Search<br/>(multi-objective)"]
    HD --> SE["Search Engine<br/>(BO / Active Learning / Diversity)"]
    PS --> ASP["Adaptive Short-Probe<br/>(PROBE mode, optional)"]
    SE --> ASP
    ASP --> REJ[Reject]
    ASP --> CONF[Confirm]
    REJ -. loop back .-> TE
    CONF --> FT[Full Training]
    FT --> GT[Ground Truth]
    GT --> MDU[Meta-Dataset Update]
    GT --> FA[Failure Analysis]
    MDU --> SDE[Scientific Discovery Engine]
    FA --> SDE
    SDE --> NEXT["PRECOG v(n+1)"]

    classDef reject fill:#fdecec,stroke:#c8483a,color:#7a2b21;
    classDef confirm fill:#e9f7ef,stroke:#1f9d55,color:#155c33;
    classDef next fill:#eef2ff,stroke:#1a56db,stroke-width:2px,color:#1a56db;
    class REJ reject;
    class CONF,GT,FT confirm;
    class NEXT next;

9Detailed Components

9.1Model Encoder

Extracts a descriptor vector $X_{model}$ from the architecture alone (no data): depth, width, number of parameters, FLOPs, activation type, normalization, residual-connection ratio, attention structure, required memory.

9.2Data Encoder

Extracts $X_{data}$ from descriptive statistics allowed in PURE mode: size, dimensionality, entropy, estimated noise, class imbalance, feature correlation, redundancy, distribution. Long-term goal: an embedding $Z_D = \text{Encoder}_{data}(D)$ enabling datasets to be compared by similarity.

9.3Hardware Encoder

Captures GPU/CPU, memory, bandwidth, numerical precision, batch capacity, interconnect — because the optimal configuration also depends on the execution environment: $\theta^* = f(M, D, H)$.

9.4Trainability Engine

The system's analytical core. Computes, without any weight update:

Combination rule: $Score_{ZC} = f(S_1, S_2, ..., S_n)$, never a single isolated score.

9.5Regime Detector

Classifies the (model, dataset, hardware) tuple into a learning regime (e.g. small model/clean data, large model/noisy data, low data volume, long sequences). Produces a regime prior used to constrain the predicted hyperparameter distribution.

flowchart LR
    A["Model, Dataset, Hardware"] --> B[Regime]
    B --> C[Hyperparameter Prior]

9.6Meta-Knowledge Base

A structured base of all past experiments (see §12), with a task embedding mechanism enabling retrieval of the historical experiments closest to a new task, and using that neighborhood as a search prior (experience transfer).

9.7Meta-Predictor

A model (or ensemble of models) taking as input:

$$ X = [X_{model}, X_{data}, X_{ZC}, X_{NEAR}, X_{init}, X_{regime}] $$

and producing, for each candidate configuration, a multi-head prediction:

The result is never a single value but a distribution, for example:

Learning rate
  recommended = 3.5e-4
  range       = [2e-4, 6e-4]
  confidence  = 91%

9.8Search Engine (BO + Active Learning + Diversity)

The meta-predictor provides an informed prior; the search engine then explores the remaining space. Hybrid acquisition function:

$$ Acquisition = \alpha \cdot \text{Expected Improvement} + \beta \cdot \text{Uncertainty} + \gamma \cdot \text{Diversity} $$

Google Vizier / Optuna / BOHB play the role here of exploration arms, not the system's brain.

9.9Pareto Search (multi-objective optimization)

Rather than seeking a single optimum, PRECOG searches for a Pareto front over (performance, compute, data, time, memory, energy):

quadrantChart
    title Pareto front: performance vs. cost
    x-axis Low Cost --> High Cost
    y-axis Low Performance --> High Performance
    quadrant-1 Best trade-offs
    quadrant-2 High cost, high performance
    quadrant-3 Low cost, low performance
    quadrant-4 Wasteful
    A: [0.2, 0.55]
    B: [0.35, 0.68]
    C: [0.58, 0.8]
    D: [0.78, 0.9]

PRECOG can then return several Pareto-optimal configurations, leaving it to the user (human or system) to choose according to their constraints.

9.10Adaptive Short-Probe (PROBE mode)

A short training budget allocated dynamically based on uncertainty and intermediate performance:

flowchart LR
    A["Candidate A · 50 steps"] -->|very poor| S1[STOP]
    B["Candidate B · 50 steps"] -->|promising| S2["+200 steps"]
    C["Candidate C · 50 steps"] -->|excellent| S3["+1000 steps"]

    classDef reject fill:#fdecec,stroke:#c8483a,color:#7a2b21;
    classDef confirm fill:#e9f7ef,stroke:#1f9d55,color:#155c33;
    class S1 reject;
    class S2,S3 confirm;

Formalization: $Budget_i = f(Uncertainty_i, Performance_i)$. This mechanism relies on learning-curve prediction (freeze-thaw) to estimate a time-to-target and decide CONTINUE/STOP.

9.11Decision Policy

An explicit policy turning PRECOG from a simple predictor into an experimental optimization agent:

$$ Policy(s_t) \rightarrow \{\text{TRAIN}, \text{STOP}, \text{EXPLORE}, \text{EXPLOIT}, \text{REQUEST MORE DATA}\} $$

9.12Causal Discovery Module

Separates correlation from causation through controlled experiments: with architecture, dataset, and optimizer fixed, a single candidate variable is varied (e.g. the gradient variance induced by initialization) to observe its isolated effect on convergence, rather than concluding from a simple observational correlation.

9.13OOD / Distribution-Shift Detector

Estimates $P(\text{known task})$. If a new task is judged far from the meta-dataset, PRECOG must automatically increase the validation budget (PROBE mode) rather than make an overconfident PURE prediction.

9.14Failure Analysis Engine

Categorizes every significant prediction error:

DATA_SHIFT
ARCHITECTURE_SHIFT
INITIALIZATION_FAILURE
OPTIMIZER_FAILURE
PROXY_FAILURE
PREDICTOR_FAILURE

and feeds the improvement cycle (meta-dataset → meta-predictor retraining).

9.15Scientific Discovery Engine

Longer-term goal: turn observed correlations into hypotheses, test those hypotheses through controlled experiments (see 9.12), and derive general principles of trainability from them (e.g. a candidate relationship $LR^* \approx f(\text{BatchSize}, \text{GradientNoise}, \text{ModelScale})$ to be experimentally verified).

flowchart LR
    E[Experiments] --> P[Patterns]
    P --> Co[Correlations]
    Co --> H[Hypotheses]
    H --> CE[Controlled experiments]
    CE --> CV[Causal evidence]
    CV --> NP[New principle]

10Variables and Hyperparameters

10.1Hierarchy of target hyperparameters (of the trained model)

Level Family Variables
1 Architecture depth, width, hidden dimension, number of heads, activation, normalization, residual connections
2 Initialization Xavier, He, Orthogonal, variance/scale, bias init, LSUV
3 Optimization optimizer (SGD, Momentum, Adam, AdamW, RMSProp, Lion), learning rate, batch size, gradient accumulation, momentum
4 Scheduling warmup, scheduler (cosine, linear, exponential, OneCycle), decay, minimum LR
5 Regularization weight decay, dropout, label smoothing
6 Data sampling ratio, augmentation, curriculum, amount of data

10.2PRECOG's internal hyperparameters (strictly distinct from the above)

Component Internal hyperparameters
Bayesian Optimization acquisition function, exploration/exploitation coefficient, kernel choice, initial observations
Short-Probe initial number of steps, probe budget, early-stopping threshold, confidence threshold
Active Learning exploration/uncertainty/diversity coefficients
Meta-learning embedding dimension, history size, meta-predictor learning rate

10.3Principle of conditional functions

PRECOG never learns a universal constant, only conditional relationships:

$$ LR^* = f(\text{Model}, \text{Dataset}, \text{Initialization}, \text{BatchSize}, \text{Optimizer}) $$ $$ \text{Initialization}^* = f(\text{Architecture}, \text{Dataset}) $$ $$ \text{BatchSize}^* = f(\text{ModelSize}, \text{DatasetSize}, \text{LR}, \text{Hardware}) $$ $$ \text{Optimizer}^* = f(\text{Model}, \text{Dataset}, \text{LR}, \text{BatchSize}) $$

and more generally a joint distribution $P(\theta^* \mid M, D, H)$, with an explicit interaction graph between variables (e.g. LR ↔ BatchSize ↔ gradient noise; Architecture ↔ Initialization ↔ signal propagation).


11The Central Concept: Trainability

11.1Operational definition

$$ \text{Trainability} = f(\text{Gradient}, \text{Jacobian}, \text{Activation}, \text{Curvature}, \text{Conditioning}, \text{Initialization}, \text{Architecture}, \text{Data}) $$

11.2Exploitable signals

11.3Central research question

Which signals, observable on an untrained model, actually predict the future speed and quality of learning — and which are merely artifacts correlated with the architecture?

This question must be addressed both predictively (the meta-predictor) and causally (the causal discovery module, §9.12).


12The Meta-Dataset: PRECOG's Scientific Memory

Every experiment — including every failure — must be recorded with, at minimum:

flowchart TD
    Exp[Experiment] --> M["Model<br/>architecture, depth, width, params, FLOPs, activation, norm."]
    Exp --> D["Dataset<br/>size, dimension, entropy, noise, imbalance, diversity"]
    Exp --> HW["Hardware<br/>GPU/CPU, memory, precision, bandwidth"]
    Exp --> Init[Initialization]
    Exp --> Opt["Optimizer, LR, batch size, weight decay, scheduler, warmup"]
    Exp --> ZCP["Zero-cost descriptors<br/>SynFlow, SNIP, GraSP, Jacobian, NEAR…"]
    Exp --> Dyn["Training dynamics<br/>gradient norms, loss slope, activation statistics"]
    Exp --> Curve[Full learning curve]
    Exp --> Cost["Steps, compute (GPU-hours), memory, time, amount of data, seed"]
    Exp --> GT["Ground truth<br/>final performance, convergence, real cost"]

    classDef confirm fill:#e9f7ef,stroke:#1f9d55,color:#155c33;
    class GT confirm;

Prediction failures are kept and labeled (see Failure Analysis, §9.14): they constitute a learning signal at least as valuable as successes.

Strict separation: the meta-dataset is partitioned into TRAIN / VALIDATION / TEST, with the TEST set explicitly locked (never used to improve PRECOG), to avoid benchmark overfitting.


13Experience Transfer and Task Embedding

flowchart TD
    NT[New Task] --> TE[Task Encoder]
    TE --> EMB[Task Embedding]
    EMB --> ST[Similar Tasks]
    EMB --> MD[Meta-Dataset]
    ST --> PK[Prior Knowledge]
    MD --> PK
    PK --> OPT[Optimization]

    classDef confirm fill:#e9f7ef,stroke:#1f9d55,color:#155c33;
    class OPT confirm;

PRECOG must be able to recognize that a new problem "resembles" a problem already encountered and exploit that similarity as a prior, rather than starting from an uninformed search — this is one of the main expected levers for moving from a merely analytical system to a genuinely intelligent one.


14End-to-End Experimental Pipeline

flowchart TD
    BT[Benchmark Tasks] --> PA["PRECOG Analysis<br/>(PURE mode)"]
    PA --> MP["Meta-Predictor<br/>prediction + uncertainty"]
    MP --> SE["Search Engine<br/>(BO / Active Learning / Pareto)"]
    SE --> TC[Top Candidates]
    TC --> SP["Short Probes<br/>(PROBE mode, optional)"]
    SP -->|promising| FT[Full Training]
    SP -->|poor| STOP["Stop / Learn"]
    FT --> GT[Ground Truth]
    GT --> MDU[Meta-Dataset Update]
    MDU --> FA[Failure Analysis + Retrain]
    FA --> NEXT["PRECOG v(n+1)"]

    classDef reject fill:#fdecec,stroke:#c8483a,color:#7a2b21;
    classDef confirm fill:#e9f7ef,stroke:#1f9d55,color:#155c33;
    classDef next fill:#eef2ff,stroke:#1a56db,stroke-width:2px,color:#1a56db;
    class STOP reject;
    class FT,GT confirm;
    class NEXT next;

This loop never stops after a single iteration: every PRECOG generation must be compared to the previous one under a strictly identical protocol.


15Test Protocols

Protocol Question Main metric
P1 — Ranking Does PRECOG rank configurations correctly? Spearman ρ, Kendall τ
P2 — Top-K Does it retrieve the best configurations? Recall@K
P3 — Convergence Does the chosen configuration converge faster? Steps/Time-to-Target
P4 — Compute How much compute is saved? GPU-hours / FLOPs
P5 — Data efficiency Same quality with less data? Samples-to-Target
P6 — Generalization Does it work on a never-seen model/dataset? Out-of-distribution performance

15.1TRAIN/VALIDATION/TEST separation

PRECOG TRAIN        → known datasets and architectures, experiment history
PRECOG VALIDATION   → different datasets, partially new architectures
PRECOG TEST (locked) → never seen, never used to improve PRECOG

15.2Reference benchmarks for the initial phase

15.3Multi-seed and statistical tests

Every important experiment is repeated over several seeds, with mean, standard deviation, and confidence interval (95% CI) computed. Comparisons between methods (PRECOG vs. Random, vs. BO, vs. Hyperband, vs. Vizier) use appropriate statistical tests (e.g. a Wilcoxon signed-rank test rather than a t-test when parametric assumptions aren't guaranteed), to avoid declaring superiority based on a lucky seed.


16Metrics and Objectives (to be demonstrated, not guaranteed)

Metric Definition Experimental target
Ranking correlation Spearman ρ / Kendall τ between PRECOG's ranking and the real ranking ρ ≥ 0.80 then ≥ 0.90
Top-K recall $Recall@K = \|\text{PredictedTopK} \cap \text{TrueTopK}\| / K$ Recall@10 ≥ 80% then ≥ 90%
Compute reduction $1 - C_{PRECOG}/C_{baseline}$ ≥ 50% then ≥ 70%
Performance retention $Performance_{PRECOG}/Performance_{oracle}$ ≥ 99% (or a tolerance defined a priori)
Data efficiency $Samples_{baseline}/Samples_{PRECOG}$ for equal target performance ≥ 30–50% reduction, to be refined
Time/Steps-to-Target Reduction in time/number of steps to reach a target ≥ 50% reduction
Prediction error (learning curve) $\lvert \text{Prediction} - \text{Actual} \rvert$ ≈ 5–10% depending on the metric
Generalization Recall@K on never-seen tasks/architectures/datasets same order of magnitude as on known data

These targets are progression hypotheses, formalized as successive gates (§17), never presented as already achieved.


17Progression Gates

flowchart TD
    P[PRECOG] --> G1["Gate 1: ρ ≥ 0.70?"]
    G1 --> G2["Gate 2: Recall@10 ≥ 80%?"]
    G2 --> G3["Gate 3: Compute reduction ≥ 50%?"]
    G3 --> G4["Gate 4: Generalization maintained<br/>(never-seen data)?"]
    G4 --> G5["Gate 5: Recall@10 ≥ 90%?"]
    G5 --> G6["Gate 6: Compute reduction ≥ 70%?"]
    G6 --> ADV["PRECOG 'advanced level'"]

    classDef next fill:#eef2ff,stroke:#1a56db,stroke-width:2px,color:#1a56db;
    class ADV next;

Each gate is validated by independent metrics, on locked datasets, before considering the next generation.


18Comparison Baselines

PRECOG must be systematically compared, at equal budget, against:

Random Search       Grid Search
Bayesian Optimization   Hyperband
ASHA                 BOHB
Population Based Training
Google Vizier         Optuna
Zero-Cost NAS (proxy alone)
Meta-learning HPO (without PRECOG's additional layers)

along the axes: final performance, compute, convergence speed, data needed, generalization.


19Ablation Strategy

19.1Pipeline component ablation

flowchart LR
    A["PRECOG-A<br/>Zero-Cost only"] --> B["+ NEAR"]
    B --> C["+ Initialization analysis"]
    C --> D["+ Meta-Learning"]
    D --> E["+ Bayesian Optimization"]
    E --> F["+ Adaptive Short Probe"]
    F --> G["+ Active Learning / Uncertainty"]
    G --> H["+ Causal Discovery / OOD detection"]

    classDef next fill:#eef2ff,stroke:#1a56db,stroke-width:2px,color:#1a56db;
    class H next;

Expected table example (a template, not real results):

System Spearman Recall@10 Compute used
Random 0.10 10% 100%
ZC 0.60 55% 10%
ZC+NEAR 0.68 64% 12%
+Init 0.73 70% 14%
+Meta 0.79 77% 16%
+BO 0.82 82% 20%
+Adaptive Probe 0.88 90% 30%

19.2Individual proxy ablation

SynFlow, SNIP, GraSP, Jacobian, NASWOT, Jacob-Cov, Gradient Norm, NEAR — tested individually then in combination, since the literature shows no proxy is universally dominant.

19.3Robustness testing

Deliberate perturbations: dataset noise and imbalance, distribution shift, model depth/width, activation, seed, batch size, hardware — to verify that PRECOG's performance doesn't collapse outside the meta-predictor's training conditions.


20Uncertainty Management

In addition to a prediction, PRECOG must systematically produce:

Example output:

Configuration A: prediction = 95%, confidence = 91%
Configuration B: prediction = 94%, confidence = 52%

Uncertainty directly feeds the acquisition function (§9.8) and the decision policy (§9.11): an uncertain but potentially informative configuration can be tested with priority to reduce the system's overall uncertainty (active learning).


21Causation vs. Correlation

A correlation observed between a pre-training signal (e.g. gradient variance) and final performance can be confounded by a third variable (typically the architecture). PRECOG must therefore:

  1. Identify candidate relationships from the meta-dataset's correlations.
  2. Formulate explicit hypotheses.
  3. Design controlled experiments where only the candidate variable changes (architecture, dataset, and optimizer fixed).
  4. Only promote a relationship to "knowledge exploitable in production" after causal validation, or otherwise explicitly mark it as "correlation not causally validated".

22Generalization and Distribution-Shift Detection

The generalization test (P6, §15) is considered the most scientifically important. It requires:

The OOD module (§9.13) must estimate $P(\text{known task})$ and automatically trigger an increase in the validation budget (PROBE mode) when a task is judged far from the meta-dataset, rather than producing an overconfident PURE prediction out of distribution.


23Methodological Risks and Mitigations

Risk Description Mitigation
Data leakage Real dataset information leaking into the PURE analysis Strict Zero-Training Contract (§5), audit of allowed features
Benchmark overfitting PRECOG optimized in a loop on the same benchmarks (NAS-Bench-201, HPOBench…) Locked TEST set, not revealed before final evaluation
Meta-dataset bias Over-representation of certain architectures/domains Diversification curriculum, explicit tracking of meta-dataset coverage
Undetected distribution shift PRECOG applied outside its domain of validity without warning OOD module (§9.13) + adaptive validation budget
Training stochasticity Confusing seed variance with a configuration's real effect Mandatory multi-seed runs, confidence intervals (§15.3)
Poorly calibrated uncertainty Displayed confidence not reflecting the real error Regular calibration, calibration tests (e.g. reliability diagrams)
PRECOG's own excessive cost Analysis cost exceeds the savings achieved Systematic measurement of $Cost_{PRECOG} + Cost_{PROBE}$ vs. $Cost_{classic\ HPO}$ (§24)
Misleading correlation A relationship exploited in production isn't causal Causal discovery module (§21)
Dependence on one architecture family Good performance only on the meta-dataset's architectures Progressive curriculum (MLP → CNN → Transformer → unknown), strict generalization tests

24System Economics

PRECOG only has practical value if:

$$ Cost_{PRECOG} + Cost_{PROBE\ if\ any} \; \ll \; Cost_{classic\ HPO\ or\ multiple\ FULL\ TRAININGs} $$

This constraint must be measured at every evaluation, not merely assumed. A system that is theoretically accurate but whose inference is too costly (e.g. a meta-predictor that itself requires enormous compute) must be considered an economic failure, even with a good ranking score.


25Development Roadmap

flowchart TD
    V1["V1 — Foundations<br/>Learning Rate, Batch Size, Optimizer, Initialization<br/>(basic zero-cost analysis, no meta-learning)"]
    V2["V2 — Full configuration<br/>Weight Decay, Warmup, Scheduler, Gradient Accumulation"]
    V3["V3 — Architecture<br/>Dropout, depth/width/activation/normalization"]
    V4["V4 — Intelligence<br/>Meta-learning, Task Embeddings, NEAR, combined Zero-Cost proxies"]
    V5["V5 — Adaptive search<br/>Active Learning, Bayesian Optimization, Adaptive Short-Probe"]
    V6["V6 — Science<br/>Causal Discovery, OOD Detection, Failure Analysis, Scientific Discovery Engine"]
    V1 --> V2 --> V3 --> V4 --> V5 --> V6

    classDef next fill:#eef2ff,stroke:#1a56db,stroke-width:2px,color:#1a56db;
    class V6 next;

Scientific progression by phase (indicative)

flowchart LR
    A["Phase A<br/>analytical foundations"] --> B["Phase B<br/>meta-learning + Bayesian Optimization"]
    B --> C["Phase C<br/>uncertainty + active learning"]
    C --> D["Phase D<br/>learning-curve prediction + adaptive probe"]
    D --> E["Phase E<br/>validation"]

    classDef next fill:#eef2ff,stroke:#1a56db,stroke-width:2px,color:#1a56db;
    class E next;

Experimental curriculum

flowchart LR
    L1["Level 1<br/>MLP on synthetic datasets"] --> L2["Level 2<br/>CNN on vision"]
    L2 --> L3["Level 3<br/>ResNet / modern architectures"]
    L3 --> L4["Level 4<br/>Transformers"]
    L4 --> L5["Level 5<br/>LLM fine-tuning"]
    L5 --> L6["Level 6<br/>never-seen models and datasets<br/>(ultimate generalization test)"]

    classDef next fill:#eef2ff,stroke:#1a56db,stroke-width:2px,color:#1a56db;
    class L6 next;

26Success Criteria

A PRECOG milestone is only considered reached if, simultaneously, on a locked test set never used for training:

  1. the ranking (Spearman ρ) reaches the target threshold for the level considered,
  2. Recall@K reaches the target threshold,
  3. the measured compute reduction reaches the target threshold,
  4. the retained final performance stays within the tolerance for loss defined a priori,
  5. results hold on never-seen tasks/architectures/datasets (generalization),
  6. results are reproducible (multi-seed, confidence intervals, documented environment).

A system that reaches only part of these criteria (e.g. good ranking but poor generalization) is not considered to have reached the milestone.


27Known Limitations


28Outlook

In the longer term, PRECOG's scientific ambition goes beyond HPO: the goal is to build an operational theory of predictable learning dynamics, i.e. a function

$$ F : (\text{Model}, \text{Data}, \text{Initialization}, \text{Hyperparameters}) \rightarrow \text{Training trajectory} $$

able to anticipate the loss trajectory $L(t)$ before full training. If this direction succeeds, PRECOG would stop being just a hyperparameter optimizer and become a predictive model of learning dynamics, with potential for its own scientific contribution (beyond integrating existing tools).


29Production Architecture (long-term target)

PRECOG, as a platform, must be able to:

  1. Receive an untrained model, the dataset's allowed metadata/statistics, and a description of the hardware environment.
  2. Run an analysis in PURE mode (no weight update on real data).
  3. Produce a hyperparameter distribution with justification and confidence level, as well as a Pareto-optimal set of configurations according to constraints (performance/compute/data/time).
  4. On request, validate the best hypotheses via a minimal budget in PROBE mode.
  5. Systematically log the experiment (including production usage) into the meta-dataset, for continuous improvement.
flowchart TD
    IN["Untrained model + Dataset (stats) + Hardware"] --> PURE["PRECOG (PURE mode)"]
    PURE --> HD["Hyperparameter distribution + confidence"]
    HD --> PO["Pareto-optimal set of configurations"]
    PO -->|optional| PROBE[PROBE]
    PO --> REC["Recommended configuration + justification"]
    PROBE --> REC

    classDef next fill:#eef2ff,stroke:#1a56db,stroke-width:2px,color:#1a56db;
    class REC next;

30Synthesis — the idea that distinguishes PRECOG from classic HPO

PRECOG does not simply search for the best hyperparameters after training many configurations; it seeks to learn the relationship between a model's initial state, the properties of the problem, and the learning conditions, in order to predict — before any training on real data — which configurations have the highest probability of leading to fast, efficient convergence.

Every evaluation, every benchmark, and every scientific communication about PRECOG must come back to this test: does the system provide information exploitable before training, that is measurable, generalizable, and economically justified — or does it merely reproduce classic HPO dressed up differently?