You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ad6ea53
Browse filesBrowse the repository at this point in the historyBrowse files
fix(requirements): architectural nesting is the contract, and Java's link floor obeyed it
The full reactor caught a stale test the java-fast lane could not: it runs the
whole metadata suite, where java-fast runs four named classes.
RequirementTest.architecturalRequirement_doesNotNest asserted the PRE-0.23.0
rule -- that architectural declares no nested-requirement child rule, because an
architectural requirement is object-independent and so has no tier to contain.
That reasoning holds for a FLAT policy and stopped being the whole story when
`@level` became optional: levelling is opt-in so a quality taxonomy can organise
the non-functional set the way a capability taxonomy organises the functional
one. Inverted to architecturalRequirement_nests.
Added architecturalRequirement_levelledTreeLoads, pinning the whole shape the
optional `@level` exists for -- L1 to L2 to L4, @disposition, @trackedBy, and the
link floor on both tiers.
IT IMMEDIATELY CAUGHT A BUG IN THE PORT IT WAS WRITTEN FOR. Java's
mayReferenceModel still returned true for ANY architectural node -- the identical
defect fixed in C# and Python two commits ago and missed here -- so a levelled L1
grouping node could name entities. Now matches every other port: an UNLEVELLED
architectural node always may, a LEVELLED one obeys the floor.
Then a sweep for the retired doctrine, because a rule that changes leaves
assertions behind:
- Java checkValidChild's javadoc still said the child rule is declared on
`functional` only.
- C#'s Status docstring listed four statuses, omitting `planned`.
- Java ValidationPhase's @status comment did the same.
- A TS test asserted the loader error contains
"live, partial, abandoned, superseded" -- which PASSED BY SUBSTRING LUCK
against the real five-value message, and would have stayed green if
`planned` were dropped from the set entirely. Now asserts all five.
java-reactor (install): green. metadata suite green, RequirementTest 7/7, TS
cli suite 47 pass.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
0 commit comments