This is a Plain English Papers summary of a research paper called AOrchestra: Automating Sub-Agent Creation for Agentic Orchestration. If you like these kinds of analysis, join AIModels.fyi or follow us on Twitter.

The multi-agent illusion

Most AI agent systems today operate under a fundamental constraint: they treat agents as either rigid specialists locked into predetermined roles or as context-isolated threads that lose all accumulated knowledge each time a new agent spawns. This creates a hidden tax on complex problem solving.

Imagine a software development team where every time someone switches tasks, they lose access to what they learned before. The front-end developer writes some code, hands it off to the backend developer, but the backend developer doesn't know about the design constraints the front-end developer discovered. Then the backend developer hands off to QA, and QA starts from scratch. Each handoff loses information. Alternatively, you could assign the same person to every role, but then they're constantly context-switching and never developing real expertise.

That's the trap existing multi-agent systems face. Researchers have documented this problem across frameworks, recognizing that multi-agent systems struggle with the tension between specialization and coherence. Some attempts at orchestral frameworks for agent orchestration have explored layered approaches, while others have looked at hierarchical structures for multi-agent reasoning, but they still work within this constraint.

The first approach treats sub-agents as isolated executors. Each time the system spawns a new agent, it gets only the immediate task. Everything the orchestrator learned is forgotten. This prevents "context rot" (where an agent's context window fills with accumulated, irrelevant details from past steps), but it means every new agent starts cold. If the orchestrator discovered that a user is on macOS or prefers a particular coding style, the next sub-agent never learns it.

The second approach assigns sub-agents static, pre-defined roles. You build a "Code Writer Agent," a "Testing Agent," and a "Documentation Agent," each with its own fixed tools and instructions. This preserves continuity and keeps agents specialized, but it's inflexible by design. What happens when a task needs something your pre-engineered agents can't handle? You're stuck. You'd need to anticipate every possible combination of skills beforehand, which defeats the purpose of using AI agents.

The deeper issue both approaches share is that they answer the question "What can this agent do?" at design time, not at execution time. The system cannot reshape its team composition to match the task at hand.

Comparison of sub-agent-as-tools approaches. (a) Sub-agents as context-isolated threads mitigate context rot but lack on-demand specialization. (b) Sub-agents as static roles provide specialized capabilities but are inflexible.

Comparison of sub-agent-as-tools approaches. (a) Sub-agents as context-isolated threads mitigate context rot but lack on-demand specialization. (b) Sub-agents as static roles provide specialized capabilities but are inflexible.

A recipe, not a machine

AOrchestra begins with a conceptual shift. Instead of thinking of agents as monolithic entities, treat them as recipes. A recipe doesn't describe a machine; it describes how to combine ingredients in a specific way to get a specific result.

Any agent, under this framework, can be described as a 4-tuple: Instruction, Context, Tools, Model.

Instruction is the task-specific goal or prompt. "Parse this JSON file into Python objects" or "Debug why this test is failing." This piece changes most frequently and is the most specific to the immediate problem.

Context is the accumulated state relevant to this particular subtask. If the orchestrator learned that the user's codebase uses type hints, that matters for a code-writing subtask. If the orchestrator knows the user is working in a constrained environment with limited dependencies, that should flow to the next agent. Context connects the dots between steps; it's what prevents each new agent from starting blind.

Tools are the executable capabilities the agent can call. A code interpreter. A file reader. A database query interface. A web browser. Different subtasks need different tools. A code-writing agent might need file system access and a Python interpreter. A research agent might need only a search API. By making tools explicit, the system can grant each agent exactly what it needs, no more, no less.

Model is the language model performing the reasoning. This is where performance-cost trade-offs live. A simple verification task might run on a fast, cheap model. A complex design task might require a more capable model. The system can choose the right tool for the job.

This abstraction is powerful because it's complete and composable. These four components fully specify an agent. By making them explicit, the orchestrator can construct the right specialist for each moment on demand. You don't pre-engineer every possible combination. You assemble them at runtime based on what the task actually requires.

How orchestration actually works

The orchestrator operates in a deliberate loop. When a user gives it a task, the orchestrator doesn't immediately create one large agent to solve it. Instead, it decomposes the problem and spawns specialized agents one at a time.

Here's the decision loop:

First, the orchestrator receives the overall task. "Fix this GitHub issue" or "Answer this question using available tools."

Second, it identifies the immediate subtask. What's the next step? Does the system need to understand the problem context? Read some files? Write code? Run a test? Each of these is a discrete piece of work.

Third, it curates the context dynamically. The orchestrator extracts only the information relevant to this specific subtask from everything it knows. If you mentioned you're using Python 3.11 but the current task is writing JavaScript, that context doesn't travel forward. Keeping context lean means agents spend their tokens on the actual task, not on irrelevant background.

Fourth, it selects the right tools. Based on the subtask, the orchestrator grants the agent access to specific capabilities. Need to execute Python? Grant a code interpreter. Need to search the web? Grant a search API. Need to modify files? Grant file system access. To...

This is a simplified guide to an AI model called PaddleOCR-VL-1.5 maintained by PaddlePaddle. If you like these kinds of analysis, join AIModels.fyi or follow us on Twitter.

Model overview

PaddleOCR-VL-1.5 represents an advancement in compact vision-language models designed for document understanding tasks. Built by PaddlePaddle, this 0.9B parameter model handles optical character recognition and document parsing across multiple languages. Unlike its predecessor PaddleOCR-VL, the 1.5 version improves robustness for real-world document scenarios. The model combines vision and language understanding in a single, lightweight architecture suitable for deployment on resource-constrained devices.

Model inputs and outputs

The model accepts document images as visual input and processes them through a vision-language framework to extract and understand text content. It returns structured text recognition results with spatial information about where text appears within documents. The architecture balances model size with performance, making it practical for production environments where computational resources remain limited.

Inputs

• Document images in standard formats (JPEG, PNG) containing text or structured document layouts
• Image dimensions ranging from low to high resolution, with automatic scaling
• Multi-language documents with text in various writing systems and scripts

Outputs

• Extracted text with character-level accuracy and word boundaries
• Bounding box coordinates indicating text location within images
• Confidence scores for recognition results
• Layout understanding identifying document structure and text regions

Capabilities

The model excels at extracting text from documents photographed in varied lighting conditions, angles, and quality levels. It handles forms, invoices, receipts, and handwritten documents with robust recognition. Multi-language support enables processing of documents containing text in different languages simultaneously. The system recognizes both printed and stylized text, making it suitable for diverse real-world document types.

What can I use it for?

Organizations can deploy this model for document digitization pipelines, automating data extraction from paper records without manual transcription. Financial institutions use it for invoice and receipt processing at scale. Educational platforms leverage it for converting scanned textbooks and educational materials into searchable digital formats. E-commerce companies implement it for order processing and shipping label reading. The lightweight design makes it suitable for mobile applications and edge devices where server-based processing becomes impractical.

Things to try

Experiment with severely degraded documents to test robustness limits—old photocopies, faxes, or images with heavy shadows. Test on documents combining multiple languages to see how the model handles code-switching and mixed-script scenarios. Try using it on non-standard document types like menu boards, street signs, or product packaging to explore its generalization capabilities. Process documents at various angles and rotations to understand how perspective changes affect accuracy. Run batch processing on large document collections to evaluate throughput and resource consumption in your deployment environment.

Original post: Read on AIModels.fyi

This is a Plain English Papers summary of a research paper called Multiscale Corrections by Continuous Super-Resolution. If you like these kinds of analysis, join AIModels.fyi or follow us on Twitter.

The curse of resolution in physics simulations

Imagine watching water flow through sand at two different zoom levels. At low zoom, you see the overall current pushing through the domain. At high zoom, individual sand grains create turbulence and complex flow patterns that wouldn't be visible from far away. To capture both, you need the high-zoom video, which takes forever to compute. Yet you can't simply use the low-zoom version because those tiny grain-scale interactions fundamentally change how the bulk flow behaves.

This is the core tension in finite element methods, the standard tool scientists use to approximate solutions to the differential equations governing physical systems. In these methods, computational cost scales brutally with resolution. Double your resolution in two dimensions and you create 16 times more elements. In three dimensions, that's 64 times more. This isn't a problem you solve by throwing more compute at it indefinitely. High-resolution simulations are accurate but prohibitively expensive. Coarse simulations are fast but miss crucial small-scale details that ripple through the big picture.

The multiscale structures in physics aren't incidental; they're fundamental. Small-scale heterogeneity in materials, turbulent fluctuations in fluids, grain-boundary effects in crystals, all these phenomena affect macroscopic behavior in ways that can't simply be averaged away. Yet capturing them requires the computational horsepower of a high-resolution simulation, creating a genuine impasse between speed and accuracy.

Why traditional multiscale methods don't quite solve it

Researchers have known for decades that you need something smarter than brute-force high-resolution simulation. The traditional approach looks like dividing a puzzle into pieces. You solve the problem at a coarse scale, figure out how that coarse solution influences the fine scale, then solve the fine-scale problem in each region, coupling the results back together. Mathematically, this works. Computationally, it's more involved than it sounds.

Methods like homogenization and multiscale finite element methods are mathematically rigorous and can provide guarantees about their approximations. But they require solving auxiliary problems, like the "cell problems" in homogenization theory, to understand how fine scales feed back into coarse scales. For complex materials or irregular geometries, these auxiliary problems can be nearly as expensive as the original simulation. You're trading one hard problem for several smaller hard problems, which is an improvement but not revolutionary.

The core limitation is that multiscale methods still require explicit computation of fine-scale corrections. You don't truly escape the resolution curse; you just distribute the work differently. For time-dependent problems or when you need to run many similar simulations, this overhead becomes prohibitive.

Super-resolution as learned multiscale correction

What if you bypassed mathematical derivation entirely and instead let a neural network learn the relationship between coarse and fine scales from examples? You run many simulations at both coarse and fine resolution, showing the network thousands of pairs, and ask it to learn the underlying pattern. Then, for new problems, you run only the cheap coarse simulation and let the network fill in the fine details.

This reframes the multiscale problem fundamentally. Instead of asking "how do I mathematically derive the fine-scale correction from the coarse solution," you ask "what statistical relationship exists between coarse-resolution snapshots of physics and fine-resolution snapshots?" Train a network to learn that relationship, and it becomes a reusable tool.

The brilliant insight is that you don't need to hand-derive the multiscale coupling. You're leveraging an assumption about the physical world: that small-scale structures follow patterns that are learnable and repeatable across different scenarios. If those patterns truly reflect the underlying physics, the network should generalize beyond its training distribution. It should work on upsampling factors it never saw, on material properties it never explicitly trained on.

Continuous super-resolution bridges coarse and fine scales. The orange region shows in-distribution scenarios (upsampling factors up to 16x), while the blue region shows out-of-distribution tests where the method extrapolates to 32x and beyond.

This is where the paper departs from typical deep learning applications. It's not just applying image super-resolution to scientific data. It's asking whether neural networks can learn and extrapolate the structure of multiscale physics.

The architecture: local implicit transformers learn across scales

Building a network that handles both coarse context and fine reconstruction simultaneously requires solving a specific technical challenge. How do you make a neural network that respects multiscale structure, preserves both large-scale features and fine details, and works at arbitrary query locations, not just fixed grid points?

The answer involves two key components working in concert. First, local implicit neural representations (LIIF) treat space as continuous rather than discrete. Instead of the network learning a grid of pixel values, it learns a continuous function that can predict the field value at any spatial coordinate, like x=0.1234, y=0.5678. The coarse module processes the coarse finite element solution and extracts features. The fine module takes those features plus a query coordinate and outputs the fine-resolution prediction at that specific location.

Second, a transformer architecture handles the multiscale learning. Transformers excel at learning long-range dependencies and attention patterns, which maps directly to the physics: the fine-scale behavior at one location depends on coarse features potentially across a large region. The transformer learns which parts of the coarse domain matter for predicting details at any given location.

The architecture processes coarse finite element data through feature extraction, then uses a local implicit function in the transformer to predict fine-scale corrections at arbitrary spatial coordinates.

The elegance of this design is that it separates the two jobs cleanly. The coarse module se...