Create Automated Reasoning Policy Test Case

bedrock_create_automated_reasoning_policy_test_case

R Documentation

Creates a test for an Automated Reasoning policy

Description

Creates a test for an Automated Reasoning policy. Tests validate that your policy works as expected by providing sample inputs and expected outcomes. Use tests to verify policy behavior before deploying to production.

Usage

bedrock_create_automated_reasoning_policy_test_case(policyArn,
  guardContent, queryContent, expectedAggregatedFindingsResult,
  clientRequestToken, confidenceThreshold)

Arguments

policyArn	[required] The Amazon Resource Name (ARN) of the Automated Reasoning policy for which to create the test.
guardContent	[required] The output content that's validated by the Automated Reasoning policy. This represents the foundation model response that will be checked for accuracy.
queryContent	The input query or prompt that generated the content. This provides context for the validation.
expectedAggregatedFindingsResult	[required] The expected result of the Automated Reasoning check. Valid values include: , TOO_COMPLEX, and NO_TRANSLATIONS. VALID - The claims are true. The claims are implied by the premises and the Automated Reasoning policy. Given the Automated Reasoning policy and premises, it is not possible for these claims to be false. In other words, there are no alternative answers that are true that contradict the claims. INVALID - The claims are false. The claims are not implied by the premises and Automated Reasoning policy. Furthermore, there exists different claims that are consistent with the premises and Automated Reasoning policy. SATISFIABLE - The claims can be true or false. It depends on what assumptions are made for the claim to be implied from the premises and Automated Reasoning policy rules. In this situation, different assumptions can make input claims false and alternative claims true. IMPOSSIBLE - Automated Reasoning can’t make a statement about the claims. This can happen if the premises are logically incorrect, or if there is a conflict within the Automated Reasoning policy itself. TRANSLATION_AMBIGUOUS - Detected an ambiguity in the translation meant it would be unsound to continue with validity checking. Additional context or follow-up questions might be needed to get translation to succeed. TOO_COMPLEX - The input contains too much information for Automated Reasoning to process within its latency limits. NO_TRANSLATIONS - Identifies that some or all of the input prompt wasn't translated into logic. This can happen if the input isn't relevant to the Automated Reasoning policy, or if the policy doesn't have variables to model relevant input. If Automated Reasoning can't translate anything, you get a single NO_TRANSLATIONS finding. You might also see a NO_TRANSLATIONS (along with other findings) if some part of the validation isn't translated.
clientRequestToken	A unique, case-sensitive identifier to ensure that the operation completes no more than one time. If this token matches a previous request, Amazon Bedrock ignores the request, but does not return an error.
confidenceThreshold	The minimum confidence level for logic validation. Content that meets the threshold is considered a high-confidence finding that can be validated.

Value

A list with the following syntax:

list(
  policyArn = "string",
  testCaseId = "string"
)

Request syntax

svc$create_automated_reasoning_policy_test_case(
  policyArn = "string",
  guardContent = "string",
  queryContent = "string",
  expectedAggregatedFindingsResult = "VALID"|"INVALID"|"SATISFIABLE"|"IMPOSSIBLE"|"TRANSLATION_AMBIGUOUS"|"TOO_COMPLEX"|"NO_TRANSLATION",
  clientRequestToken = "string",
  confidenceThreshold = 123.0
)