feat: add Meeting Worthiness Judge agent sample - #12
Merged
Conversation
A comedic hackathon agent that evaluates whether a meeting deserves to exist. Uses five tools (CountAttendees, AnalyzeAgenda, CheckIfCouldBeAnEmail, EstimateProductivityLoss, SuggestAlternative) to gather "evidence" and delivers a formal courtroom-style verdict. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
GarrettBeatty
requested review from
normj and
philasmar
and removed request for
a team
May 6, 2026 15:38
GarrettBeatty
added a commit
that referenced
this pull request
Aug 18, 2026
Lets the policy backend evaluate tool-call context with inline guardrail checks (content filter, prompt attack, sensitive information) so no pre-created Bedrock guardrail is required, streamlining onboarding (design decision #12). - Bumps AWSSDK.BedrockRuntime to 4.0.101.1 (adds InvokeGuardrailChecks). - GuardrailChecksOptions: categories/entities to check plus severity/confidence thresholds. BedrockGuardrailsPolicyOptions.InlineChecks selects the mode. - BedrockGuardrailClient.InvokeChecksAsync builds/times the request; GuardrailResponseMapper.ChecksTripped maps per-check scores to a deny (fail-safe: a finding with no score is treated as tripped). - The backend uses ApplyGuardrail when GuardrailId is set, else inline checks; ctor and setup validation accept either. Detection only (no masking), so PII sanitization stays on ApplyGuardrail. Tests cover mode selection, allow/deny by threshold, and ctor validation.
GarrettBeatty
added a commit
that referenced
this pull request
Aug 18, 2026
Lets the policy backend evaluate tool-call context with inline guardrail checks (content filter, prompt attack, sensitive information) so no pre-created Bedrock guardrail is required, streamlining onboarding (design decision #12). - Bumps AWSSDK.BedrockRuntime to 4.0.101.1 (adds InvokeGuardrailChecks). - GuardrailChecksOptions: categories/entities to check plus severity/confidence thresholds. BedrockGuardrailsPolicyOptions.InlineChecks selects the mode. - BedrockGuardrailClient.InvokeChecksAsync builds/times the request; GuardrailResponseMapper.ChecksTripped maps per-check scores to a deny (fail-safe: a finding with no score is treated as tripped). - The backend uses ApplyGuardrail when GuardrailId is set, else inline checks; ctor and setup validation accept either. Detection only (no masking), so PII sanitization stays on ApplyGuardrail. Tests cover mode selection, allow/deny by threshold, and ctor validation.
GarrettBeatty
added a commit
that referenced
this pull request
Aug 19, 2026
Lets the policy backend evaluate tool-call context with inline guardrail checks (content filter, prompt attack, sensitive information) so no pre-created Bedrock guardrail is required, streamlining onboarding (design decision #12). - Bumps AWSSDK.BedrockRuntime to 4.0.101.1 (adds InvokeGuardrailChecks). - GuardrailChecksOptions: categories/entities to check plus severity/confidence thresholds. BedrockGuardrailsPolicyOptions.InlineChecks selects the mode. - BedrockGuardrailClient.InvokeChecksAsync builds/times the request; GuardrailResponseMapper.ChecksTripped maps per-check scores to a deny (fail-safe: a finding with no score is treated as tripped). - The backend uses ApplyGuardrail when GuardrailId is set, else inline checks; ctor and setup validation accept either. Detection only (no masking), so PII sanitization stays on ApplyGuardrail. Tests cover mode selection, allow/deny by threshold, and ctor validation.
GarrettBeatty
added a commit
that referenced
this pull request
Aug 19, 2026
Lets the policy backend evaluate tool-call context with inline guardrail checks (content filter, prompt attack, sensitive information) so no pre-created Bedrock guardrail is required, streamlining onboarding (design decision #12). - Bumps AWSSDK.BedrockRuntime to 4.0.101.1 (adds InvokeGuardrailChecks). - GuardrailChecksOptions: categories/entities to check plus severity/confidence thresholds. BedrockGuardrailsPolicyOptions.InlineChecks selects the mode. - BedrockGuardrailClient.InvokeChecksAsync builds/times the request; GuardrailResponseMapper.ChecksTripped maps per-check scores to a deny (fail-safe: a finding with no score is treated as tripped). - The backend uses ApplyGuardrail when GuardrailId is set, else inline checks; ctor and setup validation accept either. Detection only (no masking), so PII sanitization stays on ApplyGuardrail. Tests cover mode selection, allow/deny by threshold, and ctor validation.
GarrettBeatty
added a commit
that referenced
this pull request
Aug 19, 2026
Lets the policy backend evaluate tool-call context with inline guardrail checks (content filter, prompt attack, sensitive information) so no pre-created Bedrock guardrail is required, streamlining onboarding (design decision #12). - Bumps AWSSDK.BedrockRuntime to 4.0.101.1 (adds InvokeGuardrailChecks). - GuardrailChecksOptions: categories/entities to check plus severity/confidence thresholds. BedrockGuardrailsPolicyOptions.InlineChecks selects the mode. - BedrockGuardrailClient.InvokeChecksAsync builds/times the request; GuardrailResponseMapper.ChecksTripped maps per-check scores to a deny (fail-safe: a finding with no score is treated as tripped). - The backend uses ApplyGuardrail when GuardrailId is set, else inline checks; ctor and setup validation accept either. Detection only (no masking), so PII sanitization stays on ApplyGuardrail. Tests cover mode selection, allow/deny by threshold, and ctor validation.
GarrettBeatty
added a commit
that referenced
this pull request
Aug 19, 2026
Lets the policy backend evaluate tool-call context with inline guardrail checks (content filter, prompt attack, sensitive information) so no pre-created Bedrock guardrail is required, streamlining onboarding (design decision #12). - Bumps AWSSDK.BedrockRuntime to 4.0.101.1 (adds InvokeGuardrailChecks). - GuardrailChecksOptions: categories/entities to check plus severity/confidence thresholds. BedrockGuardrailsPolicyOptions.InlineChecks selects the mode. - BedrockGuardrailClient.InvokeChecksAsync builds/times the request; GuardrailResponseMapper.ChecksTripped maps per-check scores to a deny (fail-safe: a finding with no score is treated as tripped). - The backend uses ApplyGuardrail when GuardrailId is set, else inline checks; ctor and setup validation accept either. Detection only (no masking), so PII sanitization stays on ApplyGuardrail. Tests cover mode selection, allow/deny by threshold, and ctor validation.
GarrettBeatty
added a commit
that referenced
this pull request
Aug 19, 2026
Lets the policy backend evaluate tool-call context with inline guardrail checks (content filter, prompt attack, sensitive information) so no pre-created Bedrock guardrail is required, streamlining onboarding (design decision #12). - Bumps AWSSDK.BedrockRuntime to 4.0.101.1 (adds InvokeGuardrailChecks). - GuardrailChecksOptions: categories/entities to check plus severity/confidence thresholds. BedrockGuardrailsPolicyOptions.InlineChecks selects the mode. - BedrockGuardrailClient.InvokeChecksAsync builds/times the request; GuardrailResponseMapper.ChecksTripped maps per-check scores to a deny (fail-safe: a finding with no score is treated as tripped). - The backend uses ApplyGuardrail when GuardrailId is set, else inline checks; ctor and setup validation accept either. Detection only (no masking), so PII sanitization stays on ApplyGuardrail. Tests cover mode selection, allow/deny by threshold, and ctor validation.
GarrettBeatty
added a commit
that referenced
this pull request
Aug 19, 2026
Lets the policy backend evaluate tool-call context with inline guardrail checks (content filter, prompt attack, sensitive information) so no pre-created Bedrock guardrail is required, streamlining onboarding (design decision #12). - Bumps AWSSDK.BedrockRuntime to 4.0.101.1 (adds InvokeGuardrailChecks). - GuardrailChecksOptions: categories/entities to check plus severity/confidence thresholds. BedrockGuardrailsPolicyOptions.InlineChecks selects the mode. - BedrockGuardrailClient.InvokeChecksAsync builds/times the request; GuardrailResponseMapper.ChecksTripped maps per-check scores to a deny (fail-safe: a finding with no score is treated as tripped). - The backend uses ApplyGuardrail when GuardrailId is set, else inline checks; ctor and setup validation accept either. Detection only (no masking), so PII sanitization stays on ApplyGuardrail. Tests cover mode selection, allow/deny by threshold, and ctor validation.
GarrettBeatty
added a commit
that referenced
this pull request
Aug 21, 2026
Lets the policy backend evaluate tool-call context with inline guardrail checks (content filter, prompt attack, sensitive information) so no pre-created Bedrock guardrail is required, streamlining onboarding (design decision #12). - Bumps AWSSDK.BedrockRuntime to 4.0.101.1 (adds InvokeGuardrailChecks). - GuardrailChecksOptions: categories/entities to check plus severity/confidence thresholds. BedrockGuardrailsPolicyOptions.InlineChecks selects the mode. - BedrockGuardrailClient.InvokeChecksAsync builds/times the request; GuardrailResponseMapper.ChecksTripped maps per-check scores to a deny (fail-safe: a finding with no score is treated as tripped). - The backend uses ApplyGuardrail when GuardrailId is set, else inline checks; ctor and setup validation accept either. Detection only (no masking), so PII sanitization stays on ApplyGuardrail. Tests cover mode selection, allow/deny by threshold, and ctor validation.
GarrettBeatty
added a commit
that referenced
this pull request
Aug 21, 2026
Lets the policy backend evaluate tool-call context with inline guardrail checks (content filter, prompt attack, sensitive information) so no pre-created Bedrock guardrail is required, streamlining onboarding (design decision #12). - Bumps AWSSDK.BedrockRuntime to 4.0.101.1 (adds InvokeGuardrailChecks). - GuardrailChecksOptions: categories/entities to check plus severity/confidence thresholds. BedrockGuardrailsPolicyOptions.InlineChecks selects the mode. - BedrockGuardrailClient.InvokeChecksAsync builds/times the request; GuardrailResponseMapper.ChecksTripped maps per-check scores to a deny (fail-safe: a finding with no score is treated as tripped). - The backend uses ApplyGuardrail when GuardrailId is set, else inline checks; ctor and setup validation accept either. Detection only (no masking), so PII sanitization stays on ApplyGuardrail. Tests cover mode selection, allow/deny by threshold, and ctor validation.
GarrettBeatty
added a commit
that referenced
this pull request
Aug 24, 2026
Lets the policy backend evaluate tool-call context with inline guardrail checks (content filter, prompt attack, sensitive information) so no pre-created Bedrock guardrail is required, streamlining onboarding (design decision #12). - Bumps AWSSDK.BedrockRuntime to 4.0.101.1 (adds InvokeGuardrailChecks). - GuardrailChecksOptions: categories/entities to check plus severity/confidence thresholds. BedrockGuardrailsPolicyOptions.InlineChecks selects the mode. - BedrockGuardrailClient.InvokeChecksAsync builds/times the request; GuardrailResponseMapper.ChecksTripped maps per-check scores to a deny (fail-safe: a finding with no score is treated as tripped). - The backend uses ApplyGuardrail when GuardrailId is set, else inline checks; ctor and setup validation accept either. Detection only (no masking), so PII sanitization stays on ApplyGuardrail. Tests cover mode selection, allow/deny by threshold, and ctor validation.
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
1 participant
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.
Summary
Test plan
dotnet build sampleapps/MeetingJudgeAgent/MeetingJudgeAgent.csprojcompiles successfullydotnet run --project sampleapps/MeetingJudgeAgentstarts on port 8080/invocationswith a meeting description returns a comedic verdict/pingreturns healthy status🤖 Generated with Claude Code