Sources is where Catalyst keeps the catalog of systems your teams depend on: what each one is, what it can access, how it connects, who owns it, and whether it is approved to feed Context or agents.
Governance decides which sources may be connected. Context decides how approved sources are modeled.
What lives in Sources
Before a system becomes context or automation, it should exist in a governed catalog with ownership, access posture, and downstream intent.
Register every application, feed, and document system your teams rely on so Governance starts from a real software dictionary instead of tribal knowledge.
Record what each source can read or write, which interface it uses, and the operational path it takes into Catalyst.
Track owner, status, and review posture so every source has a named steward before it is approved for downstream use.
Make PHI, confidential, and internal boundaries explicit before teams connect a source to Context, agents, or automation.
Set cadence expectations and monitoring posture up front so downstream teams know how fresh each system can be.
Approved sources can then be attached to the Context layer, where entities and relationships are built from the systems you trust.
How a source becomes usable
Sources creates the dictionary. Governance approves it. Context and Agents consume it.
Add the source system, owner, interface, and operational notes so it exists in the shared catalog.
Capture fields, access mode, and sensitivity before anyone assumes the source is safe or complete.
Use Governance to decide whether the source can be connected, under what conditions, and for which workflows.
Once approved, the source feeds the entities, relationships, and facts that make up your reusable memory layer.
Managed and custom agents consume only the sources and context that were explicitly registered and approved.
A shared dictionary that answers: what is this system, what does it touch, who owns it, and how does it enter the platform?
Explore the suite
Open the Sources workspace to inspect systems, owners, access patterns, refresh posture, and downstream readiness.