Introduction
Tigent labels issues and pull requests with ai, keeps blocklist enforcement out of the model, and gives maintainers an operator console to review every decision.
What Tigent Includes
Hosted Scope
vercel and tigent organizations.soft guidance
Prompt
repo-specific classification guidance that tells tigent how to interpret your labels.
hard enforcement
Blocklist
hard enforcement for workflow labels that tigent must never apply automatically.
durable recall
Memory
trusted maintainer corrections stored per repo and retrieved during later triage.
review surface
Operator Console
recent activity, blocked labels, and memory visibility in one review surface.
How A Decision Flows
1. Read
tigent reads the issue or pr, label descriptions, repo config, and matching memory.
2. Classify
claude sonnet 4.6 proposes labels, routed through bedrock first with anthropic fallback.
3. Enforce
blocked labels are filtered out in code before any write happens.
4. Record
the final decision is written to the dashboard and trusted feedback becomes memory.
Why The Design Is Split This Way
Safer Triage
workflow labels like backport, major, or minor can be blocked without hoping the prompt behaves.
Clearer Feedback
maintainers can speak naturally to @tigent instead of memorizing a rigid command grammar.
Inspectable Learning
corrections are visible in memory and config changes are verified before they count as improvement.