AAM (Adaptive API Mesh) is the integration layer that inventories your enterprise's reusable data pipes and makes their behavior and meaning explicit. Think of it as a catalog of all the ways data can flow between your systems.
AAM sits between two other systems:
AAM does not move data, transform data, or act as an integration platform. It only observes and documents what already exists.
As an operator, AAM supports exactly three jobs:
Nothing more, nothing less. AAM deliberately avoids "magic" actions like "fix automatically" or "connect now."
This is your main dashboard showing all discovered data pipes. Access it via the Pipes navigation link.
| Element | What It Means |
|---|---|
| Pipe Name | Human-readable name for this data pipe (clickable to view details) |
| Source System | Where the data comes from (e.g., "Salesforce", "Workday") |
| Modality | How this pipe connects: CONTROL_PLANE, DECLARED_INTERFACE, PASSIVE_SUBSCRIPTION, or MINIMAL_TEE |
| Transport | How data moves: API, EVENT_STREAM, TABLE, FILE, or WEBHOOK |
| Trust Labels | Quality signals like data freshness, schema stability, ownership clarity |
| Button | What It Does |
|---|---|
| Run Collector | Triggers a collector to observe systems and update pipe information |
| Run Inference | Processes raw observations into declared pipes |
| Export to DCL | Generates a snapshot of all pipes in DCL format |
Clicking on a pipe name takes you to its detail view with complete information.
| Section | What It Shows |
|---|---|
| Identity & Classification | Pipe ID, display name, source system, modality, transport kind |
| Data Characteristics | Entity scope, identity keys, change semantics, freshness |
| Provenance | Discovery source, when discovered, lineage hints |
| Trust & Ownership | Trust labels, owner signals |
| Version History | How this pipe's definition has changed over time |
| Drift Events | Any drift events specific to this pipe |
Shows connection candidates from AOD that haven't been fully processed yet.
| Status | What It Means |
|---|---|
| New | Just arrived from AOD, not yet reviewed |
| Triaged | Reviewed but not yet connected to a pipe |
| Connected | Successfully matched to a declared pipe |
| Deferred | Intentionally set aside (with a reason) |
Shows issues that need attention - places where reality has diverged from expectations.
| Type | What It Means |
|---|---|
| SCHEMA | The structure of the data changed (fields added/removed/modified) |
| FRESHNESS | Data stopped updating at the expected rate |
| CONTRACT | The agreed behavior of the pipe changed |
| Level | What It Means | Response |
|---|---|---|
| Critical | Major breaking change | Immediate action required |
| High | Significant change | Review within 24 hours |
| Medium | Notable change | Review within a week |
| Low | Minor change | Review when convenient |
| Term | Definition |
|---|---|
| Candidate | A potential connection discovered by AOD that AAM might catalog |
| Collector | A component that observes enterprise systems and creates observations |
| Declared Pipe | A cataloged data connection with full metadata |
| DCL | Data Catalog Layer - consumes pipes from AAM to unify meaning |
| Drift | When reality diverges from what was previously observed |
| Modality | The approach for connecting (control plane, declared interface, etc.) |
| Observation | Raw data from a collector before being processed into a pipe |
| Pipe | A reusable data connection between systems |
| Provenance | Origin and lineage information about a pipe |
| Schema Hash | A fingerprint of the data structure for detecting changes |
| Transport | How data physically moves (API, events, files, etc.) |
Need more help? Check the API Documentation for complete endpoint details.