# Changelog

## Score

- CAI 50 → 48 (-1.6)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 75 → 75 (+0.0)
- Architecture 94 → 94 (-0.5)
- Maturity 50 → 50 (+0.0)
- Readiness 33 → 32 (-0.2)
- Security 70 → 59 (-10.8)
- Domain Modelling 100 → 100 (+0.0)
- Performance 80 → 80 (+0.0)

## Resolved (6)

- Inconsistent argument order for `associate`. `ManyToMany` takes `(children, parent)`, while `ManyToOne` and `OneToMany` take `(child, parent)`. This inconsistency in argument ordering (plural vs singular, order of entities) can lead to bugs when switching between association types.
- Inconsistent constructor signatures for 'new'. `Changeset.new` takes `(relation, options)`, while `Pipe.new` has two distinct signatures: `(args, opts)` and `(processor, opts)`. This lack of uniformity in how new instances are created across related change-processing types is confusing.
- Inconsistent invocation methods for commands. ROM.Command exposes both `execute` and `call`, while CommandProxy and specific command types (Graph, Lazy) only expose `call`. This creates ambiguity for users on whether to use `execute` or `call` for standard commands.
- Off-boarding risk: anonymized user #1
- Split core
- While `fetch_or_store` is consistent between Cache and Namespaced Cache, the base ROM.Cache class also exposes `[](key)` for reading, whereas Namespaced Cache also exposes `[](key)`. However, the primary inconsistency is that `ROM.Cache` has `[](key)` but `ROM.Cache.Namespaced` also has `[](key)`. This is actually consistent. A better inconsistency is found in `ROM.Command` vs `ROM.CommandProxy`. `Command` has `execute` and `call`. `CommandProxy` only has `call`. `Lazy` commands only have `call`. This suggests `execute` is legacy or redundant.

## New (3)

- Floating git dependency: rom-sql
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion
