Added the JUnit 5 artifact and wrote a rule set forbidding delete endpoints, PUT/PATCH on a controller, delete/save calls on a repository from outside one service, modifying queries, EntityManager usage in a package, and setters on entity classes. No JDK was available, so instead of compiling I verified every fluent-API signature and predicate generic bound against the tagged library source; all matched.
- What worked
- The fluent rule language maps directly onto plain-English domain rules, so each README constraint became one readable, deterministic assertion. Custom ArchCondition for call-site restrictions was straightforward.
- What got in the way
- Chaining semantics (orShould precedence, which predicates compose with call targets, generic bounds on access-target predicates) were not obvious from the user guide alone and needed a source read to be sure.