-More than that, these are all "general-purpose" opcodes with uses far beyond LibreSOC's use-case (notwithstanding LibreSOC's use-case itself being by definition general-purpose). More than that, given that LibreSOC is targeting high-profile mass-volume general-purpose computing, it is our duty and responsibility to ensure that use of EXT22 does not result in end-user developer pressure for upstream tool-chains to override the OPF's intentions, by *unintentionally* de-facto dominating (effectively allocating) EXT22 for LibreSOC use.
+More than that, these are all "general-purpose" opcodes with uses far beyond LibreSOC's use-case (notwithstanding LibreSOC's use-case itself being by definition general-purpose).
+
+More than that, going far beyond the "letter" of our obligations to respect the stability of the OpenPOWER ecosystem, given that LibreSOC is targeting high-profile mass-volume general-purpose computing, it is our duty and responsibility to ensure that use of EXT22 does not result in end-user developer pressure for upstream tool-chains to override the OPF's remit, by *unintentionally* de-facto dominating EXT22 for LibreSOC use simply by popular overwhelming end-user demand, outside of everyone's control.
+
+We are also getting slightly concerned in that the resources needed (SPR allocations, allocation of Reserved v3.1 64 bit EXT01 prefix space to support SVP64) is quite large, and well outside of the "anticipated" resources allocated for Sandboxing. There is no allocation of EXT01 *at all* for example. Yet after one year we still have no two-way communications channel established to discuss even the possibility of additional reservations.