MétaCan
Menu
Back to cohort

Securing Agentic AI in IoT Systems

2025· article· W7117758288 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typearticle
Language
FieldComputer Science
TopicSoftware System Performance and Reliability
Canadian institutionsUniversity of Saskatchewan
Fundersnot available
KeywordsInternet of ThingsProxy (statistics)Gateway (web page)Forwarding planeLatency (audio)Corporate governance

Abstract

fetched live from OpenAlex

We present a dual-proxy, seven-plane gateway for agentic AI in IoT that separates data, control, security, autonomy, context/knowledge, coordination, and management concerns. A lightweight client-side proxy verifies, annotates, and signs requests, while a server-side proxy near the data plane enforces global policy and model routing. To govern autonomous AI, we add a Goal-Plan-Step sentinel that requires plan publication and step-level justifications, and we execute device commands through a Digital Twin. Our Rust/Actix-Web prototype hosts hot-swappable WebAssembly filters (Wasmtime). In closed-loop tests with 1,000 requests and 1–10 concurrent clients, median latency for the proxy-microservice invocations is below 0.8 seconds. Predictable behaviour persists up to 100 clients, with overload observed beyond 200 on a single GCP e2-medium host. These results indicate that governance and low-latency operation can be achieved for agentic IoT deployments with modest infrastructure requirements.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.890
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.002
Science and technology studies0.0000.000
Scholarly communication0.0010.000
Open science0.0010.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.008
GPT teacher head0.266
Teacher spread0.257 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it