Blame
|
1 | # Service Catalogue |
||||||
| 2 | ||||||||
| 3 | The service catalogue is the navigation layer between business/product names and their technical components. |
|||||||
| 4 | ||||||||
| 5 | ## Catalogue model |
|||||||
| 6 | ||||||||
| 7 | Each product or service should document: |
|||||||
| 8 | ||||||||
| 9 | - purpose and audience; |
|||||||
| 10 | - owning product family/team or maintainer; |
|||||||
| 11 | - source repository/repositories; |
|||||||
| 12 | - production/runtime entry points; |
|||||||
| 13 | - upstream/downstream dependencies; |
|||||||
| 14 | - authentication and data stores at a descriptive level; |
|||||||
| 15 | - monitoring/runbook links; |
|||||||
| 16 | - lifecycle status such as active, experimental, deprecated or retired. |
|||||||
| 17 | ||||||||
| 18 | ## Current catalogue |
|||||||
| 19 | ||||||||
| 20 | ### Voxel Horizons |
|||||||
| 21 | ||||||||
| 22 | - **VoxelCore** — version-aware Minecraft content foundation. See [[Products/Voxel-Horizons/VoxelCore/Index]]. |
|||||||
| 23 | ||||||||
| 24 | Additional Soatrix products can be added beneath [[Products/Index]] without changing the company-level structure. |
|||||||