# Changelog

## Score

- CAI 61 → 68 (+6.7)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 73 → 73 (+0.0)
- Architecture 100 → 100 (+0.0)
- Maturity 47 → 70 (+23.3)
- Readiness 68 → 68 (+0.0)
- Security 71 → 62 (-9.2)
- Performance 95 → 95 (+0.0)

## Resolved (3)

- Ambiguous intent: `register` implies creation, but `retrieve_or_register` implies a lookup-first strategy. While distinct, the naming convention `retrieve_or_register` is verbose and inconsistent with the simple imperative style of `register`, `destroy`, and `unregister`. It suggests a 'get_or_create' pattern that isn't reflected in the other methods.
- Inconsistent naming for bulk operations: `destroy_all_resources` uses the full noun phrase, whereas `unregister_all_resources` also uses the full phrase. However, `Semian.destroy` (singular) vs `Semian.destroy_all_resources` (plural) is slightly inconsistent with the pattern of `Semian.unregister` vs `Semian.unregister_all_resources`. More importantly, `destroy` and `unregister` seem to do similar cleanup but on different scopes or types of resources, which is confusing without clear documentation. If they are distinct (e.g., one removes from LRU, one removes from global registry), the names should reflect that distinction more clearly (e.g., `remove_from_registry` vs `cleanup_lru`).
- Off-boarding risk: anonymized user #1

## New (1)

- Off-boarding risk: anonymized user #1
