# Score Sheet

**Kata ID:** C1-capability-growth-boundary
**Run ID:** C1-cold-001

| Dimension | Score (0–4) | Why |
|-----------|-------------|-----|
| α Pattern | 2 | It had the rough idea ("don't hardcode everything into core") but lacked a fully shaped architecture artifact. |
| β Relation | 2 | It blurred runtime extension mechanics with marketplace/app-store concerns. |
| γ Exit | 2 | It suggested the right general direction but not a clean migration or layering story. |
| Efficiency | 4 | Cheap and quick. |

## Positive Signals

- [x] Recognized repeated core accretion as the deeper pressure.
- [x] Did not simply choose "hardcode into core."

## Negative Signals

- [x] Did not separate extension vs registry vs app/bundle.
- [x] Weak leverage / negative leverage articulation.
- [x] Weak process-economics reasoning.

## Transfer Assessment

- none yet

## Cost Assessment

- cheap

## Final Classification

- selection-limited
