feat(explanation): introduce Anbox VHAL adpater

.wordlist.txt

@@ -53,3 +53,4 @@ UUID
 VM
 YAML
 shaders
+adapter

explanation/aaos.md

@@ -9,6 +9,12 @@ Since the 1.21.0 release, in addition to providing images based on the Android O
 
 The [Vehicle Abstraction Layer (VHAL)](https://source.android.com/docs/automotive/vhal) enables Android Automotive to communicate with and control the different vehicle hardware controls.
 
+Before the 1.24.0 release, if you created your own VHAL implementation by following the [instructions](https://documentation.ubuntu.com/anbox-cloud/en/latest/howto/android/custom-vhal/) and loaded it as an addon during the Android runtime, vehicle properties and configurations were not visible on the Anbox Cloud dashboard. With the 1.24.0 release, Anbox Cloud introduced a VHAL adapter that acts as a bridge between the Anbox runtime and the VHAL implementation for data transmission. The Anbox VHAL adapter processes messages sent from the Anbox runtime, performs operations against the VHAL implementation(such as retrieving a list of property configurations), and sends the results back to the Anbox runtime. As a result, vehicle properties and configurations are now visible on the Anbox Cloud dashboard for the third-party VHAL implementations.
+
+If the third-party VHAL implementation is loaded during Android runtime, on the Anbox Cloud Dashboard, some vehicle property values may not be accessed, while others may not be editable due to [permission controls](https://source.android.com/docs/automotive/vhal/previous/properties#vehicle-props) that categorise vehicle properties as read-only, write-only, or read-write.
+
+In the 1.24.1 release, Anbox Cloud will introduce an `IVehicle` HIDL interface that third-party VHAL implementations can use to modify non-writable vehicle property values or access non-readable vehicle property values. This will enable the Anbox VHAL adapter to communicate directly with the VHAL implementation that implements the `IVehicle` HIDL interface and manage those vehicle properties without facing permission issues.
+
 ## Related topics
 
 * {ref}`ref-aosp-aaos`