> For the complete documentation index, see [llms.txt](https://docs.autonomify.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autonomify.xyz/4.-architecture-design-and-security-model/4.2-context-layer.md).

# 4.2 Context Layer

The Context Layer is the intellectual core of Autonomify. It defines how agents see the world—how data is captured, structured, interpreted, and authorized before any decision is made. Unlike traditional automation systems that operate on isolated inputs, Autonomify treats context as a multi-source, multi-modal, continuously streaming information surface.

Context ingestion begins through MCP adapters that unify access to chains, wallets, applications, APIs, and proprietary data sources. Each adapter enforces identity, permission scope, and query semantics before emitting data into the standardized MCP packet format. These packets are not simple key-value messages but structured schemas encoding temporal ordering, provenance, confidence scores, execution constraints, and environmental metadata. Agents therefore do not consume raw inputs; they consume interpretable state.

Once ingested, the system performs normalization, cross-schema merging, and structural reconciliation to produce a coherent world model. Temporal conflicts, stale state, and partial observations are resolved through versioned context maps, enabling agents to reason over consistent snapshots of their operating environment. Because context is streamed rather than polled, agents can detect patterns that emerge across temporal windows, not just isolated events—supporting long-horizon strategies such as portfolio migration, liquidity rotation, protocol interaction pipelines, and complex multi-step automations.

This layer also supports contextual transformation, where derived signals—risk scores, volatility indicators, task priorities, dependency graphs—are generated and stored alongside raw inputs. These derived signals dramatically increase the expressiveness of agent reasoning while keeping the system deterministic and verifiable.

The Context Layer therefore forms the epistemic boundary of autonomous execution: everything an agent knows, everything it is permitted to consider, and everything it uses to form decisions originates from this standardized, cryptographically structured surface.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.autonomify.xyz/4.-architecture-design-and-security-model/4.2-context-layer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.