Overview
Modus mines the DAGs you select, with their schedules, owners, tags, and run history, so agents can tie a data question to the job that produced the data.
What Modus reads
- 1DAG
- 2Task
- 2DAG run
You select the level Modus is allowed to mine. Everything below it is discovered automatically; everything outside it is never touched.
2context types mined
3agent tool groups
2connection methods
3security controls
Context types
Each object Modus mines produces typed context items, addressed by their position in the hierarchy. This is what an agent actually receives.
DAG metadata
Schedule, owners, tags, and paused state for each selected DAG.
DAG run metadata
Recent run state and timing.
Example context item
airflow_dag_metadatadaily_finance_marts
- Schedule
- 0 5 * * * (UTC)
- Owners
- analytics-engineering
- Tags
- finance · tier-1
- Last run
- success · 05:14 → 05:38 UTC
Connection method
Connect once. Modus stores credentials in a managed secret store, rotates what it can, and never asks an agent to handle them.
Bearer token
Token authentication against your Airflow REST API.
Username & password
Basic authentication for a read-only Airflow user.
Security & governance
Governance is applied once, at the layer every agent runs through, so it holds no matter which agent asks.
Metadata-first mining
Modus learns from structure and usage, not bulk data. Raw records stay in your environment; only the metadata needed to understand the system is stored.
Scoped selection
You choose exactly which schemas, folders, spaces, or boards Modus is allowed to see. Nothing outside the selection is ever mined.
Read-only by default
Mining runs on a read-only credential. Any tool that writes back is a separate, explicitly granted action.
