Documents
Documents are the finished work Cora writes: a launch plan, a weekly status report, a content calendar, a team handbook. They are written only by Cora, and they appear in the Documents section of Artifacts (Files until US-01M7PP0C, D0853) (D0567, D0572).
The examples on this page follow an invented coffee roaster, Larkspur Coffee, and its Spring launch campaign.
Organisation documents and mission documents
Section titled “Organisation documents and mission documents”There are two kinds of document, and each has its own readers (D0572).
- Organisation documents belong to the whole organisation, for example a team handbook or a brand summary. Organisation documents can be read by every member of the organisation. On the Artifacts page they sit under Documents, for example Documents › Handbook › Team handbook.
- Mission documents belong to one mission, for example a launch plan or a weekly status report. Mission documents can be read only by the members of that mission. They sit in that mission’s Artifacts tab, under Documents, for example Documents › Plans › Launch plan v2.
You see a mission’s documents only if you are a member of that mission. Someone outside the mission cannot open, download or be shown its documents. If you leave a mission, its documents leave your Artifacts too. Organisation documents stay readable for as long as you are a member of the organisation.
Either kind may have its own folders: a skill can name one (the weekly status report goes in Reports), and you can ask Cora to make one (“Cora, keep the dealer letters in a folder called Dealers”).
How an organisation document is made
Section titled “How an organisation document is made”Cora writes a mission document when someone in the mission asks for one, or when a skill says the work produces one. It goes straight into that mission’s folder.
An organisation document is different, because every member of the organisation can read it, including people who are not in the mission it was drawn from. So Cora writes an organisation document only when someone in a mission asks for one in that mission’s chat, for example “Cora, turn our tone of voice notes into a brand summary for the whole team”. Cora does not save it straight away. It posts an approval card in the mission’s chat that shows the name, the folder, the format, the size, the time to answer by in your own time zone, and that every member of the organisation will be able to read it. It also shows a short preview of the first lines in a box that scrolls, so you can check what you are approving without reading the whole document. The person who asked, or an org admin, approves or declines the card. Only an approved document is saved.
Each new version of an organisation document needs its own approval, on its own card.
The document records which mission and post it came from, so anyone can trace where it started.
Documents cannot be deleted yet, and a document cannot be moved between scopes, from the organisation to a mission or back. Ask Cora for a new document in the other place instead.
Written only by Cora
Section titled “Written only by Cora”Cora writes a document when you ask for one, or when a skill says the work produces one. You never edit a document yourself, and nor does anyone else in the team.
To change a document, press Ask Cora to change in its preview. It opens the mission’s chat with your message started for you, for example “@Cora please change Launch plan v2: “, with a link back to the document beside the box. Nothing is sent until you press Send. Finish the sentence and send it. For an organisation document, you first choose which of your missions to ask through, unless you are a member of the mission it came from. Cora writes a new version. Every version is kept, and every change is recorded.
A document is Markdown or HTML, or an SVG picture, and at most 1 MB (the size limit set in D0569; SVG since D0737).
Reading a document
Section titled “Reading a document”A document opens in the viewer in Artifacts:
- Markdown is shown as formatted text, with its headings, lists and tables.
- HTML is shown in a locked-down frame that cannot run scripts or reach the network (D0567).
- SVG is a picture or a diagram on its own, shown through the same frame.
An HTML or SVG document is shown only when it is self-contained. One that needs a script or anything from the internet says Inline viewing is not supported for this file. Download it to view. and offers its download there (D0736). Cora is told to write self-contained documents, so this should be rare; if you see it, ask Cora to rewrite the document without scripts.
Above the preview, breadcrumbs show its place, for example Documents › Missions › Spring launch › Reports › Weekly status, 3 Nov. A link takes you to the mission it came from.
Downloads
Section titled “Downloads”A Markdown or HTML document can be downloaded as a PDF, as Word or as the original. An SVG picture downloads as the original only.
- PDF, for sending or printing.
- Word (.docx), in the house style, for anyone who wants to work on a copy in Word.
- The original, the Markdown or HTML file exactly as Cora wrote it.
The PDF and Word copies are made on Cora AI’s servers, by a converter that fetches nothing from outside the document and never runs anything inside it (D0570). Each download is a short-lived link that saves the file to your computer. Your organisation can make up to 30 new PDF or Word copies in an hour (D0587). A copy that already exists does not count, and neither does the original. Over the limit, the download says so and asks you to try again shortly, or to download the original. A downloaded copy is yours to edit, but your changes stay on your computer: the document in Files changes only when you ask Cora.
PDF files Cora makes
Section titled “PDF files Cora makes”Cora can also make a PDF file of a mission document herself, for example to attach a weekly report to an email. She does it when someone in the mission asks for one, or when a skill says the work ends with a PDF (D0770).
- She makes it from a Markdown or HTML document of the mission, from its latest version.
- It is saved beside the document, with the same name and the extension .pdf. The PDF of the Markdown document Reports › Weekly status is Reports › Weekly status.pdf. The PDF of an HTML document adds “-html” to the name, so Reports › Weekly status-html.pdf, and a Markdown and an HTML document with the same name never share one PDF.
- Making it again, after the document has changed, adds a new version of the same PDF file, so the older ones are kept.
- It uses the same converter as the PDF download, and a new PDF counts towards your organisation’s 30 new copies an hour.
- A PDF file is at most 10 MB.
- People in the mission download it from the mission’s Artifacts tab, and Cora can attach it to an email.
An SVG picture, or an organisation document, cannot be made into a PDF this way. A PDF file has no preview in Artifacts: it shows its name and size with a Download button. It downloads as the PDF itself, never as Word.
Files Cora saves from her sandbox
Section titled “Files Cora saves from her sandbox”Cora also works with files in her sandbox: a screenshot she took, a chart picture or a CSV a command made, a PDF a tool produced. Those files are in the team folder, which the console does not show, so nobody in the mission can see them there. When the mission needs one, Cora saves it into the mission’s Documents with the tool save_file_to_documents, and posts its card in the chat (US-01M7MKRM, D0807).
- She can save PNG, JPEG, GIF and WebP pictures, PDF files and CSV files, each at most 10 MB, the same size as a file you share in the chat.
- The file’s contents must match its extension: a file called
chart.pngthat is not a PNG picture is refused. - She gives it a folder and a name, using the same rules as any document, and it keeps its own extension. For Kestrel Cycles, the screenshot
screenshots/2026-11-17T0305-e-bike-page.jpgbecomes Screenshots › E-bike page.jpg. - Saving the same folder and name again adds a new version, so the older ones are kept.
- It is a mission document: only the mission’s members can read it. There is no approval card, as for any mission document Cora writes.
- She can save only from the team folder (
/workspace/). A path with.., or a link that leads out of the folder, is refused. - A hero that another mission has called in saves from its own private folder for the call (
/task/) or the team folder, and only into its own mission’s Documents, never into the caller’s mission or the team folder (D0805).
In Artifacts, a saved picture is shown in the preview at up to the pane’s width, with a Download button. A picture larger than 3 MB, a saved CSV and a saved PDF are not shown: the preview says Inline viewing is not supported for this file. Download it to view. with the Download button. A saved file downloads as it is, never as Word or a converted PDF, and Cora can attach it to an email.
Cora is told that a file in her sandbox is not visible to the team until she saves it here, and never to say a file is in the mission’s files before it is.
Documents in the chat
Section titled “Documents in the chat”When Cora writes or changes a document, it says so in the mission’s chat with a card inside its message. The card shows a document icon, the document’s name, its place (for example “Documents · Reports”) and an Open button. Open takes you to Artifacts with that document open and its folders expanded (D0571).
The card is in the mission’s chat, so only the mission’s members see it.
Documents and the team folder
Section titled “Documents and the team folder”Documents are not kept in the team folder, and do not count towards its 5 GB. They are kept in Cora AI’s document store, with their versions and a record of every change (D0572). Material you want Cora to keep in mind, such as brand guidelines, goes in Cora’s memory instead, where CORA.md can point to it. See Artifacts.
Decisions: D0567, D0569 (replaced by D0572), D0570, D0571, D0572, D0770, D0807.