Update virtual table policy diagram.md

Author: thecppzoo

design/virtual table policy diagram.md

@@ -14,8 +14,8 @@ The most important feature of this flavor of the framework is to use virtual tab
 2. The type of the virtual table is the aggregation of the `VTableEntry` types of each affordance: [`struct VTable: AffordanceSpecifications::VTableEntry... {`](https://github.com/thecppzoo/zoo/blob/d6435fc984ee0bde31979f7908a73473f61ac4bd/inc/zoo/Any/VTablePolicy.h#L247C5-L247C60)
 3. The `VTHolder` allows every affordance to access its part of the virtual table via the template member `vTable`, if `Affordance` is the type representing an affordance, `baseManager->template vTable<Affordance>()` returns that section of the virtual table.
 4. The base value manager is the provider of the implementations for the default constructed `AnyContainer`.
-    1. Implementations are either `constexpr` data, or more typically, the pointers to the functions that implement the behaviors.  The base manager must defer to the affordances for these values, in particular to the `Default` class-members of the affordances, which are assumed to be of their `VTableEntry` type [^DefaultImplementations]
-6. The so-called "concrete value managers" provide the implementations for the value they manage.
+    1. Implementations are either `constexpr` data, or more typically, the pointers to the functions that implement the behaviors.  The base manager must defer to the affordances for these values, in particular to the `Default` class-members of the affordances, which are assumed to be of their `VTableEntry` type.  The `Default`s of the affordances are templates that expect to receive the type of base manager. [^DefaultImplementations].  Furthermore, the convention is that the functions in the virtual table entries of the affordances will receive a pointer to the base value manager, as a `void *`, but this is an affordance-maker decision.
+6. The so-called "concrete value managers" provide the implementations for the value they manage: `constexpr static inline VTable Operations = { AffordanceSpecifications::template Operation<ConcreteValueManager>... };`, they refer to the `Operations` member of the affordances, and indicate 
 
 [^DefaultImplementations]: Code for assembling the default-constructed behaviors:
     The virtual table of default-constructed `AnyContainer`: