Naming Convention¶
Why This Exists¶
This convention makes the repository predictable as the Algosure Blueprint grows.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Predictable naming improves navigation, search, review, and long-term maintainability.
File Naming¶
Use descriptive Markdown file names.
| Content Type | Convention | Example |
|---|---|---|
| Foundation standards | Title case with hyphens | Metadata-Standard.md |
| Section overview | README.md or index.md where already established |
README.md |
| Decision records | Numeric prefix and lowercase slug | 0001-record-blueprint-decisions.md |
| Diagrams | Lowercase descriptive slug | blueprint-foundation-flow.mmd |
Concept Naming¶
Use consistent names for Blueprint concepts:
- Practices
- Digital Professionals
- Business Capabilities
- SOPs
- Organizational Memory
- AI reasoning
- Executable workflows
One Concept, One Owner¶
Do not create multiple names for the same concept unless a standard explicitly defines synonyms. Each concept name must map to one accountable owner.
Naming Restrictions¶
- Do not use ambiguous abbreviations.
- Do not encode temporary sprint names into permanent concept names.
- Do not rename a governed concept without updating cross-references.