01 — Architecture
System-level design of the p24-infra platform: how services relate, the element taxonomy used throughout the codebase, and the forward-looking modernisation roadmap.
The architecture follows a hub-and-spoke model: two VPS nodes (vps-i1 and vps-h1) plus four bare-metal OVH servers (bms-1 through bms-4), all observed by a Prometheus/Thanos stack on vps-i1. Application traffic is Pinbox24 on bms-1; the fleet platform (et-operational-platform) lives on Vercel backed by Supabase.
Key Documents
| Document | Description |
|---|---|
| architecture.md | High-level system architecture diagram and component relationships |
| elements.md | Canonical element registry — VPSes, containers, SaaS, scripts |
| infrastructure-overview.md | Full infrastructure map across all projects, servers, and secrets |
| infrastructure-standard.md | Compliance requirements every new element must satisfy |
Evaluation & Roadmap
| Document | Description |
|---|---|
| README.md | Index of all evaluation reports |
| 00-documentation-audit.md | Documentation coverage audit |
| 01-service-distribution.md | Service distribution analysis across servers |
| 02-bms-modernization-plan.md | BMS server modernisation roadmap |
| 03-nightly-ops-and-mongodb.md | MongoDB rs0 nightly operations analysis |
| 04-pinbox24-map-dr-audit.md | Pinbox24 disaster-recovery audit |
Standards
| Document | Description |
|---|---|
| project-standards.md | Project-level conventions and naming rules |
| element-spec-template.md | Template for registering new elements in dev_r_services |
| workbook-template.md | Template for audit-engine workbooks |
| README.md | Improvement proposals index |