Naming standards

File placement

Put the single naming declaration in naming.bluep, or retain it in model.bluep.

Words define declared abbreviations and optional aliases.

Names split at punctuation, case transitions, and digit transitions.

Rules are selected by physical object kind.

Rules choose a case style and may explicitly choose punctuation separators.

Prefixes and suffixes are added after word rendering.

Reserved identifiers can be quoted, rejected, prefixed, or suffixed.

Configured limits are combined with each dialect's identifier limit.

Truncated and colliding names receive stable FNV hash suffixes.

Derivation applies standards only to newly derived physical objects.

bluep naming apply previews a reviewed rename plan before changing files.

The preview can write a migration script using typed rename changes.

Naming lint reports expected physical names without modifying the model.

The text and JSON forms carry words, rules, reserved policy, and limits.

With customer -> CUST, order -> ORD, and line -> LN, an upper-snake table name becomes CUST_ORD_LN.

Naming does not alter database data or raw SQL bodies.