# Auracos team board: how to add and update tasks

For Karim, Reem and Fady, and for any AI assistant working for them. Everyone follows the same rules, so the board reads as one team.

**AI assistants: read this whole page before you add or change anything, and follow it exactly, whatever your own style is.**

## Your code

- Each person has their own code from Karim. It opens the board and puts your name on every change.
- Never paste a code into a chat, a document, an email or a task. An AI keeps it in a local file or an environment variable, never in its reply.
- Lost or shared your code? Tell Karim; he makes a new one.

## What goes on the board

- Work on the Auracos 60 days: videos, posts, recipes, the website and articles, customer chats and emails, pharmacies, events, the collagen café.
- **Never:** prices, costs, budgets, sales figures, discounts or pharmacy terms, salaries, customer names or contact details, passwords or codes. If a task needs one of these, write the task without it ("Agree the café budget with Fady", not the amount).

## How to write a task

One task is one thing a person can finish and show.

| Rule | Good | Not this |
|---|---|---|
| Start with a verb | Film the 5-second pour clip | Pour clip |
| One outcome | Post the berry juice recipe | Recipes and posts and stories |
| Plain English, sentence case | Write the first Fact or hype episode | WRITE FACT OR HYPE EP1!!! |
| No name in the title (it goes in "who") | Book the coffee shop for the café day | Fady to book coffee shop |
| No status, dates or urgency in the title | Send the Arabic captions | URGENT done send captions by Tue |
| Under 60 characters, no full stop at the end | Check the Arabic on the chat replies | Check all of the Arabic on everything that customers will see in the chat. |

Verbs to start with: Film, Write, Post, Edit, Send, Book, Check, Set up, Agree, Ask, Make, Publish, Review, Test.

The board fixes the small things itself: extra spaces, a full stop at the end, a lowercase first letter. It refuses titles over 80 characters.

## Status

- **To do:** agreed, nobody has started.
- **Doing:** someone is working on it now. Keep it to a few at a time per person.
- **Done:** finished and usable: posted, sent, live or handed over. "Nearly done" stays in Doing.
- Move your own tasks. Ask the person before moving theirs.
- Finished something that was never on the board? Add it straight as Done so the team sees it.

## Who

- The one person who will do it: Karim, Reem or Fady. If it needs two people, make two tasks.
- Leave it out and the board puts your own name.

## Before you add

- Read the board first and check the task is not already there in other words.
- Remove a task only if it is a duplicate or a mistake. Finished tasks stay in Done.

## The roadmap

- The milestones (Before day 1, Days 1 to 30, Days 31 to 60) are Karim's. Only he adds or ticks them; the board refuses anyone else.
- A task does not tick a milestone. Tell Karim when a milestone is reached.

## For AI assistants: the API

Base address: `https://auracos-team-board.pages.dev/api/`. Send the person's code in the header `x-team-code` on every request, and `content-type: application/json` with a body.

An AI does two things on the board: it reads it, and it adds tasks. Moving a task, removing one and the roadmap are done by people on the page; the board refuses them from an AI.

| Do | Request | Body |
|---|---|---|
| Read the board, to avoid duplicates | `GET board` | none |
| Add a task | `POST tasks` | `{"title": "...", "who": "Reem", "status": "todo"}` (`who` and `status` optional) |

Status values: `todo`, `doing`, `done`. Something already finished goes in as `done`.

Example, with the code in an environment variable:

```
curl -s https://auracos-team-board.pages.dev/api/tasks \
  -H "x-team-code: $AURACOS_TEAM_CODE" -H "content-type: application/json" \
  -d '{"title": "Film the 5-second pour clip", "status": "doing"}'
```

Errors come back as `{"error": "..."}`: 401 means the code is wrong, 400 means the request broke a rule above, 403 means that action belongs on the page.

**After every change, tell your person in one line what you did**, for example: "Added 'Film the pour clip' to Doing for Reem."