Webel recommends that you prefer performed actions and exhibited states for the primary mechanism for "logical" layer (or zone) systems engineering functional analysis breakdown (not SysMLv2 allocations).
Please note that this statement is not to detract from the utility of allocations in SysMLv2, but much of what one might previously have used SysMLv1 Allocations for is now built-in to SysMLv2 as performed actions and exhibited states.
One approach it to reserve performed actions and exhibited states for the logical analysis, you can then use SysMLv2 allocations to bridge traceably from logical components to "physical" components, as shown in this SysMLv2 PILOT GitHub sample slide:
That approach offers a clear distinction between the systems engineering layers (or zones), and plays nicely with most systems engineering methodologies. You can also always strengthen the semantics with custom Metadata (and with your "pet" terminology as custom keywords).
To learn more about this policy attend the Webel IT SysMLv2 course: