Sources

Sources are the knowledge content inside a Context Space.

They are not prompts. They are documents that the runtime can read, search, preview in the dashboard, and use as grounding material for an agent run.

File-system sources

The travel guide sample registers local documents from ./Context:

.AddSources(sources => sources.FromFileSystem(
    id: "travel-docs",
    name: "Travel Documents",
    path: "./Context",
    description: "Sample travel planning documents and city guide notes."))

That folder contains files such as:

Context/
  ankara-guide.md
  bursa-guide.md
  istanbul-guide.md
  izmir-guide.md
  london_city_guide.pdf

For another domain, the same structure could be:

SupportDocs/
  refund-policy.md
  account-troubleshooting.md
  escalation-rules.md
  release-notes.json

Supported file types

The current file-system reader supports:

Files larger than the reader limit are skipped. The default file-system reader limit is 5 MB per file.

How source search works

When an agent with an attached Context Space runs, the runtime searches source documents using the user message.

The current implementation is deterministic text search, not a vector database. That makes the behavior simple to inspect and predictable for the sample runtime.

Grounding behavior

Source excerpts are added under Runiq Retrieved Source Context when relevant results are found.

The generated instruction text tells the model to prefer retrieved excerpts over general knowledge when they directly answer the request.

If no source excerpts are retrieved, the instructions explicitly tell the model not to claim it has read source contents.

Studio preview

The dashboard shows the result of the source registration made in code. In the example above, FromFileSystem(...) defines a source with the id travel-docs, the display name Travel Documents, and the path ./Context.

After the application starts, Runiq reads that source definition and discovers the supported files under the configured folder. The sources view groups those readable documents by source, so developers can confirm that the runtime found the expected files before an agent tries to use them.

In context-source-documents.png, the developer can inspect:

• the registered source group,
• the documents discovered from the file-system source,
• each document path and name,
• the selected document preview,
• the content that can be searched and attached to an agent run.

This matters because Context Spaces are application-owned grounding material. If a file is missing, placed in the wrong folder, too large, or not a supported type, the agent will not be able to retrieve useful excerpts from it.

When an agent with this Context Space runs, Runiq searches the discovered source documents using the user's message. Relevant excerpts are added to the run instructions under Runiq Retrieved Source Context. The agent can then answer using that application-provided content instead of relying only on general model knowledge.

Preview protects against unsafe paths and blocks common app settings/secrets file names.