Skip to content

Artifacts

Artifacts is where the things your team and Cora make live in the console: everything Cora, the heroes and your team made or shared. The organisation’s artifacts (here) and each mission’s artifacts (in the mission) are kept apart. The explorer looks and works like the one in a code editor such as VS Code (D0567, D0621). Artifacts was called Files until US-01M7PP0C (D0853).

What Cora knows is no longer here. The organisation’s memory is in Settings, under Cora’s memory, and a mission’s memory is its own Memory tab. See Cora’s memory (D0854).

The examples on this page follow an invented coffee roaster, Larkspur Coffee, and its Spring launch campaign.

There are two ways in.

  • The Artifacts page. The console’s main navigation is a rail down the left side: Home, Missions, Heroes, Artifacts and Connections. Artifacts opens this page at /artifacts. The old address /files still works and brings you here. See the console reference.
  • A mission’s artifacts. On a mission’s page, the Details button at the top right opens a pane whose Artifacts tab holds that mission’s artifacts. See the mission’s artifacts.

The organisation’s artifacts, and a mission’s

Section titled “The organisation’s artifacts, and a mission’s”

The Artifacts page shows the organisation’s documents only. It never lists missions or a mission’s files: no files shared in a mission’s messages, and no mission’s documents (D0634, which replaced the Viewing picker of D0621; D0853; the list of missions it showed until US-01M7SS78 is gone, D0883).

At the top is one header row with the title Artifacts and the storage meter, then the line “Documents Cora saved for the whole organisation.” On the left, under a search box, Search documents, is one section with its heading and its count:

  • Documents: what Cora wrote or saved for the whole organisation, for example Documents › Handbook. Each row says who it is from and its size, for example “From Cora · 6 KB”, and the date it last changed. Only Cora writes documents. See Documents.

With no documents yet it says “Nothing here yet. Cora writes documents here.” Under the list, one quiet line says where a mission’s files are: “A mission’s files are in that mission: open it, then Mission details, Artifacts.”

The search narrows the documents by name. Choosing a document opens it in the viewer on the right.

A mission’s own files are in that mission’s own page: mission details’ Artifacts tab holds the mission’s documents and the files shared in its messages (see the mission’s artifacts). Older links keep working. The address /files?project=<id>, and the old mission files address, open that mission’s page with mission details open on Artifacts, and a link to one file opens that file. The same goes for /files?doc=<id> when the id is a mission’s document: it opens that mission’s page with that document open, never on this page. An old link to a memory file, /files?path=memory/..., opens that file in Settings, Cora’s memory. A mission appears only if you are a member of it; if you are not, the mission page says it was not found.

Artifacts stay current. In a mission’s Artifacts and Memory tabs, when Cora writes a document or a memory file, the part that changed reads again by itself within a second, and both read again when Cora finishes a run. The page is told only which part changed, never what is in it, and only people in the mission are told. On the organisation’s Artifacts page the documents read again when you come back to the window and every 3 minutes while the page is open and visible. Refresh reads the documents at once and shows a busy state, and a short note if the read fails. Your open folders, your selection and the file you have open stay as they are. If the open file has been removed, it closes with the note “This file was removed.”

Reference and Skills are no longer sections here. What used to be in Reference is now in the organisation’s memory, in a folder called reference, shown as Reference files in Settings, Cora’s memory. Skills now come with Cora AI itself and are not shown here.

  • Carets and icons. Each folder has a small arrow that turns when it opens, and a closed or an open folder icon. Each file has an icon for its type: Markdown, HTML, PDF, Word, spreadsheet, image, text, or a plain page for anything else.
  • Rows and indents. Rows are 26 px tall, and each level of folder is indented by the same 16 px, with a faint guide line for each level above.
  • Folders. A folder opens in place when you click it, and shows the folders and files inside it. Click again to close it.
  • Keyboard. The explorer is a tree. Use the up and down arrows to move, the right arrow to open a folder or step into it, the left arrow to close it or step out, Home and End to jump, and Enter or Space to open.

A file opens in the viewer, which fills all the space to the right of the tree. Markdown is shown as formatted text, and a Mermaid diagram in it is drawn as a picture. The drawing happens in a separate locked-down frame that sees only the diagram’s text, cannot reach the console or the network, and hands back a plain picture (D0596). If a diagram cannot be drawn, or the drawing frame does not answer, you see its text instead. An HTML document is shown in a locked-down frame that cannot run scripts or reach the network. Its own styles still apply, because the frame is a small page of the console with its own security headers (D0612). An SVG picture is shown through the same frame. A CSV file is shown as a table.

What is shown and what is download-only. Because the frame runs nothing and loads nothing from outside, an HTML or SVG file is shown only when it is self-contained: its own styles, inline SVG, and pictures carried inside the file. A file that needs a script, a canvas, a video, another page inside it, or a stylesheet, font or picture from the internet is not shown at all (BG-01M7JAJE, D0736). In its place the viewer says Inline viewing is not supported for this file. Download it to view. with the file’s download beside it, so you never see an empty box. A PDF, an image such as a PNG or JPEG, a Word file and any other type say the same sentence and offer the download (D0562).

File In the viewer
Markdown Formatted text, with Mermaid diagrams drawn
HTML, self-contained The page, in the locked-down frame
SVG, self-contained The picture, in the locked-down frame
HTML or SVG that needs a script or anything from outside Download only
CSV A table
Plain text As text
PDF, Word, PNG, JPEG and anything else Download only

One header sits above the file. On its first line, the breadcrumb shows where the file is: the section, then each folder, then the file, for example Documents › Handbook › brand-voice.md. Click any folder in it to open that folder in the tree and move focus there. Below it are the file’s name, its size and, for a document, when it was last changed. On the right are the buttons Wide, Outline and Download. A document’s Download offers PDF, Word or the original, and Ask Cora to change opens its mission’s chat with your message started for you. A memory file, read in a mission’s Memory tab or in Settings, has no Download, because the API gives no download link for a file that is shown.

A readable column. Text sits in a centred column about 880 px wide, so lines are comfortable to read. Wide lets the text, tables and long lines use the whole viewer. A web page (HTML) and a CSV table always use the full width. Wide is remembered in your browser, per person, and nothing from the chat is kept (D0128).

On this page. A Markdown file with three or more headings (levels 1 to 3) gets an outline on the right of the text, headed “On this page”, when the viewer is wide enough (about 960 px, which is a laptop screen with the tree at its usual width, and more on a bigger screen). Click a heading in it to scroll there. The section you are reading is highlighted. Outline hides or shows the list, and your choice is remembered like Wide. The outline is only for Markdown files, not for web pages or CSV, and not on a phone.

Tables. A table in a Markdown file, or in a chat message, keeps its headings in the case they were written and shows them on one line. A short first column such as a stage number no longer breaks letter by letter. A table wider than the page scrolls sideways inside its own bordered box, never the whole page. The same holds for a file opened from a mission’s details.

Resize the tree. Drag the edge between the tree and the viewer to change the tree’s width, from 220 to 520 px. The edge can be focused and moved 16 pixels at a time with the arrow keys; double-click, Enter or Home puts it back to 300 px. The width is remembered in your browser, per person. On a phone the tree and the viewer stack, one above the other, and the page never scrolls sideways.

A small meter in the header row, on the right of the Artifacts title, shows how much of the team folder’s 5 GB is used, for example “1.16 of 5 GB”. Every member sees it, with only the amount used and the limit. When the folder is full, nobody can add to it, and Cora cannot write there, until space is freed (D0531). Documents do not count towards the 5 GB.

On a mission’s page, the Details button at the top right opens and closes a pane on the right (D0718). Its tabs are Overview, Artifacts, Memory, Skills, Tools and Hero (D0853). The Artifacts tab shows the mission’s artifacts with the same explorer, on one page (D0830): Documents, then Shared in messages, each with its count and one line saying what it is. A search box above them, Search this mission’s artifacts, narrows both by name as you type. A picture Cora saved shows a small thumbnail on its row. The Memory tab shows the mission’s memory, with CORA.md pinned at the top and marked Always read, under the line “Notes Cora keeps about this mission. Only she writes here; ask her in the chat to change something.” Each tab reads its files the first time you choose it.

  • Closed until you open it. The pane is closed when you first visit a mission page, so the chat has the full width. The Details button opens it, on Artifacts the first time. After that it remembers whether you left it open, the tab you were on and its width, in your browser. A tab saved as Files opens Artifacts, and one saved as Memory opens Memory. If your browser does not keep settings, it simply starts closed each time.
  • A file opens in the middle. Choosing a file shows it in the middle, where the dialogue was. A bar above it shows where the file lives, its name and the download buttons, with a close button. Close it, or press Esc, to go back to the dialogue at the same place you left it.
  • The message box stays. While a file is open you can still write a message, for example to ask Cora about the file.
  • The mission list folds. While the pane is open on a desktop or laptop screen, the mission list on the left folds into a slim strip, so the dialogue keeps a comfortable width. The strip shows each mission’s avatar with its unread dot, and its name when you hover over it or tab to it. The button at the top of the strip expands the list again, and a Fold mission list button in the full list folds it back. Your choice lasts for the browser session. Closing the pane brings back the full list (D0621).
  • On a phone the pane does not squeeze the dialogue. It opens as a full-screen sheet over the page, with its tabs in a row and its own close button, and choosing a file closes the sheet and shows the file.

The organisation’s own documents stay on the Artifacts page in the left rail.

Part Where Who may add or change files Who may delete files
Documents Artifacts Only Cora. You ask Cora to change a document. Only Cora.
Cora’s memory: the organisation’s Settings, Cora’s memory The organisation’s admins and the platform super admin. The organisation’s admins and the platform super admin.
Cora’s memory: a mission’s The mission’s Memory tab Only Cora. Only Cora.

In plain words:

  • Documents are written only by Cora and are read-only to people. You can read them, download them and ask Cora to change them, but you never edit one yourself (D0572).
  • The organisation’s memory is written by the organisation’s admins and the platform super admin, and Cora reads it. A mission’s memory is written only by Cora. Both are read-only to everyone else (D0618, D0855). Moving memory to Settings did not change who may write it (D0854); John’s later decision let org admins write it (D0855).
  • Reference and Skills are no longer sections of Artifacts. Files that were in Reference are now in the organisation’s memory under reference/, and skills are built into Cora for every organisation and mission (D0620).

The organisation’s admins and the platform super admin can change the organisation’s memory. In Settings, Cora’s memory they see Edit on CORA.md, Add a file under Reference files, and Remove on a reference file or a file under What Cora has learned. Every change is recorded in the organisation’s audit history, without the file’s text. Add a file takes one text file (.md, .markdown, .txt or .csv, up to 60,000 characters). Any other type is refused with a message. An uploaded file is checked for its type and size but is not scanned for malware; it is read as text and never run. Everyone else reads “Members can read it. Org admins can change it.” The pnpm cora:memory command described on the Cora’s memory page does the same from a terminal. A mission’s memory is kept by Cora alone.

If the server refuses (the folder is full, or you may not change that file), the page shows its reason and changes nothing.

  • Every member of the organisation sees the organisation’s documents on the Artifacts page and the organisation’s memory in Settings.
  • You see a mission’s documents and memory only if you are a member of that mission. Someone outside the mission never sees them (D0572, D0619).

The team sandbox is set up the first time Cora works for your organisation, and it takes a few minutes. Until it is ready, Settings, Cora’s memory says the folder is being set up. Documents, and every mission’s memory, work from the start.

Decisions: D0128, D0531, D0562, D0565, D0567, D0572, D0612, D0618, D0619, D0620, D0621, D0853, D0854.