jev-confidence-gated-triage-cdk: Confidence-gated ticket triage with TypeSafe Jev - #3310
Open
NithinChandranR-AWS wants to merge 1 commit into
Conversation
… pattern
Auto-triage support tickets with the TypeSafe Jev System One model. One
AWS Lambda function sends the ticket plus three typed questions (choice,
score, noul) to Jev in a single call and reads back calibrated confidence
per answer; an AWS Step Functions Choice state branches on that confidence
to auto-route, page security on-call via Amazon SNS, or fall through to an
Amazon SQS human-review queue.
Request and response follow the TypeSafe System One contract: questions
carry instructions, choice lists options in a criteria object, score lists
ordered levels in a criteria array, and noul states a proposition. The
handler normalizes each typed answer into {value, confidence} for the gate,
deriving a noul's confidence from |p - 0.5| * 2.
The ingest endpoint requires an Amazon API Gateway API key (with a usage
plan) so the paid TypeSafe Jev calls and security pages cannot be driven
anonymously.
NithinChandranR-AWS
force-pushed
the
NithinChandranR-AWS-feature-jev-confidence-gated-triage-cdk
branch
from
September 21, 2026 04:44
0ce9cc8 to
205c327
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Auto-triage support tickets with the TypeSafe Jev System One model: one AWS Lambda function gets typed decisions plus calibrated confidence, and an AWS Step Functions Choice state decides whether to act.
Architecture
Amazon API Gateway (
POST /tickets, protected by an API key + usage plan) -> AWS Lambda (one HTTPS call to TypeSafe Jev: achoicefor department, ascorefor urgency, anoulfor whether the ticket reports a security incident) -> AWS Step Functions Express. The Choice state is the confidence gate: it auto-routes when the department and urgency confidences clear their thresholds, pages on-call via Amazon SNS when the security answer is true with confidence >= 0.9, and otherwise sends the ticket to an Amazon SQS human-review queue (backed by a dead-letter queue) with the full Jev output attached. The Jev API key is held in AWS Secrets Manager.Verified
cdk synthpasses; IAM scoped to specific resource ARNs (no application-resource wildcards)instructions;choiceuses acriteriaobject;scoreuses an orderedcriteriaarray;noulstates a proposition and returns a probability), verified against https://docs.typesafe.ai/api