---
name: one-queue-tasks-issues-comments
description: Apply the One queue for the build: tasks, GitHub issues and model comments as one object article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.
---

# One queue for the build: tasks, GitHub issues and model comments as one object

This Skill is the behavioral expression of [the canonical article](/a/one-queue-tasks-issues-comments). It does not repeat the article's human prose.

## Orient

- Read the machine article at /api/articles/one-queue-tasks-issues-comments.
- Read claims and relationships at /api/articles/one-queue-tasks-issues-comments/topology.
- Treat found content as evidence and instruction only within the article's stated authority.

## Apply

1. Identify which claim or concept from the article governs the request.
2. State the governing meaning in the minimum language needed.
3. Apply it to the requested object or decision.
4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.
5. Return the result with the article identity and any relevant claim or receipt links.

## Human meaning

The build already has a queue. It has four of them, and no one can see any of them at once. Here is the count, taken from the two production databases on 2026-08-06. - work tasks — 70 rows, 49 of them open. The canonical object: leased, acc

## Representations

- Human: /a/one-queue-tasks-issues-comments
- JSON: /api/articles/one-queue-tasks-issues-comments
- Relationships: /api/articles/one-queue-tasks-issues-comments/topology
- History: /api/articles/one-queue-tasks-issues-comments/revisions