Skip to content
Discussion options

You must be logged in to vote

Fail open. The classifier is a UX guardrail that keeps the chat on-topic, not a security control, so its failure mode should not be able to break the actual feature it is guarding. If the classifier call errors out, the chat still needs to answer the users question about their code review. Blocking every message whenever the classifier (a separate API call) has a bad moment would turn an occasional network hiccup into a full outage of the chat feature itself, which is a worse failure than occasionally letting an off-topic message through. The cost of fail-closed (the whole feature breaks) is much higher than the cost of fail-open (the classifier misses a message here and there).

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by ApparentlyTejas
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant