AI & ML
Metadata-Driven AI: An Architectural Pattern for Sustainable Data Analysis with LLMs
arXiv cs.SE0 views
arXiv:2611.24661v1 Announce Type: new Abstract: Large Language Models (LLMs) let users analyse data in natural language, either by giving the data to the model to read directly or by having the model generate code to process it. Both routes send the data, or fragments of it, to the model; both pay for inference on every run; and the code a model writes to answer a question is usually discarded once the question is answered. We present Metadata-Driven AI, an architectural pattern that keeps the data away from the model and turns each analysis into a reusable program. Only metadata (not the actual data) crosses a one-way inference boundary to the LLM. The program the LLM returns runs next to the data and is kept, so that inference is paid once per analysis rather than once per run. We describe the pattern together with a simple cost model, a measurement of how little information crosses the boundary on public datasets, and a benchmark showing that a small, locally hosted model can serve as the generator. We illustrate the pattern on three applications, each built on a different implementation of it: geospatial photovoltaic prospection over live public APIs, extraction of portfolio positions from bank statements, and a conversational assistant over smart-city dashboards.
Source:https://arxiv.org/abs/2611.24661PreviousKeeping Up with the Kernel: Can LLMs Adapt Linux Drivers to Interface Changes?NextMLIR-MRacle: Memory-Model-Aware Metamorphic Fuzzing of Concurrent MLIR
Related posts
How do Balkan freelancers get paid by US clients without Payoneer?
0dev.to
Fuzzy name matching for sanctions screening: normalisation, transliteration and Jaro-Winkler
0dev.to
The Claude Architect Professional exam changes on 7 December - Here is what's different
0dev.to
SEO Isn't Enough Anymore. Meet GEO.
0dev.to

Prompt Engineering vs. Context Engineering vs. Harness Engineering: What’s the Difference?
0dev.to
P_SAPEA Exam Practice Questions: The Comparisons That Decide SAP Enterprise Architect Scenarios
0dev.to