Repositories
Phimi follows the same four-repository layout as the aidj platform. All are private repositories in the phimi-track organization.
| Repository | Contents | Image |
|---|---|---|
| phimi-platform | Rust workspace: protocol, ingest, core, commands, storage, API, simulator; PostgreSQL migrations; vendor frame fixtures | registry.bitview.club/phimi/phimi-platform |
| phimi-ui | Next.js dashboard | registry.bitview.club/phimi/phimi-ui |
| phimi-docs | This Docusaurus site, plus the original vendor documents in vendor/ (not published) | registry.bitview.club/phimi/phimi-docs |
| phimi-devops | Kubernetes manifests and Argo CD application for namespace phimi | — |
Platform crates
| Crate | Responsibility |
|---|---|
phimi-protocol | 0x7E framing, 0x7D escaping, XOR checksum, BCD terminal id, typed uplink/downlink messages |
phimi-ingest | Tokio TCP server: sessions, registration/authentication, ACKs, duplicates, downlinks, Prometheus metrics |
phimi-core | Location source, plausibility, device clock, "older point never replaces the latest" |
phimi-commands | V53 command texts and the command lifecycle |
phimi-storage | SQLx pool and embedded migrations |
phimi-api | Axum REST/WebSocket API; phimi-api migrate runs migrations |
phimi-simulator | Virtual V53 replaying the vendor exchanges over TCP |
Release flow
Build each repository's Dockerfile, push an immutable tag to Harbor, take the digest,
and pin it in phimi-devops. Argo CD applies the change. Rolling back means reverting
the digest commit.