# Triage knowledge profiles

One file per company codebase, written in English, read by the `triage`
skill to classify and route reports. Generate or refresh a profile with
the `map-repo` skill, run from inside the repo being mapped.

File name: `<repo-name>.md` (lowercase). Target length 100–200 lines.
Keep the exact section headings below — the triage skill relies on them.

## System identity

Name, one-line responsibility, owning developer, and which
`routing.json` area keys this system maps to.

## User-visible surfaces

Screens / pages / endpoints / dashboards a reporter might screenshot.
Include visible titles and labels exactly as they appear on screen.

## Error fingerprints

What failures from this system look like in a screenshot: banner /
dialog / toast styles, exact localized error strings (it-it and en-us),
HTTP/gRPC status codes surfaced to users, what a crash looks like.

## Symptom → area heuristics

Bullet list of `symptom → area-key`, e.g.
`payment stuck on "processing" → backend`.

## Domain glossary

Italian terms reporters actually use, mapped to system concepts
(e.g. `annunci → Announcement`, `prenotazioni → BookingOrder`).

## Not mine

Symptoms that look like this system but belong to another area — name
the correct area key for each.