Identify the resource, not just its name
A file called “report.pdf” can exist in several systems. Galaris uses a URI to identify its source and the service controlling access. Agents discover available resource families before selecting an operation.
| Address | Resource |
|---|---|
document:// |
HTML documents, JSON Datasets and attachment collections |
memory:// |
Accessible knowledge |
galaris:// |
Tasks, Goals, cycles, processes and other exposed objects |
console:// |
Files in the active console’s home |
mail:// |
Attachments of an identified message |
| A connected Tool’s URI | Provider files, including Nextcloud or messaging attachments |
| Public HTTPS | Web reading or transfer within provider limits |
Search, read and edit within the right scope
Common tools cover listing, metadata, name or content search, paginated reading, creation, replacement, appending, targeted edits, copying, moving and deletion. Each provider advertises the operations it supports.
Reading can continue with a cursor. Edits use revision preconditions when required. Protected business objects retain their own rules; a file operation cannot bypass domain management.
Copy directly to a destination
An agent can copy a messaging attachment to a document or connected storage without inventing an intermediate local path. A destination collection can retain the original filename. Overwriting must be explicit.
Incoming media retain their receiving Tool. When a library needs local bytes, Galaris creates a bounded temporary materialisation. That temporary file does not become a new agent storage location.
Open files in context
Viewers support the available formats: text, images, PDF, audio, video, HTML pages and 3D scenes. Previews and conversions depend on the resource type. Galaris links open their corresponding object under its access rules.
Find inputs and deliverables
A Task’s Working Set retains inputs, produced files and final deliverables with tool evidence. Delivery of an existing file can be retried without calling the model again.
A console is needed for console:// storage. Documents and files from other providers use their own connections.
Edit documents · Use a console
Read files and understand interrupted transfers
Markdown attachments have a rendered reader; code, JSON and text retain a source view with copy and download. 3D previews support GLB, self-contained glTF, OBJ, STL and PLY within their limits; they do not replace CAD software.
For a staged copy, a download rejection before upload leaves the destination unchanged. An error after writing begins can leave an unknown outcome. Recovery must respect that distinction to avoid a second write.
HTML documents and JSON Datasets
document:// also identifies Datasets. An agent creates one with file_create and document_type="dataset"; HTML remains the default. The type is fixed at creation, including when writing, copying to an existing target or restoring a version.
Reading and editing use actual JSON lines. Every change validates the complete JSON and checks the expected revision. file_append concatenates text: it does not append a data record. Applications use the Dataset SDK to add an entry to an array. Copying a JSON resource into the Documents collection creates a Dataset.