Is this the same as data readiness?

Readiness is the go or no-go. Data foundations is the architecture. If the context layer is missing, you still get a readiness note, not a build.

Do you move the graph into MuleSoft?

No. We front it. The store of record stays the store of record.

Data foundations

Context before agency.

Data Cloud grounds the agent. Agentforce acts. Graph and vectors hold memory. MuleSoft fronts the stores it does not own.

Get the written assessment Data readiness

Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio

Split

Context is not agency. Memory is not the warehouse.

01
Systems of record
Salesforce · ERP · HR and ops · Files
02
MuleSoft
Canonical model · Gateway · Front, do not own
03
Context
Data Cloud · Clean Knowledge · Permissioned
04
Memory
Graph for relationships · Vectors for similarity
05
Agency
Agentforce · Or a custom runtime when the desk is elsewhere

Public data foundations for agents. Data Cloud or clean Knowledge is context. Agentforce is agency. Graph and vectors are memory. MuleSoft fronts the calls. The store of record stays the store of record.

Mermaid source

flowchart TD
  A["Systems of record"] --> B["MuleSoft: canonical model and gateway"]
  B --> C["Context: Data Cloud or clean Knowledge"]
  B --> D["Memory: graph and vectors"]
  C --> E["Agentforce: agency"]
  D --> E

Memory

Relationships in a graph. Similarity in a vector store.

MuleSoft can query both. It does not become the graph engine or the warehouse.

Lineage

Pick a lineage system. We will say which.

Informatica, Data Cloud, or the metadata tool you already run. Two lineages for the same field is a finding.

Failure modes

Three ways this stalls before the agent ships.

Agent first or context first

Two orders, two outcomes.

Agent first

Context first

Topics written before the data is read: Systems of record named before any topic
Warehouse and ERP left out of the brief: MuleSoft fronts what Salesforce does not own
Two lineages for the same field: One lineage system per field
Failures with no root cause: Traces that say data, identity or model

Where it starts

The system of record, named first.

Example
Head of finance operations at a Riyadh distributor
Today: The agent is meant to match invoices to purchase orders. The orders live in the ERP, not Salesforce.
After: MuleSoft fronts the ERP. The agent matches, refuses, or sends the invoice to a person.
MuleSoft
Example
Customer service director at a Dubai property developer
Today: Owners are in Salesforce, unit history is in a property system, and the handover files sit in a shared drive.
After: Each field gets one system of record before any topic is written.
Property management
Example
HR systems lead at a US healthcare group
Today: Staff want an agent that answers leave and payroll questions. People data lives in the HRIS.
After: Governed write-back to the HRIS, not a second HRIS inside Salesforce.
Healthcare

Examples of the work, not case studies. Roles and cities are typical of the desks we see.

Questions

What we actually say.

Is this the same as data readiness?: Readiness is the go or no-go. Data foundations is the architecture. If the context layer is missing, you still get a readiness note, not a build.
Do you move the graph into MuleSoft?: No. We front it. The store of record stays the store of record.

The brief · one email

Name the systems of record.

We will tell you what is context, what is memory, and what should not be copied. The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.