minimodel.org

Mini-Model · Edge / On-Device Ontologies

Compact Intelligence for the Constrained Edge

Mini-Model is the reference vocabulary for AI operating under hard resource constraints. Where macro and micro models describe what intelligence does, mini-model describes what intelligence must not cost — in memory, power, latency, and connectivity.

Edge Use Cases

Three Canonical Edge Scenarios

Each scenario defines a distinct constraint envelope. A model that passes all three is genuinely edge-deployable across the IoT, mobile, and embedded spectrum.

Edge · IoT Sensor

IoT Sensor

Keyword classification and anomaly detection running at microwatt power budgets on embedded MCUs — no cloud round-trip, no persistent memory.

  • RAM budget: < 256 KB
  • Inference latency: < 10 ms
  • Power envelope: < 1 mW active
  • No persistent network required
Canonical Concepts
WakeWordAnomalyScoreSensorLabelThresholdRuleQuantizedWeight
Edge · Mobile App

Mobile App

On-device NLP for privacy-preserving UX — autocomplete, intent classification, and content moderation without leaving the device.

  • Model size: < 100 MB on-disk
  • Cold-start: < 200 ms
  • Battery: < 2% drain per session
  • No PII transmitted to cloud
Canonical Concepts
IntentClassEntitySpanToxicityScoreLocalEmbeddingCacheHit
Edge · Embedded System

Embedded System

Real-time control inference in automotive ECUs, industrial PLCs, and avionics — deterministic latency under hard real-time constraints.

  • Worst-case execution time: bounded
  • No dynamic memory allocation
  • Safety integrity: IEC 61508 / ISO 26262
  • Bit-exact reproducibility required
Canonical Concepts
ControlOutputSafetyEnvelopeFaultCodeDeterministicPathFixedPoint

Story Figures

The Mini Model Deployment Story

Three figures that show how a compact model earns its place: the constraint envelope it must fit, the people who share the deployment decision, and the comparison that turns a task into a concrete choice.

The Deployment Envelope places a compact model inside the memory, latency, energy, privacy, hardware, and fallback conditions that determine whether it fits.
The Deployment Envelope places a compact model inside the memory, latency, energy, privacy, hardware, and fallback conditions that determine whether it fits. · Edit in CanonDraw ↗
The Deployment Field Kit gathers product, device, privacy, offline, cost, and reliability responsibilities around one explicit deployment decision.
The Deployment Field Kit gathers product, device, privacy, offline, cost, and reliability responsibilities around one explicit deployment decision. · Edit in CanonDraw ↗
The Deployment Comparison Ticket turns one task and environment into a review of constraints, routes, assumptions, capability limits, and fallback.
The Deployment Comparison Ticket turns one task and environment into a review of constraints, routes, assumptions, capability limits, and fallback. · Edit in CanonDraw ↗