Nomenclature

Why Nomenclature Matters

Provisionr’s nomenclature is a system of naming conventions and identifiers designed to be clear, consistent, and automation-friendly. Every resource — whether it’s a group, a shared drive, a role, or a mail pipeline — follows the same structural rules. This means humans can read a name and immediately understand what it is, who owns it, and where it belongs. It also means machines can parse, lint, and enforce these names without ambiguity.

Our organization was founded by security and software engineers. You’ll encounter technical patterns throughout, but we write for accessibility. If you can read a kebab-case string, you can navigate our systems.

The Big Trade-Off

The most notable thing you’ll need to give up is Title Case strings with spaces. We use abbreviated kebab-case for all identifiers — lowercase words separated by hyphens.

Instead of:

Provisionr Sales Forecast - 2026 Q1

You’ll see:

prv-sal-doc-forecast-2026-q1

This takes some getting used to, but it keeps everything parseable, sortable, and consistent across every system we touch.

The Anatomy of a Name

Every identifier follows the same octet structure:

prv-{team}-{type}-{qualifier}

Octet	Purpose	Example
1st — Org prefix	Which organization	prv
2nd — Team / Department	Who owns or operates it	plt, eng, sec, sal
3rd — Type	What kind of thing it is	role, mail, admin, doc
4th+ — Qualifier	Specifics (system, scope, env, etc.)	aws-admin, forecast-2026-q1

This is the universal pattern. It applies to Google Groups, shared drives, role assignments, mail pipelines, automation accounts, project identifiers, and more.

For a deep dive into every token and pattern, see the Naming Anatomy series.

Short Abbreviations

We use short abbreviations to keep identifiers compact and scannable. Most are three letters, but two-letter abbreviations are fine where the meaning is clear and unambiguous (e.g., hr, it, op, gl, tf, zm).

If an abbreviation isn’t obvious or hasn’t been added to Librarian, spell it out. Clarity wins over brevity every time.

See the full Abbreviations reference.

Organization Prefixes

Provisionr’s founders operate multiple organizations. Each gets a three-letter prefix:

Prefix	Organization
prv	Provisionr (primary)
ocs	Our Collaborative Space
pqx	Piqued X
psl	Piqued Solutions
pst	Piqued Studios
pai	Piqued AI
bgh	Boldly Grow Holdings

You’ll almost always see prv. The others appear in cross-tenant or legacy contexts.

Structural Concepts

Kebab-Case

All identifiers are lowercase, hyphen-separated. Never camelCase or PascalCase unless forced by a specific system (and even then, document the exception).

prv-plt-role-aws-admin    ✅
Prv-Plt-Role-AWS-Admin    ❌
prvPltRoleAwsAdmin        ❌

Dot Notation

For hierarchical data within a system (not identifiers), we use dot notation:

user.profile.department
config.mail.intake.source

Snake Case

Some systems require underscores. When forced, use snake_case. But for our canonical identifiers, kebab-case is always preferred.

What’s Next

This guide is organized as a series of pages, each focused on a specific concept:

1. Naming Anatomy — Syntax rules, tokens, and canonical patterns
2. Groups — People, departments, teams, and automation accounts
3. Roles & Permissions — How we model access
4. Mail Pipelines — The four-pipe model for mail routing
5. Projects — Customer, vendor, and partner engagement models
6. Operations — SOPs, lifecycle management, and governance
7. Systems — System-specific conventions (Google Workspace, AWS, Platform Engineering, Git)
8. Reference — Regex rules, decision guides, and worked examples