--- name: nemoclaw-maintainer-policies description: "Answer NemoClaw maintainer policy questions about triage, labels, Project fields, releases, or competing contributions. Read-only." user_invocable: true --- # NemoClaw Maintainer Policies This package contains policy references. This file is its manifest and index. ## References Read the reference that owns the question. Read additional references only when that question crosses their boundaries. - [references/workflow-policy.md](references/workflow-policy.md) — Source of truth, authorization, Issue Type, label boundaries, and agent-owned labels. - [references/triage-instructions.md](references/triage-instructions.md) — Issue and PR evaluation, questions, `needs:*`, confidence, and suggestion payloads. - [references/label-taxonomy.md](references/label-taxonomy.md) — Label meaning, selection, compatibility, unknown labels, `agt: *`, and release labels. - [references/label-taxonomy.json](references/label-taxonomy.json) — Allowed machine values and write policy. - [references/project-workflow.md](references/project-workflow.md) — Project Status, lifecycle, duplicates, blocked work, review, and QA. - [references/daily-flow.md](references/daily-flow.md) — Daily priorities, standup, assignment, execution, and QA handoff. - [references/release-train.md](references/release-train.md) — Release inclusion, cutoff, carry-forward, history, and label retirement. - [references/examples.md](references/examples.md) — Examples for triage, review, release activation, competing PRs, and stale PRs. ## Answering Workflow Questions Read the related reference before you answer or apply policy. Use plain language for maintainers. Distinguish Issue Type, PR type labels, `needs:*` labels, Project fields, close reasons, and release labels. Do not invent labels, statuses, fields, release labels, or workflow states. Follow the shared [Documentation Writing and Review](../_shared/documentation-writing-review.md) contract for changed workflow guidance and maintainer-facing text. For agent implementation, use `triage-instructions.md` as the payload contract. Use `label-taxonomy.json` to validate allowed values. Workflow answers must remain reference-backed. Do not encode alternate policy in this manifest.