← All problem sets

SCADS 2026 / Problem 09

Core-to-edge model validation

Validate before the edge.

Research planning · deployment reliabilityNot started

The task

How could a model retain useful quality and reliability as it moves from a development environment to resource-constrained edge hardware?

Projected solution

I propose a staged validation pipeline linking model optimization, controlled core tests, representative device measurements, release criteria, and lightweight monitoring.

The plan treats quality and resource budgets as joint acceptance criteria. Quantized or distilled models would be compared with a reference model under matched data and workload conditions. Signed release manifests, bounded telemetry, and rollback criteria would connect those measurements to deployment decisions.

Proposed workflow

Proposed: model optimization · device validation · edge monitoring
  1. 01

    Qualify

    Measure quality, latency, memory, and robustness against a reference model.

  2. 02

    Validate

    Repeat representative workloads on target devices under realistic resource constraints.

  3. 03

    Monitor

    Track bounded operational signals and use explicit update and rollback criteria.

Implementation roadmap

Proposed milestones / Not started
  1. Define and freeze. Specify the task, data rights, baselines, evaluation criteria, and reserved test material.
  2. Build the smallest end-to-end study. Implement the proposed workflow with traceable inputs and reproducible outputs.
  3. Compare and stress-test. Run controlled baseline comparisons and ablations; inspect failure modes and resource use.
  4. Reproduce and report. Repeat the study from a clean environment and publish measured findings with supporting artifacts.

The research proposal expands these milestones into project-specific methods, experimental controls, and deliverables.

Methods / evidence / reproduction

Read the research.

The proposed study separates simulated constraints from measurements on physical devices. Quality changes, tail latency, memory, energy where measurable, and monitoring overhead would be reported with workload and hardware provenance.

The proposal develops the research question, proposed method, evaluation design, and phased roadmap. Its GitHub directory contains the planning documents. No implementation or experimental results are claimed.