86b51df50d
Four cleanups from the code review of the §7 ownership track, no behavior change to any passing test (416 manager-core units + 133 CLI journeys green): - #3 app-ownership read parity: `check_app_owner_single` now resolves the nearest-claimed ancestor WITHIN the apply tx (`nearest_claimed_in_tx`, the same mechanism the tree path uses) instead of on a separate pool connection, so the check and this apply's writes see one consistent snapshot. (Fully serializing against a concurrent claim on an out-of-tree ancestor stays part of the documented pool→tx follow-up.) - #4 blast-radius N+1 → one query: `group_blast_radius` replaced the per-descendant-group `ancestors()` round-trips with a single recursive `subtree → app_chain → nearest` CTE that groups + counts server-side. Cost is now one query regardless of subtree size. - #5 one ownership policy, two projections: `decide_group_claim` / `decide_app_owner` are generic over the identity key, and `preview_ownership` (plan side) now DERIVES its label from them (keyed on slugs, takeover-agnostic) rather than re-encoding the arms — plan and apply can no longer drift. - #6 shared slug validator: `validate_project_slug` delegates to a new `groups_api::validate_slug_format`, which `groups_api::validate_slug` also now uses — the format rule lives once. Projects intentionally skip the reserved-word check (a project slug is never routed). 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.