Skip to content

Latest commit

 

History

History
58 lines (48 loc) · 2.74 KB

File metadata and controls

58 lines (48 loc) · 2.74 KB

hpcc — Implementation Plan

hpcc is a distributed compilation and caching tool. A drop-in compiler wrapper that caches build artifacts locally and remotely, and optionally distributes compilation across a cluster of workers — with a strong tenant-isolation story suitable for environments (banks, regulated enterprises) where running user-supplied compilation on shared hardware is politically untenable.

This document is the index. Each phase, plus the cross-cutting structure and design-decisions sections, lives in its own file under plan/. What's done vs. what's open per phase lives in each phase doc — git log is the authoritative chronology.


Status

Phase Description Status
Phase 1 Core Compiler Wrapping Done
Phase 2 Daemon Architecture Done
Phase 3 Remote Cache Done
Phase 4 Distributed Compilation in Per-Tenant VMs Done
Phase 5 Observability & Polish In progress

Contents

Related sub-plans:

  • CAS-mode source dispatch — the §4.5 content-addressed source-staging path. Shipped as the default source_mode = "cas"; PREPROCESSED stays selectable as a fallback. Probe-then-upload, .hpcc project marker for cross-developer hits, paranoid-mode- friendly trust boundary, .S/.incbin support.
  • Multi-tenant isolation — promoting tenant_id from a JWT label to a namespace boundary: per-tenant IdP at the scheduler, per-tenant storage prefixes on every store, per-tenant upload quota on UploadBlobs. Closes the §4.5 cross-tenant probe disclosure by construction.