Skip to content

What a hero is

A hero is an AI specialist that any mission in your organisation can call in by its own name. You call in Kit with @kit, never by the name of the mission behind it (D0856, D0857). People still decide: a hero answers questions and does work, but it never approves or decides anything.

Missions and heroes are two different things (D0850). Most missions are just missions: a room where your team works with Cora, the mission coordinator. A few become heroes that other missions can call on.

  • Every mission has a spark tile: a rounded square in the mission’s colour with Cora’s white spark. It is smooth, not pixel art, and it never changes with progress. See the mission’s icon.
  • Only a hero has a mini hero: a small pixel figure in a suit and cape. A mission that becomes a hero keeps its spark tile, and beside its name you see a small chip with the hero’s face and its name, for example “Hero: Kit”.
  • Heroes have their own section: Heroes on the left rail, under Missions.

There is a mission behind every hero, where Cora coordinates and its admins train it: the mission it came from, or a training room made with it. That mission’s admins are the hero’s admins.

The examples on this page follow an invented bike shop, Kestrel Cycles, and its mission “Autumn launch”.

  • Create a hero on the Heroes page, when you know what you want before any mission has done the work. Cora makes its training room with it.
  • Make a mission a hero once the mission has proved itself. It keeps its name, objectives and people.

Either way the hero ends up the same: a card on the Heroes page, a page of its own, and a mission behind it.

The word mission stays. On the way to becoming a hero, a mission goes through four stages: a new mission starts as a recruit. You see them as four steps in the mission’s Overview, under Becoming a hero, not on its icon. Once the steps are done, a mission admin can press Make it a hero. The steps are explained below; the button and the dialog are in make a mission a hero.

Stage What it means How its hero would look
Recruit A new mission, with its objectives. Cora has not finished a piece of work in it yet. Everyday clothes: a grey top, blue trousers and brown shoes
In training Cora has finished her first piece of work. The mini hero in its suit
Ready The mission also has a skill or connection of its own, and ten finished pieces of work. The suit, with a mask and a white mark on the chest
Hero The mission is a hero: other missions can call on it. The suit and mask, with a cape and a few sparkles

The last column is how the mini hero looks at each stage. The mission itself only ever shows its spark tile.

A mission is always at exactly one stage. Nobody sets the first three by hand: they follow what has really happened in the mission (D0817).

  • A recruit from the start. Every mission has its objectives from the moment it is created, so every new mission is a recruit.
  • Recruit to In training. Cora finishes her first piece of work in the mission.
  • In training to Ready. The mission has a skill or connection of its own, and Cora has finished ten pieces of work. Both are needed, in either order.
  • To Hero. A mission admin makes the mission a hero with Make it a hero in mission details, Overview, once the other steps are done (see make a mission a hero).

One piece of work is one turn of Cora’s that finished and wrote a document in the mission’s Documents, for example a report, a plan or a checklist.

  • A turn that wrote several documents counts once.
  • A turn that only replied in the chat does not count.
  • A turn that failed or was stopped does not count.
  • A document that a person wrote or edited does not count.
  • Cora’s memory notes and files in the team folder do not count.

Only the first ten are counted towards being ready, so the mission’s details show “3 of 10”, never “14 of 10”.

What counts as its own skill or connection

Section titled “What counts as its own skill or connection”
  • A skill of its own is a skill installed for this mission only (see skills in a mission). The built-in skills and skills installed for the whole organisation do not count.
  • A connection of its own is a connection switched on in this mission, or a personal connection someone shared with it (see personal connections). A connection that has been removed does not count.

One of either is enough.

The stages follow what is true now. If the mission’s only skill is removed, or its only connection is switched off, a mission that was ready is in training again until it has one. This is rare, and nothing is lost: the work is still there.

Heroes on the left rail opens the Heroes page (/heroes). Each hero is a card, not a list row:

  • its mini hero on a band in the light shade of its cape’s colour, and its name, large;
  • where it came from, under the name: “Hero of the Page checks mission”, or “Made as a hero” for one created on this page;
  • one line on what it is good at;
  • its skills and connections as chips, so you can see what it can do before you call it in. The chips show the names of its skills, of the organisation’s connections switched on in its mission, and “Web access” when it can use the web. A person’s own connection is never shown (D0856);
  • “Helped 4 missions this week · 2 admins”;
  • Open Kit, which opens the hero’s own page, and its @handle.

The filters are All, Mine (the heroes you are an admin of) and Off (heroes that are switched off), each with how many it shows. A hero that is switched off is shown only to its admins and to org admins. Create a hero, as a button and as the dashed card after the others, opens the form to create a hero.

The missions list no longer has a Heroes filter or a Heroes group: a mission whose hero is on is listed with the other missions, with its Hero chip.

Open Kit on a card opens the hero’s page. At the top are its mini hero, its name, where it came from, its @handle, whether it is on, and how many missions it helped this week. Its admins see Turn it off, or Turn it on when it is off (see who can call a hero). A member of its mission sees a link to the mission: Open the training room for a hero made as a hero, or Open the Page checks mission.

For the people in its mission the page has four tabs, as mission details has: Overview, Memory (the notes Cora keeps for it: memory and skills are how a hero is trained), Skills and Tools. Overview holds:

  • Look: its mini hero with Shuffle and Choose (see the look);
  • Profile: Hero name (with the @handle it gives), What is it good at?, When should Cora call it in?, How should it work? (its standing instructions) and Who can call it in?. Its admins edit them and press Save; everyone else reads them;
  • Its admins: the admins of its mission;
  • What it has done: the card other missions see, the missions that called it, and its incoming tasks. Who sees what each caller spent is in calling a hero by name.

Someone in the organisation who is not in its mission sees what it is good at, when Cora calls it in, who can call it in and its admins, and nothing of its instructions, memory, skills or tools.

By default every mission can add a hero and call it in. Its admins can limit it to missions they choose. See who can call a hero.

A hero’s mini hero has five parts, and it has a name. Its admins choose the look on the hero’s page, and for a mission that is not a hero yet the look is ready in the Make it a hero dialog:

  • Head: Short hair, Spiky hair, Bun, Long hair, Helmet or Hood.
  • Hair: black, brown, blonde, red, white or teal.
  • Skin: five skin tones, Skin tone 1 to Skin tone 5.
  • Suit: one of 12 colours: fern, indigo, sunset, sky, rose, lemon, teal, plum, coral, slate, mint or mocha.
  • Cape: one of the same 12 colours. The mask is the cape’s dark shade, and a hood takes the cape’s colour once the mission is a hero.
  • The name is the hero’s own name. A mission’s suggested name is one of 24 plain names, such as Kit, Pip or Ivy, until someone chooses another. The @handle follows the name (see calling a hero by name).

Until someone chooses, each part and the name come from the mission’s own id. So every mission has its own look from the start, and it never changes by itself. Missions made before the hero world have one too. The mini heroes are original characters drawn for Cora AI.

The hero’s admins (its mission’s admins, or an org admin who is in the mission) can change the look at any time, on the hero’s page under Look. The name is changed under Profile on the same page:

  • Shuffle picks another look at random.
  • Choose opens the picker: Head, Hair, Skin, Suit and Cape, each a group of choices. The mini hero is drawn again as you choose.
  • Save appears once something has changed, and keeps it. Until you save, nobody else sees the change. Everyone in the mission sees the new look once it is saved.

Every other member sees the look with no controls, and the line “Only the hero’s admins can change its look.” Each change is recorded in the organisation’s audit history with the parts chosen and the length of the name, never the name itself.

Every mission has a spark tile: a rounded square in one of the same 12 colours, with Cora’s white four-point spark and a small spark beside it (D0849). It says “this is a mission, and it is this one”. It is smooth, not pixel art, so you can always tell a mission from a hero.

Until someone chooses, the colour comes from the mission’s id, so every mission has one from the start, including missions made before the spark tile. The mission’s admins can change it: open Mission details, then Overview, and press Change the icon colour under the mission’s name. Pick one of the 12 colours and press Save. Everyone in the mission sees the new colour, and each change is recorded in the organisation’s audit history.

The mission’s admins (a mission admin, or an org admin who is in the mission) can rename it at any time (D0852):

  • In the mission’s header, press Rename beside the name, type the new name and press Save.
  • Or open Mission details, then Overview, and press Edit beside Mission name.

A name is 1 to 200 characters. Everyone in the mission sees the new name in their missions list straight away. The audit history records that the mission was renamed and how long the new name is, never the words.

A mission’s objectives are what you write when you create it: what the mission should achieve, and by when (D0851). They show in the header after “objectives:”, and in mission details under Objectives, where the mission’s admins can edit them. Cora reads them at the start of the mission and writes up the full objectives, brief.md, in the mission’s documents (see how Cora runs a mission).

The objectives are also the first of the four steps the Overview shows on the way to being a hero: “Objectives written on” and the day they were written.

  • The Heroes page. Every hero as a card. See the Heroes page.
  • The missions list. Each mission shows its spark tile and its own name. A hero’s row also has the chip “Hero: ” with the hero’s face, and says how many missions it helped this week. There is no Heroes filter: heroes have their own page.
  • The New mission button. It is the words only.
  • The mission header. The spark tile, the mission’s name (with the Hero chip when it is a hero), and the line “Coordinated by Cora · 3 people · objectives: …”. There is no stage on the header.
  • The chat. A small line, with the mission’s spark tile, marks the moment the mission became ready to be a hero, or became one: for example “Autumn launch is ready to be a hero.” Cora’s first finished piece of work gets no line. It is not a message: it is never counted as unread and nobody is notified (D0819, D0850). See the mission dialogue.
  • Overview, in mission details. The spark tile and the mission’s name, the objectives, and under Becoming a hero one line and the four steps, each marked done or to do. A mission whose four steps are done shows Make it a hero to its admins; a hero shows its chip and Open , a link to the hero’s page.
  • Tools, in mission details. Under Heroes helping here, each hero added to the mission is drawn as its mini hero.
  • The hero’s page. The look, the picker, its profile, its admins and what it has done.
  • When a hero is called. The card that brings a hero’s answer into your chat shows the hero that answered: its mini hero, its name, the name on its card and the result. See calling a hero by name.

The mini heroes are drawn by the console itself, 16 by 18 pixels of pixel art, and are named for screen readers: “Kit, a recruit”, “Kit, a hero in training”, “Kit, ready to be a hero” or “Kit, a hero with a teal cape” (D0820).

  • The stage does not limit what a mission can do. A mission that is not a hero can use every tool a hero can.
  • The stage is separate from the mission’s own status that Cora keeps (on track, at risk, and where the work is up to).
  • A caller gets a hero’s answer, never its chat or files. Every member can see a hero’s card: its look, name, what it is good at, when to call it, where it came from, its skill and connection names and its admins (D0856).
  • Nothing from your private chat with Cora is used or stored for any of this.