Skip to content

How Cora works

Cora works with your team in three parts. People decide. Cora coordinates: she is each mission’s mission coordinator, an AI that plans and runs the work (D0851). Heroes specialise: they are AI specialists any mission can call in by name. Everything else on this page is how those three work together.

Your people make the calls. They write a mission’s objectives, answer Cora’s questions, agree what she drafts and approve anything that changes something outside Cora. Cora’s approval cards always go to people, and she can never mark her own draft agreed. Each organisation has a role catalogue, and Cora sends each question or approval to the people who hold the right role. One role, the fallback decision role, is always held, so a decision can always reach someone. See Roles and approvals.

Cora is in every mission. She reads what is asked, answers or does the work, keeps the mission’s status, and calls in help when a job needs it. She writes in the mission chat in her own name, like everyone else. She never writes a mission’s records or documents directly: she asks the platform for every change, and the platform checks it is allowed (D0113). See Objectives and the plan.

A hero is a specialist the whole organisation can call in. Each goes by its own name, so you call in Kit with @kit. A hero does the work with its own skills, tools and connections, and sends back its answer; its files stay in its own mission. You create a hero on the Heroes page, or a mission’s admins make a mission a hero once it has proved itself (D0856, D0857). See The hero world.

A mission is a chat with a job. It has its objectives, its people, its files and its own memory. Any member of your organisation can start one. A mission is private: people who are not its members cannot see it at all (D0122). See Objectives and the plan.

A mission’s objectives say what it should achieve, and by when. You write them when you create the mission. Cora writes them up in full as a draft, makes a first plan of work, and asks the mission’s lead to check the draft. A mission’s admins can edit the objectives later (D0852). See Objectives and the plan.

Each mission has one chat. It is also the official record of what was asked, answered, approved and done. You write in your own name, or press Polish to have Cora tidy your words first. Posts are never edited (D0545). When Cora needs something, she posts a card you answer with one tap. See The mission chat.

Anything that changes something outside Cora waits for a person, unless someone has chosen to let Cora go ahead. Cora posts an approval card in the chat and stops until it is approved or rejected. An approval nobody answers expires after 48 hours and counts as a reject (D0132). See Questions, approvals and choice cards.

Artifacts are everything Cora, the heroes and your team made or shared: the documents Cora writes and the files shared in messages. Artifacts on the left rail shows the organisation’s; the Artifacts tab of mission details shows a mission’s. Every version of a document is kept (D0572, D0853). See Artifacts.

Cora keeps notes for your organisation and for each mission. The main file of each is CORA.md, which Cora reads at the start of every run: it is your team’s standing instructions to her. The organisation’s memory is in Settings, under Cora’s memory, and a mission’s is the Memory tab of mission details (D0618, D0854). See Cora’s memory.

A skill is a playbook: written steps Cora follows for a kind of work, such as a weekly status report. Most are built in, and every organisation gets the same ones. Cora can propose a new skill, and an admin approves it (D0620). See Skills.

Connections let Cora use your other tools, such as a ticketing tool or an analytics account. Each tool of a connection is Allowed, Ask first or Off, set once on the connection (D0716). A connection can belong to the organisation or to one person, who shares it in the missions they choose. See Connections: Off, Ask first, Allowed.

Each mission has a small vault of named secrets, such as an API key. A mission admin adds them in a form, never in the chat. Cora sees only the names, and a key is sent only to the sites you named for it. See The vault.

The team sandbox is a private computer workspace Cora uses for your organisation. In it she can run commands, keep working files and install small tools a task needs. It belongs to the organisation, so what she keeps there is there for every mission next time (D0528). See The cloud sandbox.

Ask Cora to do something at a set time or on a repeat, such as “every weekday at 9 am, post yesterday’s open tasks”, and she sets up a schedule. A schedule runs no more often than every 15 minutes. See Schedules.

  • People decide; Cora coordinates; heroes specialise.
  • Each mission is private to its members. Nobody else in the organisation can see it.
  • Changes outside Cora wait for a person, unless someone chose Allowed for that tool or key.
  • Nothing is edited behind your back. Chat posts are never edited, and every version of a document is kept.
  • Secrets stay out of the chat. Keys go in the vault or a connection, never in a message.
  • Every plan has every feature. Plans differ only in AI usage, people, the trial’s missions and support (D0860).