You are reading one repository to draft a section of an operator's standing brief.
You have been given reading tools only: there is no shell,
no editor and no verb here, so reading and answering is the whole of what you can
do.

## What you are writing

The `## Project context` section of `POLICY.md`, which a supervising orchestrator
session re-reads on **every** tick. Keep it **under 40 lines**: a brief nobody
finishes reading is a brief that gets skimmed.

It needs exactly four things, in this order.

1. **The product in one paragraph.** What it does, for whom. Not a feature list.
2. **A repo map** — one line per routing key below, naming what that repo owns in
   the operator's vocabulary. This is what turns a routing label into a judgement.
3. **Grooming guidance.** Which repos ship together, so a change in one is known
   to need a matching PR in the other. And which *kinds* of issue touch the same
   files: those must not be queued concurrently, because two agents editing one
   file produce two pull requests that cannot both merge.
4. **Where the roadmap lives, and how to judge priority against it** — in one
   line.

## Where you are

Your working directory holds **one directory per routing repo**, each a shallow
clone, listed below. Read across all of them — that is what makes items 2 and 3
answerable, and a draft written from one repo has to guess the rest.

In each, read the `README` (what it is for, and who uses it), whatever top-level
architecture doc exists (`docs/`, `ARCHITECTURE.md`, an ADR directory) for which
repo owns which concern, and `AGENTS.md` / `CONTRIBUTING.md` for the repo's own
rules — those outrank the brief.

## Stated inputs — these are given, not yours to decide

The routing keys this project dispatches to, and the directory each was cloned
into. Refer to repos by their **routing key**, never by the directory name — the
directory is scratch, the key is what an issue carries:

{{REPOS}}

The operator's own answer about the roadmap and the current priority:

> {{ROADMAP}}

**Item 4 must quote that answer.** You are reading a repository, which shows what
is open and never what matters; the operator supplied the ranking and it is not
yours to improve. If the quote above is empty, write item 4 as a single line
saying the operator has not named a roadmap yet, and nothing more.

## Answer

One fenced markdown block containing the section and nothing else — start it at
the `## Project context` heading. No preamble, no commentary after it.

Write what the repository supports. Where you are guessing, say so in the text
itself in a few words: the operator edits this file, and a marked guess is one
they can correct, while a confident invention is one they will not notice.