Skip to content

Engineering Standard — Naming Convention and Taxonomy

Standard ID: STD-034
Parent: Document Authority Metadata Standard (STD-033)
Applies to: All documents in Engineering-Standard/


File Naming Convention

Rule Pattern Example
Lowercase kebab-case word-word-word.md git-discipline.md
No spaces or underscores — ❌ Git_Standard.md
Standard ID prefix for standards std-NNN-name.md or STD-NNN-name.md std-exec-001-execution-environment-constitution.md
Platform-specific standards PLATFORM-NNN-name.md APPLE-001-provider-authority.md
ADRs ADR-NNNN-short-title.md ADR-0001-adopt-gas-city.md
Dated snapshots name-YYYY-MM-DD.md oracle-runtime-topology-2026-07-30.md

Exception: Uppercase directory names (e.g., Runtime/) are used when the UCD uniqueness law (GOV-UCD-LAW-001) requires it.


Directory Taxonomy

Directory Content Type Owner Layer
indexes/ Navigation, executive entry points Engineering Standard
operating-model/ Factory contracts, operating models Engineering Standard
architecture/ Core architecture docs Engineering Standard
authority/ Governance identities, team model, authority matrices Engineering Standard
standards/ Normative technical standards Engineering Standard
standards/core/ Core platform-wide standards (auth, paths, evidence, Git) Engineering Standard
standards/architecture/ Architecture-level standards Engineering Standard
standards/platforms/ Platform-specific standards Engineering Standard
standards/platforms/apple/ Apple/iOS/macOS standards Engineering Standard
standards/platforms/runtime/ BluCity/Gas City runtime standards Engineering Standard
standards/platforms/security/ Security standards Engineering Standard
rules/ Binding operational rules (ES-, GOV-) Engineering Standard
governance/ Constitution, compliance policies Engineering Standard
decision-records/ ADRs Engineering Standard
catalog/ Capability/technology/tool inventories Engineering Standard
reference/ CLI resources, diagrams, templates, archived snapshots Engineering Standard
context-plane/ QMD, orbit, workspace-integration Engineering Standard
infrastructure/ Cloud, Oracle, NAS, Terraform docs Engineering Standard
Runtime/ UCD law (authoritative path required uppercase) Engineering Standard
templates/ Governed document templates Engineering Standard
glossary/ Platform terminology Engineering Standard

Document Status Taxonomy

Status Meaning
evergreen Actively maintained; accurate as of updated_at
canonical Accepted as standard practice; authoritative
snapshot Point-in-time capture; may be out-of-date
proposed Awaiting acceptance decision
candidate Under consideration, no commitment
superseded Replaced by a newer document (link the replacement)
draft Work in progress; not yet binding
informational Reference material, non-normative

Full taxonomy: status-legend.md


Required Front Matter (Governed Documents)

All documents with bluefly_document: true MUST include:

---
status: <see taxonomy above>
type: standard | index | rule | architecture | decision | reference | chore
owner: Bluefly Engineering
authority: canonical | informational | not-current
bluefly_document: true
created_at: <ISO-8601>
updated_at: <ISO-8601>
---

Optional fields for standards:

standard_id: STD-NNN
schema: standard-v1
review_cycle: quarterly | annual
supersedes: []
superseded_by: null

Full schema: Document Authority Metadata Standard (STD-033)


Standard ID Registry

Series Prefix Domain
Engineering Standard root ES-NNNN Rules: ES-GITCC, ES-APR, ES-DEPLOY, ES-CI-RUNNER-TOPO-001
Technical Standards STD-NNN General standards (STD-018=BLU-BIBLE, STD-033=doc-authority-metadata, STD-034=this)
Architecture Standards STD-ARCH-NNN Architecture (STD-ARCH-002=platform-agent-execution)
Authorization STD-CEDAR-NNN Cedar (STD-CEDAR-001)
Auth/Secrets STD-AUTH-NNN Auth (STD-AUTH-001)
Governance/Paths GOV-* Governance rules (GOV-PATH-PRIV-001, GOV-UCD-LAW-001)
Repository STD-REPO-NNN Repository standards (STD-REPO-001)
GitLab STD-GITLAB-NNN GitLab standards (STD-GITLAB-001)
Execution STD-EXEC-NNN Execution (STD-EXEC-001)
Apple/iOS APPLE-NNN Apple platform (APPLE-001 through APPLE-004)

Known Naming Issues (Require Resolution)

Issue Documents Status
Duplicate Standard ID ES-DEPLOY rules/deployment-contract.md + rules/deployment-rule.md Needs renumbering — one must change
Root auth duplicate authentication-and-secrets-constitution.md vs core/authentication-secrets-constitution.md Root file should redirect to core/ canonical
Uppercase/lowercase ES-DEPLOY vs es-deploy Mixed case in commit messages Cosmetic only