Issue intake triage
Screen new issues for vulnerabilities, label them, check for duplicates, and ask for what's missing.
Scenario paths
Pick a predefined path to highlight it through the chain. No model is called; outcomes are illustrative.
- Steps
- Endpoints
- Private security report
- Feedback triage
- Move to Q&A
- Docs label
- Suggest duplicate
- Ready for triage
- Ask the reporter
- Maintainer
What each endpoint means
Private security report · Human review
Hidden and moved to your private reporting channel; the reporter is pointed to the security policy.
Feedback triage · Handoff
Feature requests join the product feedback flow.
Continues in Feedback triageMove to Q&A · Automated
Labelled as a question and suggested for the discussion forum.
Docs label · Automated
Labelled for the documentation backlog.
Suggest duplicate · Automated
Comments with the likely duplicate; a maintainer or the reporter closes it.
Ready for triage · Automated
Labelled ready for a maintainer to prioritize.
Ask the reporter · Automated
Asks for the most important missing detail.
Maintainer · Human review
A maintainer reads and labels it.
Steps
Move vulnerability reports out of public view first.
- Move to private reportPrivate security report
- Maintainer checksMaintainer
- Continue intakeIssue report type
Question, inputs and notes
Asks:Does this report describe a possible security vulnerability in the project?
Receives
- Inputtitle
- Inputbody
- Issue report typeChoice
Label the issue.
- BugDuplicate issue signal
- Feature requestFeedback triage
- Usage questionMove to Q&A
- DocumentationDocs label
- Maintainer triageMaintainer
Question, inputs and notes
Asks:What kind of issue is this?
Receives
- Inputtitle and body
- Inputtemplate
Compare with similar open issues.
- Suggest duplicateSuggest duplicate
- Not a duplicateUnclearBug report completeness
Question, inputs and notes
Asks:Does the new issue describe the same problem as one of the candidates?
Receives
- Inputtitle and body
- Inputcandidates
- Bug report completenessChoice
Ask for what a maintainer needs.
- Ready for triageReady for triage
- Ask for reproductionAsk for environmentAsk what was expectedAsk the reporter
- Maintainer triageMaintainer
Question, inputs and notes
Asks:What, if anything, is this bug report missing that a maintainer needs to reproduce it?
Receives
- Inputtitle and body
- From step 2Type: bug
About this chain
Goal and input
Every issue ends privately reported, labelled for docs or Q&A, linked to a duplicate, ready for triage, waiting on the reporter, or with a maintainer.
The new issue, the template used, and similar issues from search.
- title
- Issue title.
- body
- Issue body.
- template
- Template picked by the reporter.
- candidates
- Similar open issues from your search.
How it runs
- The security screen runs before any public comment or label, so automated replies never repeat vulnerability details.
- No issue is closed automatically. Duplicate suggestions are comments; closing is a person's decision.
Sources (3)
Primary documentation this chain builds on.
- SourcedTypeSafe docs · PatternScreen with a Noul first
- SourcedTypeSafe docs · DocumentationSystem One
- SourcedTypeSafe docs · CookbookGuardrails for LLMs