Concepts and Architecture

MAGMA separates the interaction an agent must solve from the capabilities used to execute it. A scenario packages reusable components; a task assembles an interaction; stages define how progress is checked.

Installed scenario provider
  └─ Scenario manifest
      ├─ Environment registrations
      ├─ Presets → explicit tasks
      ├─ Definitions + requests → constructed tasks
      └─ Optional skills → orchestration of tools

Task → initial situation + stages + tools + initialization parameters
Agent → tool or skill calls → environment → results → stage verification

Read only what your current step needs

Question	Concept
What belongs in a scenario?	Scenarios
What does a task declare?	Tasks
How is progress checked?	Stages and interaction
Which state should I modify?	State and observations
How are varied interactions constructed?	Requests and constraints
What is executed?	Tools and skills
How do several robots share resources?	Execution and concurrency
How are failures introduced?	Errors and recovery
How are agent mistakes corrected?	Coaching and corrections
What must an environment preserve?	Environments

These abstractions support generation and evaluation workflows. Each consumer determines which optional capabilities it requires.

To build something, start with your own scenario package. Package and service responsibilities are described in architecture.