chore: field names must not be verbs. (#1078)

chore: field names must not be verbs.

Add guidance that field names must not be expressed in the context
of imperatives or actions, as verbs.

Fixes: #1077

Author: shwoodard

aip/general/0140.md

@@ -88,6 +88,20 @@ For uniformity, field names that contain both a noun and an adjective
 - `collected_items` (**not** `items_collected`)
 - `imported_objects` (**not** `objects_imported`)
 
+### Verbs
+
+Field names **must not** be named to reflect an intent or action. They
+**must not** be verbs. Rather, because the field defines the *desired
+value* for mutations, e.g. Create and Update, and the *current value*
+for reads, e.g.  Get and List, the name **must** be a noun. It defines
+what is so, not what to do.
+
+- `collected_items` (**not** `collect_items`)
+- `disabled` (**not** `disable`)
+
+In contrast, method names, whether standard or custom, change facets of
+resources and are named as verbs.
+
 ### Booleans
 
 Boolean fields **should** omit the prefix "is". For example:
@@ -142,6 +156,7 @@ field **should not** have a uniqueness requirement.
 
 ## Changelog
 
+- **2023-04-25**: Field names **must not** be expressed as verbs.
 - **2021-07-12**: Normalized display name guidance to "should".
 - **2021-04-07**: Added base64 and bytes guidance.
 - **2021-03-05**: Added prohibition on leading, trailing, or adjacent