Merge branch 'main' into provider-hooks

Author: beeme1mr

specification.json

@@ -284,6 +284,20 @@
             "RFC 2119 keyword": "MUST",
             "children": []
         },
+        {
+            "id": "Requirement 3.1.3",
+            "machine_id": "requirement_3_1_3",
+            "content": "The evaluation context MUST support fetching the custom fields by key and also fetching all key value pairs.",
+            "RFC 2119 keyword": "MUST",
+            "children": []
+        },
+        {
+            "id": "Requirement 3.1.4",
+            "machine_id": "requirement_3_1_4",
+            "content": "The evaluation context fields MUST have an unique key.",
+            "RFC 2119 keyword": "MUST",
+            "children": []
+        },
         {
             "id": "Requirement 3.2.1",
             "machine_id": "requirement_3_2_1",

specification/sections/03-evaluation-context.md

@@ -32,6 +32,16 @@ The targeting key uniquely identifies the subject (end-user, or client service)
 
 see: [structure](../types.md#structure), [datetime](../types.md#datetime)
 
+#### Requirement 3.1.3
+
+> The evaluation context **MUST** support fetching the custom fields by key and also fetching all key value pairs.
+
+#### Requirement 3.1.4
+
+> The evaluation context fields **MUST** have an unique key.
+
+The key uniquely identifies a field in the `evaluation context` and it should be unique accross all types to avoid any collision when marshelling the `evaluation context` by the provider.
+
 ### Merging Context
 
 #### Requirement 3.2.1