b46667c309
The groups/project-tool work had no home in the blueprint's version scheme, two "Phase N" numbering schemes overlapped, and CLAUDE.md's "current focus" was stale (claimed v1.1.0 SDK foundation; we're at v1.1.9 with the SDK line complete). Reconcile all three: * blueprint §12 Phase 5 (v1.2, already titled "Advanced Workflows & Hierarchies") — split into a Hierarchies track (the groups + project tool initiative, with §11 Phases 1–3 marked shipped) and a Workflows track, with sequencing flagged as an open call. This gives the work an explicit version home: the Hierarchies half of v1.2. * design doc header — Status Draft → Active, "scheduled as the Hierarchies track of v1.2", and an explicit warning that §11's local Phase 1–6 numbering is distinct from the blueprint product-phase numbering. * design doc §11.1 — a post-Phase-3 re-sequencing review: resolve Phase 4 scripts LIVE (drop the fan-out-invalidation sub-project, per the Phase 3 result); consider a "Phase 5-lite" (declarative apply of vars/secrets + app scripts) before the hard group-scripts work; and force the two deferred decisions (trigger/route templates vs tenant cardinality; multi-repo ownership vs a single-repo start). * CLAUDE.md — refresh "current focus" to v1.2 Hierarchies, and correct the now-broken "every v1.1+ table is app_id NOT NULL" invariant: the new group-inheritable config tables (vars, secrets) use a polymorphic owner (group_id XOR app_id), not app_id NOT NULL. Doc-only; no code change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
PiCloud
A lightweight, self-hosted, event-driven serverless compute platform. Upload a Rhai script, get an HTTP endpoint. Designed to run on a single modest server with no idle CPU cost, and to scale out to a small cluster when you need it.
Status: Phase 1 — MVP scaffolding in progress.
The authoritative design lives in
serverless_cloud_blueprint.md.
Why
Existing serverless platforms are either cloud-locked, heavyweight, or both. PiCloud aims for the opposite end of the spectrum: one binary, one database, one reverse proxy — running on hardware you already own.
Architecture (one paragraph)
PiCloud splits into three logical services — manager (control plane: scripts, schedules, dashboard), orchestrator (per-node event ingress and dispatch), and executor (per-node Rhai sandbox) — each backed by a *-core Rust library. In MVP they run in a single process; in cluster mode they run as three binaries with one manager and one orchestrator + executor per node. Caddy fronts everything; PostgreSQL is the single source of truth.
See CLAUDE.md for working notes and serverless_cloud_blueprint.md for the full design.
Quick Start
Coming as scaffolding lands. For now:
# Rust toolchain (pinned via rust-toolchain.toml)
cargo check --workspace
# Run the all-in-one MVP binary (once main.rs is wired up)
cargo run -p picloud
Repository Layout
crates/
shared/ cross-cutting types
executor-core/ Rhai engine + sandbox
orchestrator-core/ event ingress, dispatch
manager-core/ control plane
picloud/ MVP all-in-one binary
picloud-{manager,orchestrator,executor}/ cluster-mode binaries (skeleton)
dashboard/ SvelteKit
caddy/ Caddyfile
docker/ Dockerfiles
docs/
git-workflow.md Trunk-based workflow
Contributing
See docs/git-workflow.md for the branching and commit conventions. TL;DR: trunk-based, short-lived branches, Conventional Commits, no force-pushing main.
License
TBD.