Deliverables

When a task produces finished files, DataMind Oda can declare them as deliverables: at the end of the turn the files appear as cards under the closing message of your chat, ready to preview or open. This page covers the cards, which files a delivery can name, and the rules that decide when a delivery is recorded.

Delivery cards

• Where they appear. After a turn that handed over files, the chat lists them as cards under the closing message, next to the changed-files card when the turn has one. The two lists differ: the changed-files card covers every file the turn edited, while the delivery cards name only the files Oda declared.
• Preview. Preview in sidebar opens the file next to the chat as a read-only preview; Preview files in the side panel covers the viewers.
• Open or reveal. A card can also start the file in its usual application or show it in your file manager; Open files and folders in other apps describes these controls.
• Recorded per file. The declaration records one line for each file: Presented <path>.
• In context. Your first task walks through a first chat, from the message to the files it hands you at the end.

What a delivery can name

• Only existing regular files. A delivery names files, not folders: every path must point at an existing regular file. A file that is missing is refused with Cannot present <path>: file not found. Check the path, create the file if needed, and retry., and a path that is not a regular file, such as a folder, is refused with Cannot present <path>: not a regular file.
• One to eight files. A delivery carries between one and eight files, and Oda is guided to declare at most four at a time. A list with no files, or over the limit, is refused.
• Paths. A relative path counts from the chat's workspace folder; a file outside it is named by its full path.
• What gets handed over. Oda declares the finished files it selects, such as a document, a spreadsheet or a report; Company data, documents and reports covers the files it makes from your data. A file made with a shell command is not handed over by itself: ask Oda to deliver it.
• Runs and turns. A delivery is accepted only inside a running turn of a chat with a workspace folder and at least one path to name; anything else is refused and records nothing.

When a delivery is recorded

• Only a finished step records. A delivery is written when the step that declared it finishes successfully. A blocked or failed step adds nothing to the turn.
• It belongs to the chat that declared it. When a helper task Oda started made the file, Oda declares it in your chat itself so the file reaches you there.
• The latest declaration counts. If a turn declares files more than once, the latest declaration replaces the earlier ones, and the latest list is the one that shows.

What a delivery does not keep

• Not a copy. A card points at the file itself and records its path, not its contents, so it opens the file as it is now.
• A file can change after delivery. A file can be replaced between the moment it was declared and the moment another app opens it, so a card can open a version that differs from the delivered one.
• Moved or deleted files. A file that is moved or deleted after delivery can no longer be opened from its card.
• Exports. An export of the chat carries the list of delivered files, not their contents.

Questions, answered

Which files can be delivered?

A delivery names existing regular files, such as a document, a spreadsheet or a report that a task produced. Oda declares the files it selects; a file made with a shell command is delivered when you ask for it, not by itself.

How many files can one delivery carry?

Between one and eight. Oda is guided to declare at most four files at a time, and a list with no files, or over the limit, is refused.

Can a delivery name a folder?

No. A delivery names files, not folders; a folder is refused with Cannot present <path>: not a regular file. Deliver a file inside it instead.

Do delivered files have to live in the workspace folder?

No. A relative path counts from the chat's workspace folder, and a file outside it is delivered by its full path.

Why does a delivery report that a file was not found?

The path it named has no file behind it, so the declaration is refused with Cannot present <path>: file not found. Check the path, create the file if needed, and retry. Create or find the file, then ask Oda to deliver it again; nothing was recorded for the failed attempt.

Why did a delivery record nothing?

A delivery is written only when its step finishes successfully, and only inside a running turn of a chat with a workspace folder. A blocked or failed step, or a declaration made outside a turn, records nothing.

Does a delivery keep a copy of the file?

No. A card points at the file itself: it records the file's path, not its contents, so it opens the file as it is now, and a file that is moved or deleted later can no longer be opened from its card.

Can Oda deliver a file a helper task made?

Yes, once it is declared in your chat. A delivery belongs to the chat that declares it; when a helper task Oda started made the file, Oda declares it in your chat itself so the file reaches you there.

Which list shows if a turn declares files twice?

The latest one. The latest declaration for a turn replaces the earlier ones, so the most recent list is the one that counts.

What does an exported chat carry for delivered files?

The list of delivered files, not their contents: an export names the files, and the files themselves stay where they are.