Clustersco Engineering
The engineering handbook for Clustersco Inc. — the standards, playbooks, and design language every repo and every team member follows. The organizing idea is simple:
One organization, one shape. A new product, module, or client is a fill-in-the-template operation — never a redesign.
Start here
| If you want to… | Read |
|---|---|
| Understand how the code is layered | Project Architecture — CORE / MODULES / APPS |
| Branch, release, or version anything | Git & Versioning Workflow — the interactive standard |
| Ship a build safely | Build & Deploy — environments & promotion |
| Set up delivery | Governance — Jira · Confluence · Compass |
| Build a UI or a doc | Design System · UI/UX |
| Do a specific operation | Playbooks — new app / module / release / client |
The three layers
Everything is CORE → MODULES → APPS, mirrored across Git, Jira, and Compass:
- CORE — the platform foundation (Clustercore). One base repo per core line.
- MODULES — reusable modules, consumed by apps as git submodules pinned to tags.
- APPS — the assembled, shippable products (
bgvchecker,clustersky).
The one rule to remember
One string identifies a release everywhere — the git tag = the version.yml entry = the
Docker image tag (SemVer, no v prefix). Get that right and the rest of the system follows.