Role kernels

Navigator page. The canonical role kernels live in the repo. Each ~80–150 lines.

Cardinals (always present)

Role	Canonical kernel	Details (load-on-demand)
`team-lead`	`core/roles/team-lead.md`	`core/roles/team-lead.details.md`
`solution-architect`	`core/roles/solution-architect.md`	`core/roles/solution-architect.details.md`
`ai-engineer`	`core/roles/ai-engineer.md`	`core/roles/ai-engineer.details.md`
`frontend-engineer`	`core/roles/frontend-engineer.md`	`core/roles/frontend-engineer.details.md`
`backend-engineer`	`core/roles/backend-engineer.md`	`core/roles/backend-engineer.details.md`
`devops-engineer`	`core/roles/devops-engineer.md`	`core/roles/devops-engineer.details.md`
`qa-engineer`	`core/roles/qa-engineer.md`	`core/roles/qa-engineer.details.md`

Role	When to enable	Canonical
`security-engineer`	Project has auth / secret / network-policy NFRs	`extras/roles/security-engineer.md`
`ml-engineer`	Project ships an ML model, training pipeline, or serving tier	`extras/roles/ml-engineer.md`
`mobile-engineer`	Project includes a native iOS / Android / cross-platform mobile client	`extras/roles/mobile-engineer.md`
`sre`	Project has SLOs, runbooks, or post-deploy operational requirements	`extras/roles/sre.md`
`data-engineer`	Project has a data warehouse, lake, orchestrator, or dataset catalog	`extras/roles/data-engineer.md`

Author under local/roles/<your-role>.md using core/templates/role-authoring-template.md.

team-lead discovers new local/roles/*.md files on next dispatch — no registration needed.

Every cardinal kernel has the same shape (skim a single one to learn the pattern):

Front-matter — name, description (when to dispatch + what NOT to do), aliases (generic synonyms).
## Source of truth — two-tier load table (always + scope-loaded with trigger phrase). Per-file Load when column.
## Estimation-first dispatch — iteration-protocol entry point for work > 15 min.
Domain-specific sections — wire contract / mockup ownership / cost cap / etc.
## Forbidden actions (strict-domain) — role-specific negations. Hard stops.
## Reporting — what the final report must include.

Each cardinal carries aliases in its front-matter so adopters can use the more generic name if it fits their project:

Cardinal	Aliases
`frontend-engineer`	`client-engineer`, `ui-engineer`
`backend-engineer`	`service-engineer`, `server-engineer`
`devops-engineer`	`platform-engineer`, `sre-light`, `infra-engineer`
`qa-engineer`	`quality-engineer`, `test-engineer`, `sdet`
`solution-architect`	`architect`, `system-architect`

ai-engineer is role-name-canonical — no aliases. team-lead accepts orchestrator + project-manager (legacy name pre-2026-05-18) as aliases.