This page identifies a possible issue, inconsistency, concern, error, or bug!
One of the ways Webel IT Australia helps promote tools, technologies, and languages is by donating a lot of time identifying, tracking, and reporting potential issues, in order to help vendors and developers improve the tools and technologies. In some cases, we also offer workarounds and advice for users. All issues tracked on our public site are offered most constructively and with sincerest gratitude to the tool vendors and technology developers.
DISCLAIMER: Vendors do not officially endorse issue analysis by Webel IT Australia.
This is likely either a tool “feature short-coming” or an actual issue.
Although a requirement usage is a special kid of constraint usage, the additional require keyword should only be used for regular required constraint usages, NOT with subrequirements, at least according to the example in the SysML2.0 spec. p.135 and some related SysMLv2 GitHub examples. This may have something to do with this "issue" (maybe Cameo doesn't "see" that the requirement usages are constraint usages).
However, evaluations of similar models in Cameo work just fine and consistently (suggesting it's merely a display issue or policy).
In any case, it would be nice to just be able to list the subrequirements in a compartment.