@mochabug/adaptkit 1.0.0-rc.13 → 1.0.0-rc.14

package/bin/genproto/buf/validate/validate_pb.d.ts

@@ -1,4 +1,4 @@
-import type { GenEnum, GenExtension, GenFile, GenMessage } from "@bufbuild/protobuf/codegenv1";
+import type { GenEnum, GenExtension, GenFile, GenMessage } from "@bufbuild/protobuf/codegenv2";
 import type { Duration, DurationJson, FieldDescriptorProto_Type, FieldDescriptorProto_TypeJson, FieldOptions, MessageOptions, OneofOptions, Timestamp, TimestampJson } from "@bufbuild/protobuf/wkt";
 import type { Message } from "@bufbuild/protobuf";
 /**
@@ -6,10 +6,10 @@ import type { Message } from "@bufbuild/protobuf";
  */
 export declare const file_buf_validate_validate: GenFile;
 /**
- * `Constraint` represents a validation rule written in the Common Expression
- * Language (CEL) syntax. Each Constraint includes a unique identifier, an
+ * `Rule` represents a validation rule written in the Common Expression
+ * Language (CEL) syntax. Each Rule includes a unique identifier, an
  * optional error message, and the CEL expression to evaluate. For more
- * information on CEL, [see our documentation](https://github.com/bufbuild/protovalidate/blob/main/docs/cel.md).
+ * information, [see our documentation](https://buf.build/docs/protovalidate/schemas/custom-rules/).
  *
  * ```proto
  * message Foo {
@@ -22,11 +22,11 @@ export declare const file_buf_validate_validate: GenFile;
  * }
  * ```
  *
- * @generated from message buf.validate.Constraint
+ * @generated from message buf.validate.Rule
  */
-export type Constraint = Message<"buf.validate.Constraint"> & {
+export type Rule = Message<"buf.validate.Rule"> & {
     /**
-     * `id` is a string that serves as a machine-readable name for this Constraint.
+     * `id` is a string that serves as a machine-readable name for this Rule.
      * It should be unique within its scope, which could be either a message or a field.
      *
      * @generated from field: optional string id = 1;
@@ -34,7 +34,7 @@ export type Constraint = Message<"buf.validate.Constraint"> & {
     id: string;
     /**
      * `message` is an optional field that provides a human-readable error message
-     * for this Constraint when the CEL expression evaluates to false. If a
+     * for this Rule when the CEL expression evaluates to false. If a
      * non-empty message is provided, any strings resulting from the CEL
      * expression evaluation are ignored.
      *
@@ -52,10 +52,10 @@ export type Constraint = Message<"buf.validate.Constraint"> & {
     expression: string;
 };
 /**
- * `Constraint` represents a validation rule written in the Common Expression
- * Language (CEL) syntax. Each Constraint includes a unique identifier, an
+ * `Rule` represents a validation rule written in the Common Expression
+ * Language (CEL) syntax. Each Rule includes a unique identifier, an
  * optional error message, and the CEL expression to evaluate. For more
- * information on CEL, [see our documentation](https://github.com/bufbuild/protovalidate/blob/main/docs/cel.md).
+ * information, [see our documentation](https://buf.build/docs/protovalidate/schemas/custom-rules/).
  *
  * ```proto
  * message Foo {
@@ -68,11 +68,11 @@ export type Constraint = Message<"buf.validate.Constraint"> & {
  * }
  * ```
  *
- * @generated from message buf.validate.Constraint
+ * @generated from message buf.validate.Rule
  */
-export type ConstraintJson = {
+export type RuleJson = {
     /**
-     * `id` is a string that serves as a machine-readable name for this Constraint.
+     * `id` is a string that serves as a machine-readable name for this Rule.
      * It should be unique within its scope, which could be either a message or a field.
      *
      * @generated from field: optional string id = 1;
@@ -80,7 +80,7 @@ export type ConstraintJson = {
     id?: string;
     /**
      * `message` is an optional field that provides a human-readable error message
-     * for this Constraint when the CEL expression evaluates to false. If a
+     * for this Rule when the CEL expression evaluates to false. If a
      * non-empty message is provided, any strings resulting from the CEL
      * expression evaluation are ignored.
      *
@@ -98,17 +98,19 @@ export type ConstraintJson = {
     expression?: string;
 };
 /**
- * Describes the message buf.validate.Constraint.
- * Use `create(ConstraintSchema)` to create a new message.
+ * Describes the message buf.validate.Rule.
+ * Use `create(RuleSchema)` to create a new message.
  */
-export declare const ConstraintSchema: GenMessage<Constraint, ConstraintJson>;
+export declare const RuleSchema: GenMessage<Rule, {
+    jsonType: RuleJson;
+}>;
 /**
- * MessageConstraints represents validation rules that are applied to the entire message.
- * It includes disabling options and a list of Constraint messages representing Common Expression Language (CEL) validation rules.
+ * MessageRules represents validation rules that are applied to the entire message.
+ * It includes disabling options and a list of Rule messages representing Common Expression Language (CEL) validation rules.
  *
- * @generated from message buf.validate.MessageConstraints
+ * @generated from message buf.validate.MessageRules
  */
-export type MessageConstraints = Message<"buf.validate.MessageConstraints"> & {
+export type MessageRules = Message<"buf.validate.MessageRules"> & {
     /**
      * `disabled` is a boolean flag that, when set to true, nullifies any validation rules for this message.
      * This includes any fields within the message that would otherwise support validation.
@@ -124,9 +126,9 @@ export type MessageConstraints = Message<"buf.validate.MessageConstraints"> & {
      */
     disabled: boolean;
     /**
-     * `cel` is a repeated field of type Constraint. Each Constraint specifies a validation rule to be applied to this message.
-     * These constraints are written in Common Expression Language (CEL) syntax. For more information on
-     * CEL, [see our documentation](https://github.com/bufbuild/protovalidate/blob/main/docs/cel.md).
+     * `cel` is a repeated field of type Rule. Each Rule specifies a validation rule to be applied to this message.
+     * These rules are written in Common Expression Language (CEL) syntax. For more information,
+     * [see our documentation](https://buf.build/docs/protovalidate/schemas/custom-rules/).
      *
      *
      * ```proto
@@ -141,17 +143,56 @@ export type MessageConstraints = Message<"buf.validate.MessageConstraints"> & {
      * }
      * ```
      *
-     * @generated from field: repeated buf.validate.Constraint cel = 3;
+     * @generated from field: repeated buf.validate.Rule cel = 3;
      */
-    cel: Constraint[];
+    cel: Rule[];
+    /**
+     * `oneof` is a repeated field of type MessageOneofRule that specifies a list of fields
+     * of which at most one can be present. If `required` is also specified, then exactly one
+     * of the specified fields _must_ be present.
+     *
+     * This will enforce oneof-like constraints with a few features not provided by
+     * actual Protobuf oneof declarations:
+     *   1. Repeated and map fields are allowed in this validation. In a Protobuf oneof,
+     *      only scalar fields are allowed.
+     *   2. Fields with implicit presence are allowed. In a Protobuf oneof, all member
+     *      fields have explicit presence. This means that, for the purpose of determining
+     *      how many fields are set, explicitly setting such a field to its zero value is
+     *      effectively the same as not setting it at all.
+     *   3. This will always generate validation errors for a message unmarshalled from
+     *      serialized data that sets more than one field. With a Protobuf oneof, when
+     *      multiple fields are present in the serialized form, earlier values are usually
+     *      silently ignored when unmarshalling, with only the last field being set when
+     *      unmarshalling completes.
+     *
+     * Note that adding a field to a `oneof` will also set the IGNORE_IF_UNPOPULATED on the fields. This means
+     * only the field that is set will be validated and the unset fields are not validated according to the field rules.
+     * This behavior can be overridden by setting `ignore` against a field.
+     *
+     * ```proto
+     * message MyMessage {
+     *   // Only one of `field1` or `field2` _can_ be present in this message.
+     *   option (buf.validate.message).oneof = { fields: ["field1", "field2"] };
+     *   // Exactly one of `field3` or `field4` _must_ be present in this message.
+     *   option (buf.validate.message).oneof = { fields: ["field3", "field4"], required: true };
+     *   string field1 = 1;
+     *   bytes field2 = 2;
+     *   bool field3 = 3;
+     *   int32 field4 = 4;
+     * }
+     * ```
+     *
+     * @generated from field: repeated buf.validate.MessageOneofRule oneof = 4;
+     */
+    oneof: MessageOneofRule[];
 };
 /**
- * MessageConstraints represents validation rules that are applied to the entire message.
- * It includes disabling options and a list of Constraint messages representing Common Expression Language (CEL) validation rules.
+ * MessageRules represents validation rules that are applied to the entire message.
+ * It includes disabling options and a list of Rule messages representing Common Expression Language (CEL) validation rules.
  *
- * @generated from message buf.validate.MessageConstraints
+ * @generated from message buf.validate.MessageRules
  */
-export type MessageConstraintsJson = {
+export type MessageRulesJson = {
     /**
      * `disabled` is a boolean flag that, when set to true, nullifies any validation rules for this message.
      * This includes any fields within the message that would otherwise support validation.
@@ -167,9 +208,9 @@ export type MessageConstraintsJson = {
      */
     disabled?: boolean;
     /**
-     * `cel` is a repeated field of type Constraint. Each Constraint specifies a validation rule to be applied to this message.
-     * These constraints are written in Common Expression Language (CEL) syntax. For more information on
-     * CEL, [see our documentation](https://github.com/bufbuild/protovalidate/blob/main/docs/cel.md).
+     * `cel` is a repeated field of type Rule. Each Rule specifies a validation rule to be applied to this message.
+     * These rules are written in Common Expression Language (CEL) syntax. For more information,
+     * [see our documentation](https://buf.build/docs/protovalidate/schemas/custom-rules/).
      *
      *
      * ```proto
@@ -184,26 +225,112 @@ export type MessageConstraintsJson = {
      * }
      * ```
      *
-     * @generated from field: repeated buf.validate.Constraint cel = 3;
+     * @generated from field: repeated buf.validate.Rule cel = 3;
+     */
+    cel?: RuleJson[];
+    /**
+     * `oneof` is a repeated field of type MessageOneofRule that specifies a list of fields
+     * of which at most one can be present. If `required` is also specified, then exactly one
+     * of the specified fields _must_ be present.
+     *
+     * This will enforce oneof-like constraints with a few features not provided by
+     * actual Protobuf oneof declarations:
+     *   1. Repeated and map fields are allowed in this validation. In a Protobuf oneof,
+     *      only scalar fields are allowed.
+     *   2. Fields with implicit presence are allowed. In a Protobuf oneof, all member
+     *      fields have explicit presence. This means that, for the purpose of determining
+     *      how many fields are set, explicitly setting such a field to its zero value is
+     *      effectively the same as not setting it at all.
+     *   3. This will always generate validation errors for a message unmarshalled from
+     *      serialized data that sets more than one field. With a Protobuf oneof, when
+     *      multiple fields are present in the serialized form, earlier values are usually
+     *      silently ignored when unmarshalling, with only the last field being set when
+     *      unmarshalling completes.
+     *
+     * Note that adding a field to a `oneof` will also set the IGNORE_IF_UNPOPULATED on the fields. This means
+     * only the field that is set will be validated and the unset fields are not validated according to the field rules.
+     * This behavior can be overridden by setting `ignore` against a field.
+     *
+     * ```proto
+     * message MyMessage {
+     *   // Only one of `field1` or `field2` _can_ be present in this message.
+     *   option (buf.validate.message).oneof = { fields: ["field1", "field2"] };
+     *   // Exactly one of `field3` or `field4` _must_ be present in this message.
+     *   option (buf.validate.message).oneof = { fields: ["field3", "field4"], required: true };
+     *   string field1 = 1;
+     *   bytes field2 = 2;
+     *   bool field3 = 3;
+     *   int32 field4 = 4;
+     * }
+     * ```
+     *
+     * @generated from field: repeated buf.validate.MessageOneofRule oneof = 4;
+     */
+    oneof?: MessageOneofRuleJson[];
+};
+/**
+ * Describes the message buf.validate.MessageRules.
+ * Use `create(MessageRulesSchema)` to create a new message.
+ */
+export declare const MessageRulesSchema: GenMessage<MessageRules, {
+    jsonType: MessageRulesJson;
+}>;
+/**
+ * @generated from message buf.validate.MessageOneofRule
+ */
+export type MessageOneofRule = Message<"buf.validate.MessageOneofRule"> & {
+    /**
+     * A list of field names to include in the oneof. All field names must be
+     * defined in the message. At least one field must be specified, and
+     * duplicates are not permitted.
+     *
+     * @generated from field: repeated string fields = 1;
+     */
+    fields: string[];
+    /**
+     * If true, one of the fields specified _must_ be set.
+     *
+     * @generated from field: optional bool required = 2;
+     */
+    required: boolean;
+};
+/**
+ * @generated from message buf.validate.MessageOneofRule
+ */
+export type MessageOneofRuleJson = {
+    /**
+     * A list of field names to include in the oneof. All field names must be
+     * defined in the message. At least one field must be specified, and
+     * duplicates are not permitted.
+     *
+     * @generated from field: repeated string fields = 1;
      */
-    cel?: ConstraintJson[];
+    fields?: string[];
+    /**
+     * If true, one of the fields specified _must_ be set.
+     *
+     * @generated from field: optional bool required = 2;
+     */
+    required?: boolean;
 };
 /**
- * Describes the message buf.validate.MessageConstraints.
- * Use `create(MessageConstraintsSchema)` to create a new message.
+ * Describes the message buf.validate.MessageOneofRule.
+ * Use `create(MessageOneofRuleSchema)` to create a new message.
  */
-export declare const MessageConstraintsSchema: GenMessage<MessageConstraints, MessageConstraintsJson>;
+export declare const MessageOneofRuleSchema: GenMessage<MessageOneofRule, {
+    jsonType: MessageOneofRuleJson;
+}>;
 /**
- * The `OneofConstraints` message type enables you to manage constraints for
+ * The `OneofRules` message type enables you to manage rules for
  * oneof fields in your protobuf messages.
  *
- * @generated from message buf.validate.OneofConstraints
+ * @generated from message buf.validate.OneofRules
  */
-export type OneofConstraints = Message<"buf.validate.OneofConstraints"> & {
+export type OneofRules = Message<"buf.validate.OneofRules"> & {
     /**
      * If `required` is true, exactly one field of the oneof must be present. A
      * validation error is returned if no fields in the oneof are present. The
-     * field itself may still be a default value; further constraints
+     * field itself may still be a default value; further rules
      * should be placed on the fields themselves to ensure they are valid values,
      * such as `min_len` or `gt`.
      *
@@ -224,16 +351,16 @@ export type OneofConstraints = Message<"buf.validate.OneofConstraints"> & {
     required: boolean;
 };
 /**
- * The `OneofConstraints` message type enables you to manage constraints for
+ * The `OneofRules` message type enables you to manage rules for
  * oneof fields in your protobuf messages.
  *
- * @generated from message buf.validate.OneofConstraints
+ * @generated from message buf.validate.OneofRules
  */
-export type OneofConstraintsJson = {
+export type OneofRulesJson = {
     /**
      * If `required` is true, exactly one field of the oneof must be present. A
      * validation error is returned if no fields in the oneof are present. The
-     * field itself may still be a default value; further constraints
+     * field itself may still be a default value; further rules
      * should be placed on the fields themselves to ensure they are valid values,
      * such as `min_len` or `gt`.
      *
@@ -254,21 +381,23 @@ export type OneofConstraintsJson = {
     required?: boolean;
 };
 /**
- * Describes the message buf.validate.OneofConstraints.
- * Use `create(OneofConstraintsSchema)` to create a new message.
+ * Describes the message buf.validate.OneofRules.
+ * Use `create(OneofRulesSchema)` to create a new message.
  */
-export declare const OneofConstraintsSchema: GenMessage<OneofConstraints, OneofConstraintsJson>;
+export declare const OneofRulesSchema: GenMessage<OneofRules, {
+    jsonType: OneofRulesJson;
+}>;
 /**
- * FieldConstraints encapsulates the rules for each type of field. Depending on
+ * FieldRules encapsulates the rules for each type of field. Depending on
  * the field, the correct set should be used to ensure proper validations.
  *
- * @generated from message buf.validate.FieldConstraints
+ * @generated from message buf.validate.FieldRules
  */
-export type FieldConstraints = Message<"buf.validate.FieldConstraints"> & {
+export type FieldRules = Message<"buf.validate.FieldRules"> & {
     /**
      * `cel` is a repeated field used to represent a textual expression
-     * in the Common Expression Language (CEL) syntax. For more information on
-     * CEL, [see our documentation](https://github.com/bufbuild/protovalidate/blob/main/docs/cel.md).
+     * in the Common Expression Language (CEL) syntax. For more information,
+     * [see our documentation](https://buf.build/docs/protovalidate/schemas/custom-rules/).
      *
      * ```proto
      * message MyMessage {
@@ -281,9 +410,9 @@ export type FieldConstraints = Message<"buf.validate.FieldConstraints"> & {
      * }
      * ```
      *
-     * @generated from field: repeated buf.validate.Constraint cel = 23;
+     * @generated from field: repeated buf.validate.Rule cel = 23;
      */
-    cel: Constraint[];
+    cel: Rule[];
     /**
      * If `required` is true, the field must be populated. A populated field can be
      * described as "serialized in the wire format," which includes:
@@ -295,6 +424,7 @@ export type FieldConstraints = Message<"buf.validate.FieldConstraints"> & {
      *   - proto2 scalar fields (both optional and required)
      * - proto3 scalar fields must be non-zero to be considered populated
      * - repeated and map fields must be non-empty to be considered populated
+     * - map keys/values and repeated items are always considered populated
      *
      * ```proto
      * message MyMessage {
@@ -325,7 +455,7 @@ export type FieldConstraints = Message<"buf.validate.FieldConstraints"> & {
      */
     ignore: Ignore;
     /**
-     * @generated from oneof buf.validate.FieldConstraints.type
+     * @generated from oneof buf.validate.FieldRules.type
      */
     type: {
         /**
@@ -465,16 +595,16 @@ export type FieldConstraints = Message<"buf.validate.FieldConstraints"> & {
     };
 };
 /**
- * FieldConstraints encapsulates the rules for each type of field. Depending on
+ * FieldRules encapsulates the rules for each type of field. Depending on
  * the field, the correct set should be used to ensure proper validations.
  *
- * @generated from message buf.validate.FieldConstraints
+ * @generated from message buf.validate.FieldRules
  */
-export type FieldConstraintsJson = {
+export type FieldRulesJson = {
     /**
      * `cel` is a repeated field used to represent a textual expression
-     * in the Common Expression Language (CEL) syntax. For more information on
-     * CEL, [see our documentation](https://github.com/bufbuild/protovalidate/blob/main/docs/cel.md).
+     * in the Common Expression Language (CEL) syntax. For more information,
+     * [see our documentation](https://buf.build/docs/protovalidate/schemas/custom-rules/).
      *
      * ```proto
      * message MyMessage {
@@ -487,9 +617,9 @@ export type FieldConstraintsJson = {
      * }
      * ```
      *
-     * @generated from field: repeated buf.validate.Constraint cel = 23;
+     * @generated from field: repeated buf.validate.Rule cel = 23;
      */
-    cel?: ConstraintJson[];
+    cel?: RuleJson[];
     /**
      * If `required` is true, the field must be populated. A populated field can be
      * described as "serialized in the wire format," which includes:
@@ -501,6 +631,7 @@ export type FieldConstraintsJson = {
      *   - proto2 scalar fields (both optional and required)
      * - proto3 scalar fields must be non-zero to be considered populated
      * - repeated and map fields must be non-empty to be considered populated
+     * - map keys/values and repeated items are always considered populated
      *
      * ```proto
      * message MyMessage {
@@ -622,21 +753,23 @@ export type FieldConstraintsJson = {
     timestamp?: TimestampRulesJson;
 };
 /**
- * Describes the message buf.validate.FieldConstraints.
- * Use `create(FieldConstraintsSchema)` to create a new message.
+ * Describes the message buf.validate.FieldRules.
+ * Use `create(FieldRulesSchema)` to create a new message.
  */
-export declare const FieldConstraintsSchema: GenMessage<FieldConstraints, FieldConstraintsJson>;
+export declare const FieldRulesSchema: GenMessage<FieldRules, {
+    jsonType: FieldRulesJson;
+}>;
 /**
- * PredefinedConstraints are custom constraints that can be re-used with
+ * PredefinedRules are custom rules that can be re-used with
  * multiple fields.
  *
- * @generated from message buf.validate.PredefinedConstraints
+ * @generated from message buf.validate.PredefinedRules
  */
-export type PredefinedConstraints = Message<"buf.validate.PredefinedConstraints"> & {
+export type PredefinedRules = Message<"buf.validate.PredefinedRules"> & {
     /**
      * `cel` is a repeated field used to represent a textual expression
-     * in the Common Expression Language (CEL) syntax. For more information on
-     * CEL, [see our documentation](https://github.com/bufbuild/protovalidate/blob/main/docs/cel.md).
+     * in the Common Expression Language (CEL) syntax. For more information,
+     * [see our documentation](https://buf.build/docs/protovalidate/schemas/predefined-rules/).
      *
      * ```proto
      * message MyMessage {
@@ -649,21 +782,21 @@ export type PredefinedConstraints = Message<"buf.validate.PredefinedConstraints"
      * }
      * ```
      *
-     * @generated from field: repeated buf.validate.Constraint cel = 1;
+     * @generated from field: repeated buf.validate.Rule cel = 1;
      */
-    cel: Constraint[];
+    cel: Rule[];
 };
 /**
- * PredefinedConstraints are custom constraints that can be re-used with
+ * PredefinedRules are custom rules that can be re-used with
  * multiple fields.
  *
- * @generated from message buf.validate.PredefinedConstraints
+ * @generated from message buf.validate.PredefinedRules
  */
-export type PredefinedConstraintsJson = {
+export type PredefinedRulesJson = {
     /**
      * `cel` is a repeated field used to represent a textual expression
-     * in the Common Expression Language (CEL) syntax. For more information on
-     * CEL, [see our documentation](https://github.com/bufbuild/protovalidate/blob/main/docs/cel.md).
+     * in the Common Expression Language (CEL) syntax. For more information,
+     * [see our documentation](https://buf.build/docs/protovalidate/schemas/predefined-rules/).
      *
      * ```proto
      * message MyMessage {
@@ -676,17 +809,19 @@ export type PredefinedConstraintsJson = {
      * }
      * ```
      *
-     * @generated from field: repeated buf.validate.Constraint cel = 1;
+     * @generated from field: repeated buf.validate.Rule cel = 1;
      */
-    cel?: ConstraintJson[];
+    cel?: RuleJson[];
 };
 /**
- * Describes the message buf.validate.PredefinedConstraints.
- * Use `create(PredefinedConstraintsSchema)` to create a new message.
+ * Describes the message buf.validate.PredefinedRules.
+ * Use `create(PredefinedRulesSchema)` to create a new message.
  */
-export declare const PredefinedConstraintsSchema: GenMessage<PredefinedConstraints, PredefinedConstraintsJson>;
+export declare const PredefinedRulesSchema: GenMessage<PredefinedRules, {
+    jsonType: PredefinedRulesJson;
+}>;
 /**
- * FloatRules describes the constraints applied to `float` values. These
+ * FloatRules describes the rules applied to `float` values. These
  * rules may also be applied to the `google.protobuf.FloatValue` Well-Known-Type.
  *
  * @generated from message buf.validate.FloatRules
@@ -843,14 +978,14 @@ export type FloatRules = Message<"buf.validate.FloatRules"> & {
     finite: boolean;
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
      * message MyFloat {
      *   float value = 1 [
      *     (buf.validate.field).float.example = 1.0,
-     *     (buf.validate.field).float.example = "Infinity"
+     *     (buf.validate.field).float.example = inf
      *   ];
      * }
      * ```
@@ -860,7 +995,7 @@ export type FloatRules = Message<"buf.validate.FloatRules"> & {
     example: number[];
 };
 /**
- * FloatRules describes the constraints applied to `float` values. These
+ * FloatRules describes the rules applied to `float` values. These
  * rules may also be applied to the `google.protobuf.FloatValue` Well-Known-Type.
  *
  * @generated from message buf.validate.FloatRules
@@ -995,14 +1130,14 @@ export type FloatRulesJson = {
     finite?: boolean;
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
      * message MyFloat {
      *   float value = 1 [
      *     (buf.validate.field).float.example = 1.0,
-     *     (buf.validate.field).float.example = "Infinity"
+     *     (buf.validate.field).float.example = inf
      *   ];
      * }
      * ```
@@ -1015,9 +1150,11 @@ export type FloatRulesJson = {
  * Describes the message buf.validate.FloatRules.
  * Use `create(FloatRulesSchema)` to create a new message.
  */
-export declare const FloatRulesSchema: GenMessage<FloatRules, FloatRulesJson>;
+export declare const FloatRulesSchema: GenMessage<FloatRules, {
+    jsonType: FloatRulesJson;
+}>;
 /**
- * DoubleRules describes the constraints applied to `double` values. These
+ * DoubleRules describes the rules applied to `double` values. These
  * rules may also be applied to the `google.protobuf.DoubleValue` Well-Known-Type.
  *
  * @generated from message buf.validate.DoubleRules
@@ -1174,14 +1311,14 @@ export type DoubleRules = Message<"buf.validate.DoubleRules"> & {
     finite: boolean;
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
      * message MyDouble {
      *   double value = 1 [
      *     (buf.validate.field).double.example = 1.0,
-     *     (buf.validate.field).double.example = "Infinity"
+     *     (buf.validate.field).double.example = inf
      *   ];
      * }
      * ```
@@ -1191,7 +1328,7 @@ export type DoubleRules = Message<"buf.validate.DoubleRules"> & {
     example: number[];
 };
 /**
- * DoubleRules describes the constraints applied to `double` values. These
+ * DoubleRules describes the rules applied to `double` values. These
  * rules may also be applied to the `google.protobuf.DoubleValue` Well-Known-Type.
  *
  * @generated from message buf.validate.DoubleRules
@@ -1326,14 +1463,14 @@ export type DoubleRulesJson = {
     finite?: boolean;
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
      * message MyDouble {
      *   double value = 1 [
      *     (buf.validate.field).double.example = 1.0,
-     *     (buf.validate.field).double.example = "Infinity"
+     *     (buf.validate.field).double.example = inf
      *   ];
      * }
      * ```
@@ -1346,9 +1483,11 @@ export type DoubleRulesJson = {
  * Describes the message buf.validate.DoubleRules.
  * Use `create(DoubleRulesSchema)` to create a new message.
  */
-export declare const DoubleRulesSchema: GenMessage<DoubleRules, DoubleRulesJson>;
+export declare const DoubleRulesSchema: GenMessage<DoubleRules, {
+    jsonType: DoubleRulesJson;
+}>;
 /**
- * Int32Rules describes the constraints applied to `int32` values. These
+ * Int32Rules describes the rules applied to `int32` values. These
  * rules may also be applied to the `google.protobuf.Int32Value` Well-Known-Type.
  *
  * @generated from message buf.validate.Int32Rules
@@ -1498,7 +1637,7 @@ export type Int32Rules = Message<"buf.validate.Int32Rules"> & {
     notIn: number[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -1515,7 +1654,7 @@ export type Int32Rules = Message<"buf.validate.Int32Rules"> & {
     example: number[];
 };
 /**
- * Int32Rules describes the constraints applied to `int32` values. These
+ * Int32Rules describes the rules applied to `int32` values. These
  * rules may also be applied to the `google.protobuf.Int32Value` Well-Known-Type.
  *
  * @generated from message buf.validate.Int32Rules
@@ -1643,7 +1782,7 @@ export type Int32RulesJson = {
     notIn?: number[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -1663,9 +1802,11 @@ export type Int32RulesJson = {
  * Describes the message buf.validate.Int32Rules.
  * Use `create(Int32RulesSchema)` to create a new message.
  */
-export declare const Int32RulesSchema: GenMessage<Int32Rules, Int32RulesJson>;
+export declare const Int32RulesSchema: GenMessage<Int32Rules, {
+    jsonType: Int32RulesJson;
+}>;
 /**
- * Int64Rules describes the constraints applied to `int64` values. These
+ * Int64Rules describes the rules applied to `int64` values. These
  * rules may also be applied to the `google.protobuf.Int64Value` Well-Known-Type.
  *
  * @generated from message buf.validate.Int64Rules
@@ -1815,7 +1956,7 @@ export type Int64Rules = Message<"buf.validate.Int64Rules"> & {
     notIn: bigint[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -1832,7 +1973,7 @@ export type Int64Rules = Message<"buf.validate.Int64Rules"> & {
     example: bigint[];
 };
 /**
- * Int64Rules describes the constraints applied to `int64` values. These
+ * Int64Rules describes the rules applied to `int64` values. These
  * rules may also be applied to the `google.protobuf.Int64Value` Well-Known-Type.
  *
  * @generated from message buf.validate.Int64Rules
@@ -1960,7 +2101,7 @@ export type Int64RulesJson = {
     notIn?: string[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -1980,9 +2121,11 @@ export type Int64RulesJson = {
  * Describes the message buf.validate.Int64Rules.
  * Use `create(Int64RulesSchema)` to create a new message.
  */
-export declare const Int64RulesSchema: GenMessage<Int64Rules, Int64RulesJson>;
+export declare const Int64RulesSchema: GenMessage<Int64Rules, {
+    jsonType: Int64RulesJson;
+}>;
 /**
- * UInt32Rules describes the constraints applied to `uint32` values. These
+ * UInt32Rules describes the rules applied to `uint32` values. These
  * rules may also be applied to the `google.protobuf.UInt32Value` Well-Known-Type.
  *
  * @generated from message buf.validate.UInt32Rules
@@ -2132,7 +2275,7 @@ export type UInt32Rules = Message<"buf.validate.UInt32Rules"> & {
     notIn: number[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -2149,7 +2292,7 @@ export type UInt32Rules = Message<"buf.validate.UInt32Rules"> & {
     example: number[];
 };
 /**
- * UInt32Rules describes the constraints applied to `uint32` values. These
+ * UInt32Rules describes the rules applied to `uint32` values. These
  * rules may also be applied to the `google.protobuf.UInt32Value` Well-Known-Type.
  *
  * @generated from message buf.validate.UInt32Rules
@@ -2277,7 +2420,7 @@ export type UInt32RulesJson = {
     notIn?: number[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -2297,9 +2440,11 @@ export type UInt32RulesJson = {
  * Describes the message buf.validate.UInt32Rules.
  * Use `create(UInt32RulesSchema)` to create a new message.
  */
-export declare const UInt32RulesSchema: GenMessage<UInt32Rules, UInt32RulesJson>;
+export declare const UInt32RulesSchema: GenMessage<UInt32Rules, {
+    jsonType: UInt32RulesJson;
+}>;
 /**
- * UInt64Rules describes the constraints applied to `uint64` values. These
+ * UInt64Rules describes the rules applied to `uint64` values. These
  * rules may also be applied to the `google.protobuf.UInt64Value` Well-Known-Type.
  *
  * @generated from message buf.validate.UInt64Rules
@@ -2449,7 +2594,7 @@ export type UInt64Rules = Message<"buf.validate.UInt64Rules"> & {
     notIn: bigint[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -2466,7 +2611,7 @@ export type UInt64Rules = Message<"buf.validate.UInt64Rules"> & {
     example: bigint[];
 };
 /**
- * UInt64Rules describes the constraints applied to `uint64` values. These
+ * UInt64Rules describes the rules applied to `uint64` values. These
  * rules may also be applied to the `google.protobuf.UInt64Value` Well-Known-Type.
  *
  * @generated from message buf.validate.UInt64Rules
@@ -2594,7 +2739,7 @@ export type UInt64RulesJson = {
     notIn?: string[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -2614,9 +2759,11 @@ export type UInt64RulesJson = {
  * Describes the message buf.validate.UInt64Rules.
  * Use `create(UInt64RulesSchema)` to create a new message.
  */
-export declare const UInt64RulesSchema: GenMessage<UInt64Rules, UInt64RulesJson>;
+export declare const UInt64RulesSchema: GenMessage<UInt64Rules, {
+    jsonType: UInt64RulesJson;
+}>;
 /**
- * SInt32Rules describes the constraints applied to `sint32` values.
+ * SInt32Rules describes the rules applied to `sint32` values.
  *
  * @generated from message buf.validate.SInt32Rules
  */
@@ -2765,7 +2912,7 @@ export type SInt32Rules = Message<"buf.validate.SInt32Rules"> & {
     notIn: number[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -2782,7 +2929,7 @@ export type SInt32Rules = Message<"buf.validate.SInt32Rules"> & {
     example: number[];
 };
 /**
- * SInt32Rules describes the constraints applied to `sint32` values.
+ * SInt32Rules describes the rules applied to `sint32` values.
  *
  * @generated from message buf.validate.SInt32Rules
  */
@@ -2909,7 +3056,7 @@ export type SInt32RulesJson = {
     notIn?: number[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -2929,9 +3076,11 @@ export type SInt32RulesJson = {
  * Describes the message buf.validate.SInt32Rules.
  * Use `create(SInt32RulesSchema)` to create a new message.
  */
-export declare const SInt32RulesSchema: GenMessage<SInt32Rules, SInt32RulesJson>;
+export declare const SInt32RulesSchema: GenMessage<SInt32Rules, {
+    jsonType: SInt32RulesJson;
+}>;
 /**
- * SInt64Rules describes the constraints applied to `sint64` values.
+ * SInt64Rules describes the rules applied to `sint64` values.
  *
  * @generated from message buf.validate.SInt64Rules
  */
@@ -3080,7 +3229,7 @@ export type SInt64Rules = Message<"buf.validate.SInt64Rules"> & {
     notIn: bigint[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -3097,7 +3246,7 @@ export type SInt64Rules = Message<"buf.validate.SInt64Rules"> & {
     example: bigint[];
 };
 /**
- * SInt64Rules describes the constraints applied to `sint64` values.
+ * SInt64Rules describes the rules applied to `sint64` values.
  *
  * @generated from message buf.validate.SInt64Rules
  */
@@ -3224,7 +3373,7 @@ export type SInt64RulesJson = {
     notIn?: string[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -3244,9 +3393,11 @@ export type SInt64RulesJson = {
  * Describes the message buf.validate.SInt64Rules.
  * Use `create(SInt64RulesSchema)` to create a new message.
  */
-export declare const SInt64RulesSchema: GenMessage<SInt64Rules, SInt64RulesJson>;
+export declare const SInt64RulesSchema: GenMessage<SInt64Rules, {
+    jsonType: SInt64RulesJson;
+}>;
 /**
- * Fixed32Rules describes the constraints applied to `fixed32` values.
+ * Fixed32Rules describes the rules applied to `fixed32` values.
  *
  * @generated from message buf.validate.Fixed32Rules
  */
@@ -3395,7 +3546,7 @@ export type Fixed32Rules = Message<"buf.validate.Fixed32Rules"> & {
     notIn: number[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -3412,7 +3563,7 @@ export type Fixed32Rules = Message<"buf.validate.Fixed32Rules"> & {
     example: number[];
 };
 /**
- * Fixed32Rules describes the constraints applied to `fixed32` values.
+ * Fixed32Rules describes the rules applied to `fixed32` values.
  *
  * @generated from message buf.validate.Fixed32Rules
  */
@@ -3539,7 +3690,7 @@ export type Fixed32RulesJson = {
     notIn?: number[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -3559,9 +3710,11 @@ export type Fixed32RulesJson = {
  * Describes the message buf.validate.Fixed32Rules.
  * Use `create(Fixed32RulesSchema)` to create a new message.
  */
-export declare const Fixed32RulesSchema: GenMessage<Fixed32Rules, Fixed32RulesJson>;
+export declare const Fixed32RulesSchema: GenMessage<Fixed32Rules, {
+    jsonType: Fixed32RulesJson;
+}>;
 /**
- * Fixed64Rules describes the constraints applied to `fixed64` values.
+ * Fixed64Rules describes the rules applied to `fixed64` values.
  *
  * @generated from message buf.validate.Fixed64Rules
  */
@@ -3710,7 +3863,7 @@ export type Fixed64Rules = Message<"buf.validate.Fixed64Rules"> & {
     notIn: bigint[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -3727,7 +3880,7 @@ export type Fixed64Rules = Message<"buf.validate.Fixed64Rules"> & {
     example: bigint[];
 };
 /**
- * Fixed64Rules describes the constraints applied to `fixed64` values.
+ * Fixed64Rules describes the rules applied to `fixed64` values.
  *
  * @generated from message buf.validate.Fixed64Rules
  */
@@ -3854,7 +4007,7 @@ export type Fixed64RulesJson = {
     notIn?: string[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -3874,9 +4027,11 @@ export type Fixed64RulesJson = {
  * Describes the message buf.validate.Fixed64Rules.
  * Use `create(Fixed64RulesSchema)` to create a new message.
  */
-export declare const Fixed64RulesSchema: GenMessage<Fixed64Rules, Fixed64RulesJson>;
+export declare const Fixed64RulesSchema: GenMessage<Fixed64Rules, {
+    jsonType: Fixed64RulesJson;
+}>;
 /**
- * SFixed32Rules describes the constraints applied to `fixed32` values.
+ * SFixed32Rules describes the rules applied to `fixed32` values.
  *
  * @generated from message buf.validate.SFixed32Rules
  */
@@ -4025,7 +4180,7 @@ export type SFixed32Rules = Message<"buf.validate.SFixed32Rules"> & {
     notIn: number[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -4042,7 +4197,7 @@ export type SFixed32Rules = Message<"buf.validate.SFixed32Rules"> & {
     example: number[];
 };
 /**
- * SFixed32Rules describes the constraints applied to `fixed32` values.
+ * SFixed32Rules describes the rules applied to `fixed32` values.
  *
  * @generated from message buf.validate.SFixed32Rules
  */
@@ -4169,7 +4324,7 @@ export type SFixed32RulesJson = {
     notIn?: number[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -4189,9 +4344,11 @@ export type SFixed32RulesJson = {
  * Describes the message buf.validate.SFixed32Rules.
  * Use `create(SFixed32RulesSchema)` to create a new message.
  */
-export declare const SFixed32RulesSchema: GenMessage<SFixed32Rules, SFixed32RulesJson>;
+export declare const SFixed32RulesSchema: GenMessage<SFixed32Rules, {
+    jsonType: SFixed32RulesJson;
+}>;
 /**
- * SFixed64Rules describes the constraints applied to `fixed64` values.
+ * SFixed64Rules describes the rules applied to `fixed64` values.
  *
  * @generated from message buf.validate.SFixed64Rules
  */
@@ -4340,7 +4497,7 @@ export type SFixed64Rules = Message<"buf.validate.SFixed64Rules"> & {
     notIn: bigint[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -4357,7 +4514,7 @@ export type SFixed64Rules = Message<"buf.validate.SFixed64Rules"> & {
     example: bigint[];
 };
 /**
- * SFixed64Rules describes the constraints applied to `fixed64` values.
+ * SFixed64Rules describes the rules applied to `fixed64` values.
  *
  * @generated from message buf.validate.SFixed64Rules
  */
@@ -4484,7 +4641,7 @@ export type SFixed64RulesJson = {
     notIn?: string[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -4504,9 +4661,11 @@ export type SFixed64RulesJson = {
  * Describes the message buf.validate.SFixed64Rules.
  * Use `create(SFixed64RulesSchema)` to create a new message.
  */
-export declare const SFixed64RulesSchema: GenMessage<SFixed64Rules, SFixed64RulesJson>;
+export declare const SFixed64RulesSchema: GenMessage<SFixed64Rules, {
+    jsonType: SFixed64RulesJson;
+}>;
 /**
- * BoolRules describes the constraints applied to `bool` values. These rules
+ * BoolRules describes the rules applied to `bool` values. These rules
  * may also be applied to the `google.protobuf.BoolValue` Well-Known-Type.
  *
  * @generated from message buf.validate.BoolRules
@@ -4528,7 +4687,7 @@ export type BoolRules = Message<"buf.validate.BoolRules"> & {
     const: boolean;
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -4545,7 +4704,7 @@ export type BoolRules = Message<"buf.validate.BoolRules"> & {
     example: boolean[];
 };
 /**
- * BoolRules describes the constraints applied to `bool` values. These rules
+ * BoolRules describes the rules applied to `bool` values. These rules
  * may also be applied to the `google.protobuf.BoolValue` Well-Known-Type.
  *
  * @generated from message buf.validate.BoolRules
@@ -4567,7 +4726,7 @@ export type BoolRulesJson = {
     const?: boolean;
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -4587,9 +4746,11 @@ export type BoolRulesJson = {
  * Describes the message buf.validate.BoolRules.
  * Use `create(BoolRulesSchema)` to create a new message.
  */
-export declare const BoolRulesSchema: GenMessage<BoolRules, BoolRulesJson>;
+export declare const BoolRulesSchema: GenMessage<BoolRules, {
+    jsonType: BoolRulesJson;
+}>;
 /**
- * StringRules describes the constraints applied to `string` values These
+ * StringRules describes the rules applied to `string` values These
  * rules may also be applied to the `google.protobuf.StringValue` Well-Known-Type.
  *
  * @generated from message buf.validate.StringRules
@@ -4810,15 +4971,21 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
      */
     notIn: string[];
     /**
-     * `WellKnown` rules provide advanced constraints against common string
-     * patterns
+     * `WellKnown` rules provide advanced rules against common string
+     * patterns.
      *
      * @generated from oneof buf.validate.StringRules.well_known
      */
     wellKnown: {
         /**
-         * `email` specifies that the field value must be a valid email address
-         * (addr-spec only) as defined by [RFC 5322](https://datatracker.ietf.org/doc/html/rfc5322#section-3.4.1).
+         * `email` specifies that the field value must be a valid email address, for
+         * example "foo@example.com".
+         *
+         * Conforms to the definition for a valid email address from the [HTML standard](https://html.spec.whatwg.org/multipage/input.html#valid-e-mail-address).
+         * Note that this standard willfully deviates from [RFC 5322](https://datatracker.ietf.org/doc/html/rfc5322),
+         * which allows many unexpected forms of email addresses and will easily match
+         * a typographical error.
+         *
          * If the field value isn't a valid email address, an error message will be generated.
          *
          * ```proto
@@ -4834,10 +5001,18 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
         case: "email";
     } | {
         /**
-         * `hostname` specifies that the field value must be a valid
-         * hostname as defined by [RFC 1034](https://datatracker.ietf.org/doc/html/rfc1034#section-3.5). This constraint doesn't support
-         * internationalized domain names (IDNs). If the field value isn't a
-         * valid hostname, an error message will be generated.
+         * `hostname` specifies that the field value must be a valid hostname, for
+         * example "foo.example.com".
+         *
+         * A valid hostname follows the rules below:
+         * - The name consists of one or more labels, separated by a dot (".").
+         * - Each label can be 1 to 63 alphanumeric characters.
+         * - A label can contain hyphens ("-"), but must not start or end with a hyphen.
+         * - The right-most label must not be digits only.
+         * - The name can have a trailing dot—for example, "foo.example.com.".
+         * - The name can be 253 characters at most, excluding the optional trailing dot.
+         *
+         * If the field value isn't a valid hostname, an error message will be generated.
          *
          * ```proto
          * message MyString {
@@ -4852,8 +5027,15 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
         case: "hostname";
     } | {
         /**
-         * `ip` specifies that the field value must be a valid IP
-         * (v4 or v6) address, without surrounding square brackets for IPv6 addresses.
+         * `ip` specifies that the field value must be a valid IP (v4 or v6) address.
+         *
+         * IPv4 addresses are expected in the dotted decimal format—for example, "192.168.5.21".
+         * IPv6 addresses are expected in their text representation—for example, "::1",
+         * or "2001:0DB8:ABCD:0012::0".
+         *
+         * Both formats are well-defined in the internet standard [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986).
+         * Zone identifiers for IPv6 addresses (for example, "fe80::a%en1") are supported.
+         *
          * If the field value isn't a valid IP address, an error message will be
          * generated.
          *
@@ -4870,9 +5052,9 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
         case: "ip";
     } | {
         /**
-         * `ipv4` specifies that the field value must be a valid IPv4
-         * address. If the field value isn't a valid IPv4 address, an error message
-         * will be generated.
+         * `ipv4` specifies that the field value must be a valid IPv4 address—for
+         * example "192.168.5.21". If the field value isn't a valid IPv4 address, an
+         * error message will be generated.
          *
          * ```proto
          * message MyString {
@@ -4887,9 +5069,9 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
         case: "ipv4";
     } | {
         /**
-         * `ipv6` specifies that the field value must be a valid
-         * IPv6 address, without surrounding square brackets. If the field value is
-         * not a valid IPv6 address, an error message will be generated.
+         * `ipv6` specifies that the field value must be a valid IPv6 address—for
+         * example "::1", or "d7a:115c:a1e0:ab12:4843:cd96:626b:430b". If the field
+         * value is not a valid IPv6 address, an error message will be generated.
          *
          * ```proto
          * message MyString {
@@ -4904,8 +5086,11 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
         case: "ipv6";
     } | {
         /**
-         * `uri` specifies that the field value must be a valid URI as defined by
-         * [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986#section-3).
+         * `uri` specifies that the field value must be a valid URI, for example
+         * "https://example.com/foo/bar?baz=quux#frag".
+         *
+         * URI is defined in the internet standard [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986).
+         * Zone Identifiers in IPv6 address literals are supported ([RFC 6874](https://datatracker.ietf.org/doc/html/rfc6874)).
          *
          * If the field value isn't a valid URI, an error message will be generated.
          *
@@ -4922,11 +5107,13 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
         case: "uri";
     } | {
         /**
-         * `uri_ref` specifies that the field value must be a valid URI Reference as
-         * defined by [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986#section-4.1).
+         * `uri_ref` specifies that the field value must be a valid URI Reference—either
+         * a URI such as "https://example.com/foo/bar?baz=quux#frag", or a Relative
+         * Reference such as "./foo/bar?query".
          *
-         * A URI Reference is either a [URI](https://datatracker.ietf.org/doc/html/rfc3986#section-3),
-         * or a [Relative Reference](https://datatracker.ietf.org/doc/html/rfc3986#section-4.2).
+         * URI, URI Reference, and Relative Reference are defined in the internet
+         * standard [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986). Zone
+         * Identifiers in IPv6 address literals are supported ([RFC 6874](https://datatracker.ietf.org/doc/html/rfc6874)).
          *
          * If the field value isn't a valid URI Reference, an error message will be
          * generated.
@@ -4945,10 +5132,9 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
     } | {
         /**
          * `address` specifies that the field value must be either a valid hostname
-         * as defined by [RFC 1034](https://datatracker.ietf.org/doc/html/rfc1034#section-3.5)
-         * (which doesn't support internationalized domain names or IDNs) or a valid
-         * IP (v4 or v6). If the field value isn't a valid hostname or IP, an error
-         * message will be generated.
+         * (for example, "example.com"), or a valid IP (v4 or v6) address (for example,
+         * "192.168.0.1", or "::1"). If the field value isn't a valid hostname or IP,
+         * an error message will be generated.
          *
          * ```proto
          * message MyString {
@@ -4998,10 +5184,10 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
         case: "tuuid";
     } | {
         /**
-         * `ip_with_prefixlen` specifies that the field value must be a valid IP (v4 or v6)
-         * address with prefix length. If the field value isn't a valid IP with prefix
-         * length, an error message will be generated.
-         *
+         * `ip_with_prefixlen` specifies that the field value must be a valid IP
+         * (v4 or v6) address with prefix length—for example, "192.168.5.21/16" or
+         * "2001:0DB8:ABCD:0012::F1/64". If the field value isn't a valid IP with
+         * prefix length, an error message will be generated.
          *
          * ```proto
          * message MyString {
@@ -5017,9 +5203,9 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
     } | {
         /**
          * `ipv4_with_prefixlen` specifies that the field value must be a valid
-         * IPv4 address with prefix.
-         * If the field value isn't a valid IPv4 address with prefix length,
-         * an error message will be generated.
+         * IPv4 address with prefix length—for example, "192.168.5.21/16". If the
+         * field value isn't a valid IPv4 address with prefix length, an error
+         * message will be generated.
          *
          * ```proto
          * message MyString {
@@ -5035,7 +5221,7 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
     } | {
         /**
          * `ipv6_with_prefixlen` specifies that the field value must be a valid
-         * IPv6 address with prefix length.
+         * IPv6 address with prefix length—for example, "2001:0DB8:ABCD:0012::F1/64".
          * If the field value is not a valid IPv6 address with prefix length,
          * an error message will be generated.
          *
@@ -5052,10 +5238,15 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
         case: "ipv6WithPrefixlen";
     } | {
         /**
-         * `ip_prefix` specifies that the field value must be a valid IP (v4 or v6) prefix.
+         * `ip_prefix` specifies that the field value must be a valid IP (v4 or v6)
+         * prefix—for example, "192.168.0.0/16" or "2001:0DB8:ABCD:0012::0/64".
+         *
+         * The prefix must have all zeros for the unmasked bits. For example,
+         * "2001:0DB8:ABCD:0012::0/64" designates the left-most 64 bits for the
+         * prefix, and the remaining 64 bits must be zero.
+         *
          * If the field value isn't a valid IP prefix, an error message will be
-         * generated. The prefix must have all zeros for the masked bits of the prefix (e.g.,
-         * `127.0.0.0/16`, not `127.0.0.1/16`).
+         * generated.
          *
          * ```proto
          * message MyString {
@@ -5071,9 +5262,14 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
     } | {
         /**
          * `ipv4_prefix` specifies that the field value must be a valid IPv4
-         * prefix. If the field value isn't a valid IPv4 prefix, an error message
-         * will be generated. The prefix must have all zeros for the masked bits of
-         * the prefix (e.g., `127.0.0.0/16`, not `127.0.0.1/16`).
+         * prefix, for example "192.168.0.0/16".
+         *
+         * The prefix must have all zeros for the unmasked bits. For example,
+         * "192.168.0.0/16" designates the left-most 16 bits for the prefix,
+         * and the remaining 16 bits must be zero.
+         *
+         * If the field value isn't a valid IPv4 prefix, an error message
+         * will be generated.
          *
          * ```proto
          * message MyString {
@@ -5088,10 +5284,15 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
         case: "ipv4Prefix";
     } | {
         /**
-         * `ipv6_prefix` specifies that the field value must be a valid IPv6 prefix.
+         * `ipv6_prefix` specifies that the field value must be a valid IPv6 prefix—for
+         * example, "2001:0DB8:ABCD:0012::0/64".
+         *
+         * The prefix must have all zeros for the unmasked bits. For example,
+         * "2001:0DB8:ABCD:0012::0/64" designates the left-most 64 bits for the
+         * prefix, and the remaining 64 bits must be zero.
+         *
          * If the field value is not a valid IPv6 prefix, an error message will be
-         * generated. The prefix must have all zeros for the masked bits of the prefix
-         * (e.g., `2001:db8::/48`, not `2001:db8::1/48`).
+         * generated.
          *
          * ```proto
          * message MyString {
@@ -5106,10 +5307,16 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
         case: "ipv6Prefix";
     } | {
         /**
-         * `host_and_port` specifies the field value must be a valid host and port
-         * pair. The host must be a valid hostname or IP address while the port
-         * must be in the range of 0-65535, inclusive. IPv6 addresses must be delimited
-         * with square brackets (e.g., `[::1]:1234`).
+         * `host_and_port` specifies that the field value must be valid host/port
+         * pair—for example, "example.com:8080".
+         *
+         * The host can be one of:
+         * - An IPv4 address in dotted decimal format—for example, "192.168.5.21".
+         * - An IPv6 address enclosed in square brackets—for example, "[2001:0DB8:ABCD:0012::F1]".
+         * - A hostname—for example, "example.com".
+         *
+         * The port is separated by a colon. It must be non-empty, with a decimal number
+         * in the range of 0-65535, inclusive.
          *
          * @generated from field: bool host_and_port = 32;
          */
@@ -5165,7 +5372,7 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
     strict: boolean;
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -5182,7 +5389,7 @@ export type StringRules = Message<"buf.validate.StringRules"> & {
     example: string[];
 };
 /**
- * StringRules describes the constraints applied to `string` values These
+ * StringRules describes the rules applied to `string` values These
  * rules may also be applied to the `google.protobuf.StringValue` Well-Known-Type.
  *
  * @generated from message buf.validate.StringRules
@@ -5403,8 +5610,14 @@ export type StringRulesJson = {
      */
     notIn?: string[];
     /**
-     * `email` specifies that the field value must be a valid email address
-     * (addr-spec only) as defined by [RFC 5322](https://datatracker.ietf.org/doc/html/rfc5322#section-3.4.1).
+     * `email` specifies that the field value must be a valid email address, for
+     * example "foo@example.com".
+     *
+     * Conforms to the definition for a valid email address from the [HTML standard](https://html.spec.whatwg.org/multipage/input.html#valid-e-mail-address).
+     * Note that this standard willfully deviates from [RFC 5322](https://datatracker.ietf.org/doc/html/rfc5322),
+     * which allows many unexpected forms of email addresses and will easily match
+     * a typographical error.
+     *
      * If the field value isn't a valid email address, an error message will be generated.
      *
      * ```proto
@@ -5418,10 +5631,18 @@ export type StringRulesJson = {
      */
     email?: boolean;
     /**
-     * `hostname` specifies that the field value must be a valid
-     * hostname as defined by [RFC 1034](https://datatracker.ietf.org/doc/html/rfc1034#section-3.5). This constraint doesn't support
-     * internationalized domain names (IDNs). If the field value isn't a
-     * valid hostname, an error message will be generated.
+     * `hostname` specifies that the field value must be a valid hostname, for
+     * example "foo.example.com".
+     *
+     * A valid hostname follows the rules below:
+     * - The name consists of one or more labels, separated by a dot (".").
+     * - Each label can be 1 to 63 alphanumeric characters.
+     * - A label can contain hyphens ("-"), but must not start or end with a hyphen.
+     * - The right-most label must not be digits only.
+     * - The name can have a trailing dot—for example, "foo.example.com.".
+     * - The name can be 253 characters at most, excluding the optional trailing dot.
+     *
+     * If the field value isn't a valid hostname, an error message will be generated.
      *
      * ```proto
      * message MyString {
@@ -5434,8 +5655,15 @@ export type StringRulesJson = {
      */
     hostname?: boolean;
     /**
-     * `ip` specifies that the field value must be a valid IP
-     * (v4 or v6) address, without surrounding square brackets for IPv6 addresses.
+     * `ip` specifies that the field value must be a valid IP (v4 or v6) address.
+     *
+     * IPv4 addresses are expected in the dotted decimal format—for example, "192.168.5.21".
+     * IPv6 addresses are expected in their text representation—for example, "::1",
+     * or "2001:0DB8:ABCD:0012::0".
+     *
+     * Both formats are well-defined in the internet standard [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986).
+     * Zone identifiers for IPv6 addresses (for example, "fe80::a%en1") are supported.
+     *
      * If the field value isn't a valid IP address, an error message will be
      * generated.
      *
@@ -5450,9 +5678,9 @@ export type StringRulesJson = {
      */
     ip?: boolean;
     /**
-     * `ipv4` specifies that the field value must be a valid IPv4
-     * address. If the field value isn't a valid IPv4 address, an error message
-     * will be generated.
+     * `ipv4` specifies that the field value must be a valid IPv4 address—for
+     * example "192.168.5.21". If the field value isn't a valid IPv4 address, an
+     * error message will be generated.
      *
      * ```proto
      * message MyString {
@@ -5465,9 +5693,9 @@ export type StringRulesJson = {
      */
     ipv4?: boolean;
     /**
-     * `ipv6` specifies that the field value must be a valid
-     * IPv6 address, without surrounding square brackets. If the field value is
-     * not a valid IPv6 address, an error message will be generated.
+     * `ipv6` specifies that the field value must be a valid IPv6 address—for
+     * example "::1", or "d7a:115c:a1e0:ab12:4843:cd96:626b:430b". If the field
+     * value is not a valid IPv6 address, an error message will be generated.
      *
      * ```proto
      * message MyString {
@@ -5480,8 +5708,11 @@ export type StringRulesJson = {
      */
     ipv6?: boolean;
     /**
-     * `uri` specifies that the field value must be a valid URI as defined by
-     * [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986#section-3).
+     * `uri` specifies that the field value must be a valid URI, for example
+     * "https://example.com/foo/bar?baz=quux#frag".
+     *
+     * URI is defined in the internet standard [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986).
+     * Zone Identifiers in IPv6 address literals are supported ([RFC 6874](https://datatracker.ietf.org/doc/html/rfc6874)).
      *
      * If the field value isn't a valid URI, an error message will be generated.
      *
@@ -5496,11 +5727,13 @@ export type StringRulesJson = {
      */
     uri?: boolean;
     /**
-     * `uri_ref` specifies that the field value must be a valid URI Reference as
-     * defined by [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986#section-4.1).
+     * `uri_ref` specifies that the field value must be a valid URI Reference—either
+     * a URI such as "https://example.com/foo/bar?baz=quux#frag", or a Relative
+     * Reference such as "./foo/bar?query".
      *
-     * A URI Reference is either a [URI](https://datatracker.ietf.org/doc/html/rfc3986#section-3),
-     * or a [Relative Reference](https://datatracker.ietf.org/doc/html/rfc3986#section-4.2).
+     * URI, URI Reference, and Relative Reference are defined in the internet
+     * standard [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986). Zone
+     * Identifiers in IPv6 address literals are supported ([RFC 6874](https://datatracker.ietf.org/doc/html/rfc6874)).
      *
      * If the field value isn't a valid URI Reference, an error message will be
      * generated.
@@ -5517,10 +5750,9 @@ export type StringRulesJson = {
     uriRef?: boolean;
     /**
      * `address` specifies that the field value must be either a valid hostname
-     * as defined by [RFC 1034](https://datatracker.ietf.org/doc/html/rfc1034#section-3.5)
-     * (which doesn't support internationalized domain names or IDNs) or a valid
-     * IP (v4 or v6). If the field value isn't a valid hostname or IP, an error
-     * message will be generated.
+     * (for example, "example.com"), or a valid IP (v4 or v6) address (for example,
+     * "192.168.0.1", or "::1"). If the field value isn't a valid hostname or IP,
+     * an error message will be generated.
      *
      * ```proto
      * message MyString {
@@ -5564,10 +5796,10 @@ export type StringRulesJson = {
      */
     tuuid?: boolean;
     /**
-     * `ip_with_prefixlen` specifies that the field value must be a valid IP (v4 or v6)
-     * address with prefix length. If the field value isn't a valid IP with prefix
-     * length, an error message will be generated.
-     *
+     * `ip_with_prefixlen` specifies that the field value must be a valid IP
+     * (v4 or v6) address with prefix length—for example, "192.168.5.21/16" or
+     * "2001:0DB8:ABCD:0012::F1/64". If the field value isn't a valid IP with
+     * prefix length, an error message will be generated.
      *
      * ```proto
      * message MyString {
@@ -5581,9 +5813,9 @@ export type StringRulesJson = {
     ipWithPrefixlen?: boolean;
     /**
      * `ipv4_with_prefixlen` specifies that the field value must be a valid
-     * IPv4 address with prefix.
-     * If the field value isn't a valid IPv4 address with prefix length,
-     * an error message will be generated.
+     * IPv4 address with prefix length—for example, "192.168.5.21/16". If the
+     * field value isn't a valid IPv4 address with prefix length, an error
+     * message will be generated.
      *
      * ```proto
      * message MyString {
@@ -5597,7 +5829,7 @@ export type StringRulesJson = {
     ipv4WithPrefixlen?: boolean;
     /**
      * `ipv6_with_prefixlen` specifies that the field value must be a valid
-     * IPv6 address with prefix length.
+     * IPv6 address with prefix length—for example, "2001:0DB8:ABCD:0012::F1/64".
      * If the field value is not a valid IPv6 address with prefix length,
      * an error message will be generated.
      *
@@ -5612,10 +5844,15 @@ export type StringRulesJson = {
      */
     ipv6WithPrefixlen?: boolean;
     /**
-     * `ip_prefix` specifies that the field value must be a valid IP (v4 or v6) prefix.
+     * `ip_prefix` specifies that the field value must be a valid IP (v4 or v6)
+     * prefix—for example, "192.168.0.0/16" or "2001:0DB8:ABCD:0012::0/64".
+     *
+     * The prefix must have all zeros for the unmasked bits. For example,
+     * "2001:0DB8:ABCD:0012::0/64" designates the left-most 64 bits for the
+     * prefix, and the remaining 64 bits must be zero.
+     *
      * If the field value isn't a valid IP prefix, an error message will be
-     * generated. The prefix must have all zeros for the masked bits of the prefix (e.g.,
-     * `127.0.0.0/16`, not `127.0.0.1/16`).
+     * generated.
      *
      * ```proto
      * message MyString {
@@ -5629,9 +5866,14 @@ export type StringRulesJson = {
     ipPrefix?: boolean;
     /**
      * `ipv4_prefix` specifies that the field value must be a valid IPv4
-     * prefix. If the field value isn't a valid IPv4 prefix, an error message
-     * will be generated. The prefix must have all zeros for the masked bits of
-     * the prefix (e.g., `127.0.0.0/16`, not `127.0.0.1/16`).
+     * prefix, for example "192.168.0.0/16".
+     *
+     * The prefix must have all zeros for the unmasked bits. For example,
+     * "192.168.0.0/16" designates the left-most 16 bits for the prefix,
+     * and the remaining 16 bits must be zero.
+     *
+     * If the field value isn't a valid IPv4 prefix, an error message
+     * will be generated.
      *
      * ```proto
      * message MyString {
@@ -5644,10 +5886,15 @@ export type StringRulesJson = {
      */
     ipv4Prefix?: boolean;
     /**
-     * `ipv6_prefix` specifies that the field value must be a valid IPv6 prefix.
+     * `ipv6_prefix` specifies that the field value must be a valid IPv6 prefix—for
+     * example, "2001:0DB8:ABCD:0012::0/64".
+     *
+     * The prefix must have all zeros for the unmasked bits. For example,
+     * "2001:0DB8:ABCD:0012::0/64" designates the left-most 64 bits for the
+     * prefix, and the remaining 64 bits must be zero.
+     *
      * If the field value is not a valid IPv6 prefix, an error message will be
-     * generated. The prefix must have all zeros for the masked bits of the prefix
-     * (e.g., `2001:db8::/48`, not `2001:db8::1/48`).
+     * generated.
      *
      * ```proto
      * message MyString {
@@ -5660,10 +5907,16 @@ export type StringRulesJson = {
      */
     ipv6Prefix?: boolean;
     /**
-     * `host_and_port` specifies the field value must be a valid host and port
-     * pair. The host must be a valid hostname or IP address while the port
-     * must be in the range of 0-65535, inclusive. IPv6 addresses must be delimited
-     * with square brackets (e.g., `[::1]:1234`).
+     * `host_and_port` specifies that the field value must be valid host/port
+     * pair—for example, "example.com:8080".
+     *
+     * The host can be one of:
+     * - An IPv4 address in dotted decimal format—for example, "192.168.5.21".
+     * - An IPv6 address enclosed in square brackets—for example, "[2001:0DB8:ABCD:0012::F1]".
+     * - A hostname—for example, "example.com".
+     *
+     * The port is separated by a colon. It must be non-empty, with a decimal number
+     * in the range of 0-65535, inclusive.
      *
      * @generated from field: bool host_and_port = 32;
      */
@@ -5712,7 +5965,7 @@ export type StringRulesJson = {
     strict?: boolean;
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -5732,9 +5985,11 @@ export type StringRulesJson = {
  * Describes the message buf.validate.StringRules.
  * Use `create(StringRulesSchema)` to create a new message.
  */
-export declare const StringRulesSchema: GenMessage<StringRules, StringRulesJson>;
+export declare const StringRulesSchema: GenMessage<StringRules, {
+    jsonType: StringRulesJson;
+}>;
 /**
- * BytesRules describe the constraints applied to `bytes` values. These rules
+ * BytesRules describe the rules applied to `bytes` values. These rules
  * may also be applied to the `google.protobuf.BytesValue` Well-Known-Type.
  *
  * @generated from message buf.validate.BytesRules
@@ -5892,7 +6147,7 @@ export type BytesRules = Message<"buf.validate.BytesRules"> & {
      */
     notIn: Uint8Array[];
     /**
-     * WellKnown rules provide advanced constraints against common byte
+     * WellKnown rules provide advanced rules against common byte
      * patterns
      *
      * @generated from oneof buf.validate.BytesRules.well_known
@@ -5900,7 +6155,7 @@ export type BytesRules = Message<"buf.validate.BytesRules"> & {
     wellKnown: {
         /**
          * `ip` ensures that the field `value` is a valid IP address (v4 or v6) in byte format.
-         * If the field value doesn't meet this constraint, an error message is generated.
+         * If the field value doesn't meet this rule, an error message is generated.
          *
          * ```proto
          * message MyBytes {
@@ -5916,7 +6171,7 @@ export type BytesRules = Message<"buf.validate.BytesRules"> & {
     } | {
         /**
          * `ipv4` ensures that the field `value` is a valid IPv4 address in byte format.
-         * If the field value doesn't meet this constraint, an error message is generated.
+         * If the field value doesn't meet this rule, an error message is generated.
          *
          * ```proto
          * message MyBytes {
@@ -5932,7 +6187,7 @@ export type BytesRules = Message<"buf.validate.BytesRules"> & {
     } | {
         /**
          * `ipv6` ensures that the field `value` is a valid IPv6 address in byte format.
-         * If the field value doesn't meet this constraint, an error message is generated.
+         * If the field value doesn't meet this rule, an error message is generated.
          * ```proto
          * message MyBytes {
          *   // value must be a valid IPv6 address
@@ -5950,7 +6205,7 @@ export type BytesRules = Message<"buf.validate.BytesRules"> & {
     };
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -5967,7 +6222,7 @@ export type BytesRules = Message<"buf.validate.BytesRules"> & {
     example: Uint8Array[];
 };
 /**
- * BytesRules describe the constraints applied to `bytes` values. These rules
+ * BytesRules describe the rules applied to `bytes` values. These rules
  * may also be applied to the `google.protobuf.BytesValue` Well-Known-Type.
  *
  * @generated from message buf.validate.BytesRules
@@ -6126,7 +6381,7 @@ export type BytesRulesJson = {
     notIn?: string[];
     /**
      * `ip` ensures that the field `value` is a valid IP address (v4 or v6) in byte format.
-     * If the field value doesn't meet this constraint, an error message is generated.
+     * If the field value doesn't meet this rule, an error message is generated.
      *
      * ```proto
      * message MyBytes {
@@ -6140,7 +6395,7 @@ export type BytesRulesJson = {
     ip?: boolean;
     /**
      * `ipv4` ensures that the field `value` is a valid IPv4 address in byte format.
-     * If the field value doesn't meet this constraint, an error message is generated.
+     * If the field value doesn't meet this rule, an error message is generated.
      *
      * ```proto
      * message MyBytes {
@@ -6154,7 +6409,7 @@ export type BytesRulesJson = {
     ipv4?: boolean;
     /**
      * `ipv6` ensures that the field `value` is a valid IPv6 address in byte format.
-     * If the field value doesn't meet this constraint, an error message is generated.
+     * If the field value doesn't meet this rule, an error message is generated.
      * ```proto
      * message MyBytes {
      *   // value must be a valid IPv6 address
@@ -6167,7 +6422,7 @@ export type BytesRulesJson = {
     ipv6?: boolean;
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -6187,9 +6442,11 @@ export type BytesRulesJson = {
  * Describes the message buf.validate.BytesRules.
  * Use `create(BytesRulesSchema)` to create a new message.
  */
-export declare const BytesRulesSchema: GenMessage<BytesRules, BytesRulesJson>;
+export declare const BytesRulesSchema: GenMessage<BytesRules, {
+    jsonType: BytesRulesJson;
+}>;
 /**
- * EnumRules describe the constraints applied to `enum` values.
+ * EnumRules describe the rules applied to `enum` values.
  *
  * @generated from message buf.validate.EnumRules
  */
@@ -6278,7 +6535,7 @@ export type EnumRules = Message<"buf.validate.EnumRules"> & {
     notIn: number[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -6299,7 +6556,7 @@ export type EnumRules = Message<"buf.validate.EnumRules"> & {
     example: number[];
 };
 /**
- * EnumRules describe the constraints applied to `enum` values.
+ * EnumRules describe the rules applied to `enum` values.
  *
  * @generated from message buf.validate.EnumRules
  */
@@ -6388,7 +6645,7 @@ export type EnumRulesJson = {
     notIn?: number[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -6412,9 +6669,11 @@ export type EnumRulesJson = {
  * Describes the message buf.validate.EnumRules.
  * Use `create(EnumRulesSchema)` to create a new message.
  */
-export declare const EnumRulesSchema: GenMessage<EnumRules, EnumRulesJson>;
+export declare const EnumRulesSchema: GenMessage<EnumRules, {
+    jsonType: EnumRulesJson;
+}>;
 /**
- * RepeatedRules describe the constraints applied to `repeated` values.
+ * RepeatedRules describe the rules applied to `repeated` values.
  *
  * @generated from message buf.validate.RepeatedRules
  */
@@ -6453,7 +6712,7 @@ export type RepeatedRules = Message<"buf.validate.RepeatedRules"> & {
     maxItems: bigint;
     /**
      * `unique` indicates that all elements in this field must
-     * be unique. This constraint is strictly applicable to scalar and enum
+     * be unique. This rule is strictly applicable to scalar and enum
      * types, with message types not being supported.
      *
      * ```proto
@@ -6467,13 +6726,16 @@ export type RepeatedRules = Message<"buf.validate.RepeatedRules"> & {
      */
     unique: boolean;
     /**
-     * `items` details the constraints to be applied to each item
+     * `items` details the rules to be applied to each item
      * in the field. Even for repeated message fields, validation is executed
      * against each item unless skip is explicitly specified.
      *
+     * Note that repeated items are always considered populated. The `required`
+     * rule does not apply.
+     *
      * ```proto
      * message MyRepeated {
-     *   // The items in the field `value` must follow the specified constraints.
+     *   // The items in the field `value` must follow the specified rules.
      *   repeated string value = 1 [(buf.validate.field).repeated.items = {
      *     string: {
      *       min_len: 3
@@ -6483,12 +6745,12 @@ export type RepeatedRules = Message<"buf.validate.RepeatedRules"> & {
      * }
      * ```
      *
-     * @generated from field: optional buf.validate.FieldConstraints items = 4;
+     * @generated from field: optional buf.validate.FieldRules items = 4;
      */
-    items?: FieldConstraints;
+    items?: FieldRules;
 };
 /**
- * RepeatedRules describe the constraints applied to `repeated` values.
+ * RepeatedRules describe the rules applied to `repeated` values.
  *
  * @generated from message buf.validate.RepeatedRules
  */
@@ -6527,7 +6789,7 @@ export type RepeatedRulesJson = {
     maxItems?: string;
     /**
      * `unique` indicates that all elements in this field must
-     * be unique. This constraint is strictly applicable to scalar and enum
+     * be unique. This rule is strictly applicable to scalar and enum
      * types, with message types not being supported.
      *
      * ```proto
@@ -6541,13 +6803,16 @@ export type RepeatedRulesJson = {
      */
     unique?: boolean;
     /**
-     * `items` details the constraints to be applied to each item
+     * `items` details the rules to be applied to each item
      * in the field. Even for repeated message fields, validation is executed
      * against each item unless skip is explicitly specified.
      *
+     * Note that repeated items are always considered populated. The `required`
+     * rule does not apply.
+     *
      * ```proto
      * message MyRepeated {
-     *   // The items in the field `value` must follow the specified constraints.
+     *   // The items in the field `value` must follow the specified rules.
      *   repeated string value = 1 [(buf.validate.field).repeated.items = {
      *     string: {
      *       min_len: 3
@@ -6557,17 +6822,19 @@ export type RepeatedRulesJson = {
      * }
      * ```
      *
-     * @generated from field: optional buf.validate.FieldConstraints items = 4;
+     * @generated from field: optional buf.validate.FieldRules items = 4;
      */
-    items?: FieldConstraintsJson;
+    items?: FieldRulesJson;
 };
 /**
  * Describes the message buf.validate.RepeatedRules.
  * Use `create(RepeatedRulesSchema)` to create a new message.
  */
-export declare const RepeatedRulesSchema: GenMessage<RepeatedRules, RepeatedRulesJson>;
+export declare const RepeatedRulesSchema: GenMessage<RepeatedRules, {
+    jsonType: RepeatedRulesJson;
+}>;
 /**
- * MapRules describe the constraints applied to `map` values.
+ * MapRules describe the rules applied to `map` values.
  *
  * @generated from message buf.validate.MapRules
  */
@@ -6601,11 +6868,14 @@ export type MapRules = Message<"buf.validate.MapRules"> & {
      */
     maxPairs: bigint;
     /**
-     * Specifies the constraints to be applied to each key in the field.
+     * Specifies the rules to be applied to each key in the field.
+     *
+     * Note that map keys are always considered populated. The `required`
+     * rule does not apply.
      *
      * ```proto
      * message MyMap {
-     *   // The keys in the field `value` must follow the specified constraints.
+     *   // The keys in the field `value` must follow the specified rules.
      *   map<string, string> value = 1 [(buf.validate.field).map.keys = {
      *     string: {
      *       min_len: 3
@@ -6615,17 +6885,20 @@ export type MapRules = Message<"buf.validate.MapRules"> & {
      * }
      * ```
      *
-     * @generated from field: optional buf.validate.FieldConstraints keys = 4;
+     * @generated from field: optional buf.validate.FieldRules keys = 4;
      */
-    keys?: FieldConstraints;
+    keys?: FieldRules;
     /**
-     * Specifies the constraints to be applied to the value of each key in the
+     * Specifies the rules to be applied to the value of each key in the
      * field. Message values will still have their validations evaluated unless
      * skip is specified here.
      *
+     * Note that map values are always considered populated. The `required`
+     * rule does not apply.
+     *
      * ```proto
      * message MyMap {
-     *   // The values in the field `value` must follow the specified constraints.
+     *   // The values in the field `value` must follow the specified rules.
      *   map<string, string> value = 1 [(buf.validate.field).map.values = {
      *     string: {
      *       min_len: 5
@@ -6635,12 +6908,12 @@ export type MapRules = Message<"buf.validate.MapRules"> & {
      * }
      * ```
      *
-     * @generated from field: optional buf.validate.FieldConstraints values = 5;
+     * @generated from field: optional buf.validate.FieldRules values = 5;
      */
-    values?: FieldConstraints;
+    values?: FieldRules;
 };
 /**
- * MapRules describe the constraints applied to `map` values.
+ * MapRules describe the rules applied to `map` values.
  *
  * @generated from message buf.validate.MapRules
  */
@@ -6674,11 +6947,14 @@ export type MapRulesJson = {
      */
     maxPairs?: string;
     /**
-     * Specifies the constraints to be applied to each key in the field.
+     * Specifies the rules to be applied to each key in the field.
+     *
+     * Note that map keys are always considered populated. The `required`
+     * rule does not apply.
      *
      * ```proto
      * message MyMap {
-     *   // The keys in the field `value` must follow the specified constraints.
+     *   // The keys in the field `value` must follow the specified rules.
      *   map<string, string> value = 1 [(buf.validate.field).map.keys = {
      *     string: {
      *       min_len: 3
@@ -6688,17 +6964,20 @@ export type MapRulesJson = {
      * }
      * ```
      *
-     * @generated from field: optional buf.validate.FieldConstraints keys = 4;
+     * @generated from field: optional buf.validate.FieldRules keys = 4;
      */
-    keys?: FieldConstraintsJson;
+    keys?: FieldRulesJson;
     /**
-     * Specifies the constraints to be applied to the value of each key in the
+     * Specifies the rules to be applied to the value of each key in the
      * field. Message values will still have their validations evaluated unless
      * skip is specified here.
      *
+     * Note that map values are always considered populated. The `required`
+     * rule does not apply.
+     *
      * ```proto
      * message MyMap {
-     *   // The values in the field `value` must follow the specified constraints.
+     *   // The values in the field `value` must follow the specified rules.
      *   map<string, string> value = 1 [(buf.validate.field).map.values = {
      *     string: {
      *       min_len: 5
@@ -6708,17 +6987,19 @@ export type MapRulesJson = {
      * }
      * ```
      *
-     * @generated from field: optional buf.validate.FieldConstraints values = 5;
+     * @generated from field: optional buf.validate.FieldRules values = 5;
      */
-    values?: FieldConstraintsJson;
+    values?: FieldRulesJson;
 };
 /**
  * Describes the message buf.validate.MapRules.
  * Use `create(MapRulesSchema)` to create a new message.
  */
-export declare const MapRulesSchema: GenMessage<MapRules, MapRulesJson>;
+export declare const MapRulesSchema: GenMessage<MapRules, {
+    jsonType: MapRulesJson;
+}>;
 /**
- * AnyRules describe constraints applied exclusively to the `google.protobuf.Any` well-known type.
+ * AnyRules describe rules applied exclusively to the `google.protobuf.Any` well-known type.
  *
  * @generated from message buf.validate.AnyRules
  */
@@ -6731,7 +7012,9 @@ export type AnyRules = Message<"buf.validate.AnyRules"> & {
      * ```proto
      * message MyAny {
      *   //  The `value` field must have a `type_url` equal to one of the specified values.
-     *   google.protobuf.Any value = 1 [(buf.validate.field).any.in = ["type.googleapis.com/MyType1", "type.googleapis.com/MyType2"]];
+     *   google.protobuf.Any value = 1 [(buf.validate.field).any = {
+     *       in: ["type.googleapis.com/MyType1", "type.googleapis.com/MyType2"]
+     *   }];
      * }
      * ```
      *
@@ -6743,8 +7026,10 @@ export type AnyRules = Message<"buf.validate.AnyRules"> & {
      *
      * ```proto
      * message MyAny {
-     *   // The field `value` must not have a `type_url` equal to any of the specified values.
-     *   google.protobuf.Any value = 1 [(buf.validate.field).any.not_in = ["type.googleapis.com/ForbiddenType1", "type.googleapis.com/ForbiddenType2"]];
+     *   //  The `value` field must not have a `type_url` equal to any of the specified values.
+     *   google.protobuf.Any value = 1 [(buf.validate.field).any = {
+     *       not_in: ["type.googleapis.com/ForbiddenType1", "type.googleapis.com/ForbiddenType2"]
+     *   }];
      * }
      * ```
      *
@@ -6753,7 +7038,7 @@ export type AnyRules = Message<"buf.validate.AnyRules"> & {
     notIn: string[];
 };
 /**
- * AnyRules describe constraints applied exclusively to the `google.protobuf.Any` well-known type.
+ * AnyRules describe rules applied exclusively to the `google.protobuf.Any` well-known type.
  *
  * @generated from message buf.validate.AnyRules
  */
@@ -6766,7 +7051,9 @@ export type AnyRulesJson = {
      * ```proto
      * message MyAny {
      *   //  The `value` field must have a `type_url` equal to one of the specified values.
-     *   google.protobuf.Any value = 1 [(buf.validate.field).any.in = ["type.googleapis.com/MyType1", "type.googleapis.com/MyType2"]];
+     *   google.protobuf.Any value = 1 [(buf.validate.field).any = {
+     *       in: ["type.googleapis.com/MyType1", "type.googleapis.com/MyType2"]
+     *   }];
      * }
      * ```
      *
@@ -6778,8 +7065,10 @@ export type AnyRulesJson = {
      *
      * ```proto
      * message MyAny {
-     *   // The field `value` must not have a `type_url` equal to any of the specified values.
-     *   google.protobuf.Any value = 1 [(buf.validate.field).any.not_in = ["type.googleapis.com/ForbiddenType1", "type.googleapis.com/ForbiddenType2"]];
+     *   //  The `value` field must not have a `type_url` equal to any of the specified values.
+     *   google.protobuf.Any value = 1 [(buf.validate.field).any = {
+     *       not_in: ["type.googleapis.com/ForbiddenType1", "type.googleapis.com/ForbiddenType2"]
+     *   }];
      * }
      * ```
      *
@@ -6791,9 +7080,11 @@ export type AnyRulesJson = {
  * Describes the message buf.validate.AnyRules.
  * Use `create(AnyRulesSchema)` to create a new message.
  */
-export declare const AnyRulesSchema: GenMessage<AnyRules, AnyRulesJson>;
+export declare const AnyRulesSchema: GenMessage<AnyRules, {
+    jsonType: AnyRulesJson;
+}>;
 /**
- * DurationRules describe the constraints applied exclusively to the `google.protobuf.Duration` well-known type.
+ * DurationRules describe the rules applied exclusively to the `google.protobuf.Duration` well-known type.
  *
  * @generated from message buf.validate.DurationRules
  */
@@ -6944,7 +7235,7 @@ export type DurationRules = Message<"buf.validate.DurationRules"> & {
     notIn: Duration[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -6961,7 +7252,7 @@ export type DurationRules = Message<"buf.validate.DurationRules"> & {
     example: Duration[];
 };
 /**
- * DurationRules describe the constraints applied exclusively to the `google.protobuf.Duration` well-known type.
+ * DurationRules describe the rules applied exclusively to the `google.protobuf.Duration` well-known type.
  *
  * @generated from message buf.validate.DurationRules
  */
@@ -7090,7 +7381,7 @@ export type DurationRulesJson = {
     notIn?: DurationJson[];
     /**
      * `example` specifies values that the field may have. These values SHOULD
-     * conform to other constraints. `example` values will not impact validation
+     * conform to other rules. `example` values will not impact validation
      * but may be used as helpful guidance on how to populate the given field.
      *
      * ```proto
@@ -7110,9 +7401,11 @@ export type DurationRulesJson = {
  * Describes the message buf.validate.DurationRules.
  * Use `create(DurationRulesSchema)` to create a new message.
  */
-export declare const DurationRulesSchema: GenMessage<DurationRules, DurationRulesJson>;
+export declare const DurationRulesSchema: GenMessage<DurationRules, {
+    jsonType: DurationRulesJson;
+}>;
 /**
- * TimestampRules describe the constraints applied exclusively to the `google.protobuf.Timestamp` well-known type.
+ * TimestampRules describe the rules applied exclusively to the `google.protobuf.Timestamp` well-known type.
  *
  * @generated from message buf.validate.TimestampRules
  */
@@ -7268,12 +7561,25 @@ export type TimestampRules = Message<"buf.validate.TimestampRules"> & {
      */
     within?: Duration;
     /**
+     * `example` specifies values that the field may have. These values SHOULD
+     * conform to other rules. `example` values will not impact validation
+     * but may be used as helpful guidance on how to populate the given field.
+     *
+     * ```proto
+     * message MyTimestamp {
+     *   google.protobuf.Timestamp value = 1 [
+     *     (buf.validate.field).timestamp.example = { seconds: 1672444800 },
+     *     (buf.validate.field).timestamp.example = { seconds: 1672531200 },
+     *   ];
+     * }
+     * ```
+     *
      * @generated from field: repeated google.protobuf.Timestamp example = 10;
      */
     example: Timestamp[];
 };
 /**
- * TimestampRules describe the constraints applied exclusively to the `google.protobuf.Timestamp` well-known type.
+ * TimestampRules describe the rules applied exclusively to the `google.protobuf.Timestamp` well-known type.
  *
  * @generated from message buf.validate.TimestampRules
  */
@@ -7403,6 +7709,19 @@ export type TimestampRulesJson = {
      */
     within?: DurationJson;
     /**
+     * `example` specifies values that the field may have. These values SHOULD
+     * conform to other rules. `example` values will not impact validation
+     * but may be used as helpful guidance on how to populate the given field.
+     *
+     * ```proto
+     * message MyTimestamp {
+     *   google.protobuf.Timestamp value = 1 [
+     *     (buf.validate.field).timestamp.example = { seconds: 1672444800 },
+     *     (buf.validate.field).timestamp.example = { seconds: 1672531200 },
+     *   ];
+     * }
+     * ```
+     *
      * @generated from field: repeated google.protobuf.Timestamp example = 10;
      */
     example?: TimestampJson[];
@@ -7411,10 +7730,12 @@ export type TimestampRulesJson = {
  * Describes the message buf.validate.TimestampRules.
  * Use `create(TimestampRulesSchema)` to create a new message.
  */
-export declare const TimestampRulesSchema: GenMessage<TimestampRules, TimestampRulesJson>;
+export declare const TimestampRulesSchema: GenMessage<TimestampRules, {
+    jsonType: TimestampRulesJson;
+}>;
 /**
  * `Violations` is a collection of `Violation` messages. This message type is returned by
- * protovalidate when a proto message fails to meet the requirements set by the `Constraint` validation rules.
+ * Protovalidate when a proto message fails to meet the requirements set by the `Rule` validation rules.
  * Each individual violation is represented by a `Violation` message.
  *
  * @generated from message buf.validate.Violations
@@ -7429,7 +7750,7 @@ export type Violations = Message<"buf.validate.Violations"> & {
 };
 /**
  * `Violations` is a collection of `Violation` messages. This message type is returned by
- * protovalidate when a proto message fails to meet the requirements set by the `Constraint` validation rules.
+ * Protovalidate when a proto message fails to meet the requirements set by the `Rule` validation rules.
  * Each individual violation is represented by a `Violation` message.
  *
  * @generated from message buf.validate.Violations
@@ -7446,18 +7767,51 @@ export type ViolationsJson = {
  * Describes the message buf.validate.Violations.
  * Use `create(ViolationsSchema)` to create a new message.
  */
-export declare const ViolationsSchema: GenMessage<Violations, ViolationsJson>;
+export declare const ViolationsSchema: GenMessage<Violations, {
+    jsonType: ViolationsJson;
+}>;
 /**
  * `Violation` represents a single instance where a validation rule, expressed
- * as a `Constraint`, was not met. It provides information about the field that
- * caused the violation, the specific constraint that wasn't fulfilled, and a
+ * as a `Rule`, was not met. It provides information about the field that
+ * caused the violation, the specific rule that wasn't fulfilled, and a
  * human-readable error message.
  *
+ * For example, consider the following message:
+ *
+ * ```proto
+ * message User {
+ *     int32 age = 1 [(buf.validate.field).cel = {
+ *         id: "user.age",
+ *         expression: "this < 18 ? 'User must be at least 18 years old' : ''",
+ *     }];
+ * }
+ * ```
+ *
+ * It could produce the following violation:
+ *
  * ```json
  * {
- *   "fieldPath": "bar",
- *   "constraintId": "foo.bar",
- *   "message": "bar must be greater than 0"
+ *   "ruleId": "user.age",
+ *   "message": "User must be at least 18 years old",
+ *   "field": {
+ *     "elements": [
+ *       {
+ *         "fieldNumber": 1,
+ *         "fieldName": "age",
+ *         "fieldType": "TYPE_INT32"
+ *       }
+ *     ]
+ *   },
+ *   "rule": {
+ *     "elements": [
+ *       {
+ *         "fieldNumber": 23,
+ *         "fieldName": "cel",
+ *         "fieldType": "TYPE_MESSAGE",
+ *         "index": "0"
+ *       }
+ *     ]
+ *   }
  * }
  * ```
  *
@@ -7489,9 +7843,9 @@ export type Violation = Message<"buf.validate.Violation"> & {
      */
     field?: FieldPath;
     /**
-     * `rule` is a machine-readable path that points to the specific constraint rule that failed validation.
-     * This will be a nested field starting from the FieldConstraints of the field that failed validation.
-     * For custom constraints, this will provide the path of the constraint, e.g. `cel[0]`.
+     * `rule` is a machine-readable path that points to the specific rule that failed validation.
+     * This will be a nested field starting from the FieldRules of the field that failed validation.
+     * For custom rules, this will provide the path of the rule, e.g. `cel[0]`.
      *
      * For example, consider the following message:
      *
@@ -7499,7 +7853,7 @@ export type Violation = Message<"buf.validate.Violation"> & {
      * message Message {
      *   bool a = 1 [(buf.validate.field).required = true];
      *   bool b = 2 [(buf.validate.field).cel = {
-     *     id: "custom_constraint",
+     *     id: "custom_rule",
      *     expression: "!this ? 'b must be true': ''"
      *   }]
      * }
@@ -7522,15 +7876,15 @@ export type Violation = Message<"buf.validate.Violation"> & {
      */
     rule?: FieldPath;
     /**
-     * `constraint_id` is the unique identifier of the `Constraint` that was not fulfilled.
-     * This is the same `id` that was specified in the `Constraint` message, allowing easy tracing of which rule was violated.
+     * `rule_id` is the unique identifier of the `Rule` that was not fulfilled.
+     * This is the same `id` that was specified in the `Rule` message, allowing easy tracing of which rule was violated.
      *
-     * @generated from field: optional string constraint_id = 2;
+     * @generated from field: optional string rule_id = 2;
      */
-    constraintId: string;
+    ruleId: string;
     /**
      * `message` is a human-readable error message that describes the nature of the violation.
-     * This can be the default error message from the violated `Constraint`, or it can be a custom message that gives more context about the violation.
+     * This can be the default error message from the violated `Rule`, or it can be a custom message that gives more context about the violation.
      *
      * @generated from field: optional string message = 3;
      */
@@ -7544,15 +7898,46 @@ export type Violation = Message<"buf.validate.Violation"> & {
 };
 /**
  * `Violation` represents a single instance where a validation rule, expressed
- * as a `Constraint`, was not met. It provides information about the field that
- * caused the violation, the specific constraint that wasn't fulfilled, and a
+ * as a `Rule`, was not met. It provides information about the field that
+ * caused the violation, the specific rule that wasn't fulfilled, and a
  * human-readable error message.
  *
+ * For example, consider the following message:
+ *
+ * ```proto
+ * message User {
+ *     int32 age = 1 [(buf.validate.field).cel = {
+ *         id: "user.age",
+ *         expression: "this < 18 ? 'User must be at least 18 years old' : ''",
+ *     }];
+ * }
+ * ```
+ *
+ * It could produce the following violation:
+ *
  * ```json
  * {
- *   "fieldPath": "bar",
- *   "constraintId": "foo.bar",
- *   "message": "bar must be greater than 0"
+ *   "ruleId": "user.age",
+ *   "message": "User must be at least 18 years old",
+ *   "field": {
+ *     "elements": [
+ *       {
+ *         "fieldNumber": 1,
+ *         "fieldName": "age",
+ *         "fieldType": "TYPE_INT32"
+ *       }
+ *     ]
+ *   },
+ *   "rule": {
+ *     "elements": [
+ *       {
+ *         "fieldNumber": 23,
+ *         "fieldName": "cel",
+ *         "fieldType": "TYPE_MESSAGE",
+ *         "index": "0"
+ *       }
+ *     ]
+ *   }
  * }
  * ```
  *
@@ -7584,9 +7969,9 @@ export type ViolationJson = {
      */
     field?: FieldPathJson;
     /**
-     * `rule` is a machine-readable path that points to the specific constraint rule that failed validation.
-     * This will be a nested field starting from the FieldConstraints of the field that failed validation.
-     * For custom constraints, this will provide the path of the constraint, e.g. `cel[0]`.
+     * `rule` is a machine-readable path that points to the specific rule that failed validation.
+     * This will be a nested field starting from the FieldRules of the field that failed validation.
+     * For custom rules, this will provide the path of the rule, e.g. `cel[0]`.
      *
      * For example, consider the following message:
      *
@@ -7594,7 +7979,7 @@ export type ViolationJson = {
      * message Message {
      *   bool a = 1 [(buf.validate.field).required = true];
      *   bool b = 2 [(buf.validate.field).cel = {
-     *     id: "custom_constraint",
+     *     id: "custom_rule",
      *     expression: "!this ? 'b must be true': ''"
      *   }]
      * }
@@ -7617,15 +8002,15 @@ export type ViolationJson = {
      */
     rule?: FieldPathJson;
     /**
-     * `constraint_id` is the unique identifier of the `Constraint` that was not fulfilled.
-     * This is the same `id` that was specified in the `Constraint` message, allowing easy tracing of which rule was violated.
+     * `rule_id` is the unique identifier of the `Rule` that was not fulfilled.
+     * This is the same `id` that was specified in the `Rule` message, allowing easy tracing of which rule was violated.
      *
-     * @generated from field: optional string constraint_id = 2;
+     * @generated from field: optional string rule_id = 2;
      */
-    constraintId?: string;
+    ruleId?: string;
     /**
      * `message` is a human-readable error message that describes the nature of the violation.
-     * This can be the default error message from the violated `Constraint`, or it can be a custom message that gives more context about the violation.
+     * This can be the default error message from the violated `Rule`, or it can be a custom message that gives more context about the violation.
      *
      * @generated from field: optional string message = 3;
      */
@@ -7641,7 +8026,9 @@ export type ViolationJson = {
  * Describes the message buf.validate.Violation.
  * Use `create(ViolationSchema)` to create a new message.
  */
-export declare const ViolationSchema: GenMessage<Violation, ViolationJson>;
+export declare const ViolationSchema: GenMessage<Violation, {
+    jsonType: ViolationJson;
+}>;
 /**
  * `FieldPath` provides a path to a nested protobuf field.
  *
@@ -7678,7 +8065,9 @@ export type FieldPathJson = {
  * Describes the message buf.validate.FieldPath.
  * Use `create(FieldPathSchema)` to create a new message.
  */
-export declare const FieldPathSchema: GenMessage<FieldPath, FieldPathJson>;
+export declare const FieldPathSchema: GenMessage<FieldPath, {
+    jsonType: FieldPathJson;
+}>;
 /**
  * `FieldPathElement` provides enough information to nest through a single protobuf field.
  *
@@ -7870,16 +8259,18 @@ export type FieldPathElementJson = {
  * Describes the message buf.validate.FieldPathElement.
  * Use `create(FieldPathElementSchema)` to create a new message.
  */
-export declare const FieldPathElementSchema: GenMessage<FieldPathElement, FieldPathElementJson>;
+export declare const FieldPathElementSchema: GenMessage<FieldPathElement, {
+    jsonType: FieldPathElementJson;
+}>;
 /**
- * Specifies how FieldConstraints.ignore behaves. See the documentation for
- * FieldConstraints.required for definitions of "populated" and "nullable".
+ * Specifies how FieldRules.ignore behaves. See the documentation for
+ * FieldRules.required for definitions of "populated" and "nullable".
  *
  * @generated from enum buf.validate.Ignore
  */
 export declare enum Ignore {
     /**
-     * Validation is only skipped if it's an unpopulated nullable fields.
+     * Validation is only skipped if it's an unpopulated nullable field.
      *
      * ```proto
      * syntax="proto3";
@@ -8018,7 +8409,7 @@ export declare enum Ignore {
      * The validation rules of this field will be skipped and not evaluated. This
      * is useful for situations that necessitate turning off the rules of a field
      * containing a message that may not make sense in the current context, or to
-     * temporarily disable constraints during development.
+     * temporarily disable rules during development.
      *
      * ```proto
      * message MyMessage {
@@ -8034,8 +8425,8 @@ export declare enum Ignore {
     ALWAYS = 3
 }
 /**
- * Specifies how FieldConstraints.ignore behaves. See the documentation for
- * FieldConstraints.required for definitions of "populated" and "nullable".
+ * Specifies how FieldRules.ignore behaves. See the documentation for
+ * FieldRules.required for definitions of "populated" and "nullable".
  *
  * @generated from enum buf.validate.Ignore
  */
@@ -8045,7 +8436,7 @@ export type IgnoreJson = "IGNORE_UNSPECIFIED" | "IGNORE_IF_UNPOPULATED" | "IGNOR
  */
 export declare const IgnoreSchema: GenEnum<Ignore, IgnoreJson>;
 /**
- * WellKnownRegex contain some well-known patterns.
+ * KnownRegex contains some well-known patterns.
  *
  * @generated from enum buf.validate.KnownRegex
  */
@@ -8068,7 +8459,7 @@ export declare enum KnownRegex {
     HTTP_HEADER_VALUE = 2
 }
 /**
- * WellKnownRegex contain some well-known patterns.
+ * KnownRegex contains some well-known patterns.
  *
  * @generated from enum buf.validate.KnownRegex
  */
@@ -8081,25 +8472,25 @@ export declare const KnownRegexSchema: GenEnum<KnownRegex, KnownRegexJson>;
  * Rules specify the validations to be performed on this message. By default,
  * no validation is performed against a message.
  *
- * @generated from extension: optional buf.validate.MessageConstraints message = 1159;
+ * @generated from extension: optional buf.validate.MessageRules message = 1159;
  */
-export declare const message: GenExtension<MessageOptions, MessageConstraints>;
+export declare const message: GenExtension<MessageOptions, MessageRules>;
 /**
  * Rules specify the validations to be performed on this oneof. By default,
  * no validation is performed against a oneof.
  *
- * @generated from extension: optional buf.validate.OneofConstraints oneof = 1159;
+ * @generated from extension: optional buf.validate.OneofRules oneof = 1159;
  */
-export declare const oneof: GenExtension<OneofOptions, OneofConstraints>;
+export declare const oneof: GenExtension<OneofOptions, OneofRules>;
 /**
  * Rules specify the validations to be performed on this field. By default,
  * no validation is performed against a field.
  *
- * @generated from extension: optional buf.validate.FieldConstraints field = 1159;
+ * @generated from extension: optional buf.validate.FieldRules field = 1159;
  */
-export declare const field: GenExtension<FieldOptions, FieldConstraints>;
+export declare const field: GenExtension<FieldOptions, FieldRules>;
 /**
- * Specifies predefined rules. When extending a standard constraint message,
+ * Specifies predefined rules. When extending a standard rule message,
  * this adds additional CEL expressions that apply when the extension is used.
  *
  * ```proto
@@ -8116,7 +8507,7 @@ export declare const field: GenExtension<FieldOptions, FieldConstraints>;
  * }
  * ```
  *
- * @generated from extension: optional buf.validate.PredefinedConstraints predefined = 1160;
+ * @generated from extension: optional buf.validate.PredefinedRules predefined = 1160;
  */
-export declare const predefined: GenExtension<FieldOptions, PredefinedConstraints>;
+export declare const predefined: GenExtension<FieldOptions, PredefinedRules>;
 //# sourceMappingURL=validate_pb.d.ts.map