Skip to content

Glossary

The words the docs and the console use, grouped by topic. Where a term rests on a recorded decision, the decision id is given.

A chat with a job: what older versions of Cora called a project. A mission has its objectives, a spark tile in its own colour, its own people, its own chat, its own documents and its own memory, and Cora works in it. Only its members can see it. Any member of the organisation can start one. See how Cora runs a mission.

What a person writes when they create a mission: what it should achieve, and by when. They show in the mission’s header and in mission details, and the mission’s admins can edit them. From them, Cora writes up the full objectives as brief.md in the mission’s documents, which stays a draft until someone with the right role agrees it. See how Cora runs a mission.

Cora’s role in every mission. She coordinates the work: she writes up the objectives in full, keeps the to-do list, asks the right people and calls in heroes. People decide; Cora does not approve anything for them. Each of her messages says “Cora · mission coordinator”. See how Cora runs a mission.

The one shared chat in each mission, where the team and Cora talk. Everyone writes in their own name, and it is the record of what was asked, answered, approved and done. Cora posts cards in it for you to answer. See the mission chat.

A card Cora posts in the mission chat before a step that waits for a person, such as a tool set to Ask first. It shows exactly what Cora wants to do. Nothing happens until someone with the right role approves it, and a card nobody answers in 48 hours counts as a reject (D0132, D0314). See Off, Ask first and Allowed.

A card where Cora asks the mission to pick between two and five options, such as two page designs. Each member votes once, and Cora carries on with the result. A choice is not an approval (D0773). See questions, approvals and choice cards.

Work Cora does at a set time or on a repeat, no more often than every 15 minutes, set up by asking her in a mission. When it is due she wakes, does the work and posts the result in the mission. See schedules.

Numbers a mission keeps, such as a score or a count. Cora records a value when she measures it in a piece of work, and mission details shows how it has moved. See mission metrics.

A mission’s icon: a rounded square in one of 12 colours with Cora’s white spark. The colour comes from the mission’s id until one of its admins picks another in Overview. It never changes with progress. See the hero world.

An AI specialist that any mission in your organisation can call in by its own name, such as @kit. Where it comes from. A mission that its admins have promoted so the whole organisation can call it in. Or a hero created on the Heroes page, with a training room as its mission. Another mission asks it for something; the hero does the work with everything its own mission has (its skills, tools, connections and keys) and sends back its answer, a summary by default or a full answer if its admins choose. Its files and documents stay in its own mission (D0794, D0802). A hero answers and does work, but never approves or decides anything. See what a hero is.

The small pixel figure of a hero. A mission itself shows its spark tile, never a mini hero; a hero’s mini hero shows in its “Hero: ” chip, on its card on the Heroes page and on its own page. The four stages towards becoming a hero are Recruit (a new mission, in everyday clothes), In training (Cora has finished her first piece of work; it wears its suit), Ready (the mission also has a skill or connection of its own and ten finished pieces of work; it adds a mask) and Hero (the mission is a hero; it adds a cape). See the hero world.

The place in the console for everything Cora, the heroes and your team made or shared: the organisation’s artifacts on the Artifacts page, and each mission’s in its own Artifacts tab. Artifacts was called Files until US-01M7PP0C (D0853). See Artifacts.

The finished work Cora writes, such as a plan or a weekly status report, in Markdown or HTML. Only Cora writes them; you change one by asking her, and every version is kept. Mission documents are for the mission’s members; organisation documents are for every member. Each one downloads as a PDF, as Word or as the original. See documents.

What Cora knows. Your organisation’s memory, read at the start of every run, is changed only by its org admins and the platform super admin, never by Cora. Each mission also has its own memory, which only Cora writes (D0618, D0855). Its main file in each place is CORA.md. Your private chat is never part of it. See Cora’s memory.

A playbook: written steps Cora follows for a kind of work, such as a weekly status report. Some skills come with Cora; more can be added when Cora proposes one and an admin approves it (D0620, D0815). See skills.

A link between Cora and another service, so she can use its tools. An organisation connection is added by an org admin for everyone. A personal connection belongs to the person who added it, and Cora uses it only in the missions that person shares it in. Each mission switches a connection on before Cora can use it there (D0716). See personal connections and connecting an MCP server.

One of the three settings for a group of tools on a connection, with Ask first and Allowed; an org admin sets them on an organisation connection, and the owner on a personal one (D0716). Off stops Cora using a tool at all. On an organisation connection an org admin adds by its address, every new tool starts Off. See Off, Ask first and Allowed.

The setting that makes each call to a tool wait for a person’s approval card. Nothing happens until it is approved. Some tools always ask, whatever the setting (D0684). See Off, Ask first and Allowed.

The setting that lets Cora use a tool without asking. A tool that always asks cannot be set to Allowed (D0684). See Off, Ask first and Allowed.

An outside service that offers tools Cora can call, over the Model Context Protocol. An org admin turns MCP on for the organisation first. A server can be added by its https address, or set up from the catalogue of ready-made services (D0131). See connecting an MCP server.

Each mission’s small store of named keys for other services, such as an API key. A mission admin types a key once and nobody can read it back. Cora sees only its name; Cora AI’s worker adds the key to a call, sent only to the sites named for it (D0738, D0741). See the vault.

Your organisation’s private computer workspace, in AWS in Sydney, where Cora runs commands and keeps working files in the team folder, up to 5 GB. Each organisation has its own (D0528). See the team sandbox.

Cora’s ability to search the public web and read one page at a time. It is on for a new organisation, and an org admin can turn it off. What a page says is treated as data, never as an instruction to Cora (D0637). See web access.

A web browser Cora can drive to look at a page, click and take a screenshot. Each session is fresh and short, and is not recorded. See Cora’s browser.

The AI work your organisation’s plan includes: model calls, web searches, sandbox and browser time. The console shows it as a share of what your plan includes, never in dollars. When it is used up, Cora pauses until the next month (D0666). See plans and the free trial.

The 14 days a new organisation starts on: no card, a capped amount of AI usage in total, up to 5 members and 3 active missions. It ends when the 14 days are over or its AI usage is used up, and Cora then pauses; nothing is deleted (D0658). See plans and the free trial.

What your organisation pays for after the trial: Standard, Pro or Enterprise. Every plan has every feature. Plans differ only in AI usage, people, missions in the trial, and support (D0860). See plans and the free trial.

Your company in Cora: its people, missions, documents, memory, connections, sandbox and plan. Each organisation is kept apart from every other. See security and privacy.

A person whose org role is admin. Org admins look after the organisation: its people and roles, its connections and tool access, its settings, and its memory (D0855). See roles and approvals.

A person who can manage one mission: its people, its objectives, its vault and its settings. The person who creates a mission is its first admin, and an admin can make other members admins. A mission always has at least one. See the mission chat.

A person in your organisation whose org role is member. A member can start missions and work in the missions they belong to. Inviting people, and starting someone as an org admin or in an admin role, is for org admins. See roles and approvals.