Triage
Private PreviewClassify inbound work, reduce duplicates, and route items to the right owner or workflow.
Triage is the intake stage of the Software Factory. It turns incoming issues, threads, and alerts into routed engineering work with enough context for a Droid or teammate to act.
Use Triage when the team needs a repeatable path from "someone reported something" to "the right workflow owns it."
Triage is in Private Preview. To request access, fill out the form at factory.ai/contact or contact your Factory account team.
What Triage does
Triage connects intake signals to Software Factory stages:
- 1
- 2Classify the request by type, priority, repository, owning team, and likely workflow.
- 3Reduce duplicates by comparing new work against recent issues, related threads, and open pull requests.
- 4Route the item to a teammate, queue, Droid session, or Automation.
- 5Measure throughput, backlog, and cycle time in the Software Factory dashboard.
When to use it
Turn team threads into tracked engineering work with the right context attached.
Group duplicate reports, identify the likely owning surface, and start remediation.
Send repeatable triage decisions into scheduled or trigger-based workflows.
Triage metrics
The Software Factory dashboard tracks both intake volume and routing health.
| Metric | What it indicates |
|---|---|
| Throughput | How many requests Triage classified in the selected time range. |
| Backlog | Items still waiting for an owner, duplicate decision, or next workflow. |
| Cycle time | Time from intake signal to routing decision. |
| Health | Whether the connected intake sources and automations are ready to run. |
What to connect first
Start with the systems where work already arrives:
| Source | What Triage reads | Common route |
|---|---|---|
| Linear | Issue title, description, comments, labels, project, and status | Owning team, implementation session, or duplicate closure |
| Slack | Channel, thread, links, and requester context | Incident response, bug investigation, or follow-up issue |
| GitHub | Repository, issue, pull request, and CI context | Code review, QA, security review, or AutoWiki |
After the first source is connected, add a narrow automation before broadening coverage. A good first workflow is "classify new bugs in one team queue and route only high-confidence matches."