Performance

Hyperscale-first: for the same effort, prefer the shape that scales further. When you can't scale today, ship the simple path + open a follow-up — performance is not late-stage optimization, it's a design column.

Commitment

Scalability × efficiency × sustainability triad applied to every architectural call. Per-module perf budgets tracked in registries/perf-baseline.md. Self-prune for hot data, mandatory cache layers above sub-1ms hot paths, horizontal scaling baked in from commit 1.

Canonical specs

policies/hyperscale-first.kmd · registries/perf-baseline.md · rfcs/stack-RFC-001-kdb-as-unified-data-plane.kmd. Owner-curated expansion will cover per-surface baselines and degradation criteria.