# Changelog

## Score

- CAI 71 → 71 (+0.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 100 → 100 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 65 → 65 (+0.0)
- Readiness 69 → 69 (+0.0)
- Security 100 → 100 (+0.0)

## Resolved (3)

- Confusing naming convention and type mismatch between 'draw' and 'add' methods. 'draw' methods accept raw Arrow objects, while 'add' methods accept DrawnArrow objects. The distinction between 'drawing' (visualizing) and 'adding' (registering in the graph) is unclear, especially since both modify the graph state. Furthermore, the plural/singular naming convention is inconsistent with the parameter types (e.g., drawArrows takes a single Arrow, not an array).
- Inconsistent construction patterns. Arrow uses a fluent builder pattern (from/via) but requires an EventName in the constructor. DrawnArrow requires all three components in the constructor. This creates two different ways to create arrow-like objects with different requirements and interfaces.
- Redundant interface/method signatures across different types. Both Event and NamedEvent have a name() method returning EventName, and similarly for State/NamedState. It is unclear if NamedEvent/NamedState are distinct types or if Event/State are abstract interfaces. If they are distinct, the identical method signatures suggest a lack of clear inheritance or interface segregation.
