anchor.diff:  
   The `SubpackageEnum` provides an off the shelf implementation; you will probably want to copy this and adjust as necessary.
   
  -To run the test itself, use:
  +To run the test, use:
   
   [source,java]
   ----
   @ArchTest
  -public static ArchRule code_dependencies_follow_module_Imports_and_subpackage_rules =
  -      code_dependencies_follow_module_Imports_and_subpackage_rules(
  -          analyzeClasses_packagesOf(ModulesArchTests.class),
  -            asList(SimplifiedSubpackageEnum.values()));
  -----
  +public static ArchRule code_deps_follow_module_Imports_and_subpackage_rules =
  +      code_dependencies_follow_module_Imports_and_subpackage_rules(     // <.>
  +          analyzeClasses_packagesOf(ModulesArchTests.class),            // <.>
  +          asList(SimplifiedSubpackageEnum.values()));                   // <.>
  +----
  +<.> architecture test itself, imported from `ArchitectureModuleRules`
  +<.> utility that passes in for all analysis all of the module classes that are annotated on `Architecture_Test`.
  +<.> list of the ``Subpackage``s whose relationships are to be checked
   
   where for example `Subpackage` is implemented using with:
   
  
positive.code: == Domain rules
  
  Checks for rules defined against domain classes reside in the `ArchitectureDomainRules` library.
  None of these rules take any arguments, so simply include (as a static field) those that you wish to enforce.
  
  * logical type name:
  
  
negative.code: ** `every_finder_method_in_Repository_must_return_either_Collection_or_Optional()`
  
  
  None of these rules take any arguments, so simply include (as a static field) those that you wish to enforce.
  
  == Entity Checks
  
  Entity rule checks are provided for both xref:pjpa::about.adoc[] and xref:pjdo::about.adoc[], in `ArchitectureJpaRules` and `ArchitectureJdoRules` respectively:
  
  * ensure conformance of persistence vs Isis annotations:
  
  