# scrum.aomi.dev — agent handbook

> You are an agent acting for an aomi teammate. Fetch this once per session, then
> do what your operator asked. Generated live — do not cache across days.

The board is a DERIVED view: every page reads GitHub (org `aomi-labs`) and
re-renders. There is no board database to edit. To change anything you see on any
page, write to GitHub with the marker contracts below, using your operator's own
credentials — run `gh auth status` first; you act as them, and the board shows
the work under their login. Writes appear on the board within ~60s.

Roster (every owner/assignee below is a GitHub login): CeciliaZ030, h4n0, kevinssgh, arixoneth, 0xgordian, victorchimakanu

Markers are load-bearing: the `<!-- aomi-* -->` HTML comments in issue bodies
are how the board derives state. Keep them intact when editing; place them on
their own lines.

## /tasks — the engineering board

Cards are LINES OF WORK derived from PRs across org repos, plus declared todos.
A todo is an issue in `aomi-labs/aomi-scrum` — the issue IS the card.

### Add a todo to someone's plate

```
gh issue create -R aomi-labs/aomi-scrum \
  --title "<what needs doing>" \
  --assignee <owner-login> --label aomi-todo \
  --body "<context, links, acceptance>

<!-- aomi-todo owner=<owner-login> -->
_Declared through the aomi-scrum board. Reference this issue from your PRs to attach them; at 2+ PRs it graduates into the lines-of-work tree._"
```

Contract: repo `aomi-labs/aomi-scrum` · label `aomi-todo` · assignee = owner ·
body ends with the owner marker. The marker also accepts optional `flow=<key>`
and `line=<line-id>` attrs to suggest placement — omit them when unsure.

### Work a todo
- Attach PRs by referencing the issue from PR bodies (cross-repo form: `aomi-labs/aomi-scrum#<N>`). At 2+ attached PRs the todo graduates into the tree as a declared story.
- Complete: `gh issue close <N> -R aomi-labs/aomi-scrum --comment "<what shipped>"`
- Reassign: change BOTH the GitHub assignee and `owner=` in the marker — they must agree.

### Doctor cards ([bug] issues)
Same repo, filed daily by the sentry-doctor workflow with a fixed owner rotation.
Operator's move: read the prescription, fix it in `aomi-labs/product-mono`,
reference the issue from the fix PR, close when deployed. Do NOT file `[bug]`
issues by hand — the doctor owns that flow; file a plain todo instead.

## /marketing — the GTM map

A marketing story = an issue in `aomi-labs/design` carrying the deliverable
marker. Sectors are the map's regions — tag every story to one:

- `fintech-mgmt` — Fintech Management: A single high-profile agentic app — e.g
- `agents` — Agents: The surface consumed by coding agents — Claude, Codex, openclaw
- `retail-chatbot` — Retail Chatbot: The consumer chatbot experience — ChatGPT-for-crypto
- `web3-platforms` — Web3 Platforms: One-shot launch platform — good for meme coins and custom crypto trading surfaces

### Add a marketing story

```
gh issue create -R aomi-labs/design \
  --title "<the deliverable>" --label <home-tag> \
  --body "<what it is, for whom, why now>

<!-- aomi-deliverable sector=<sector-key> -->"
```

`<home-tag>` is a kebab-case topic label the story's workspace folder is named
after (e.g. `retail-chat-ui`) — pick a short durable topic; never one of the
reserved type dirs `posts` `decks` `videos` `docs` `_templates`.

Optional markers, own line each:
- `<!-- aomi-needs owner/repo:ref ... -->` — declare eng dependencies
- `<!-- aomi-publish-on YYYY-MM-DD -->` — put it on the release calendar

Campaign variant (a container, not a deliverable): title prefixed `[Campaign]:`
+ `<!-- aomi-campaign sector=<sector-key> -->`, no home-tag label.

## /marketing/deliverable/<N> — one story

The story's lifecycle (idea → drafting → ready → delivered) derives from its
WORKSPACE in `aomi-labs/design` main — folders, not ceremony:

- `deliverables/<home-tag>/<N>-<slug>/draft/` — scratch space; push artifacts straight to main
- `draft/STATE.md` — the story's running log; append intent and decisions, never rewrite history
- Adopting (promoting a finished artifact into its subtype folder `post/`, `video/`, …) flips the story toward ready — do that from the story page UI, or move the file and add the publish-on marker

Before MAKING content (posts, decks, video scripts, HTML): fetch
https://scrum.aomi.dev/marketing/llms.txt — the brand brief (message, voice,
terminology, design tokens). Claims not derivable from it are not yours to make.

## Other pages

`/marketing/core` (brand hub), `/marketing/sector/<key>`,
`/marketing/collection/<tag>`, calendar, analytics, partners — all are views
over the same two stores. Same contracts as above; there is nothing extra to
write to.

## Ground rules

- Act only on your operator's ask; don't close or edit other people's issues unprompted.
- Issues and the design workspace are the write surface. Repo CODE stays PR-only — never push code to main anywhere.
- Verify your write landed: re-run the `gh` read, or reload the page after ~60s.
- If a contract here seems stale, trust the board's behavior and say so to your operator — this doc is generated, and drift is a bug worth reporting (an `aomi-todo` on CeciliaZ030's plate).
