bbfdb1bf47
`group_blast_radius`'s `app_chain` up-walk is depth-capped (`ac.depth < 64`, added by76926deto stop a should-be-impossible `groups.parent_id` cycle from spinning the recursive CTE forever), but the sibling `subtree` down-walk in the same query was left unbounded. A `parent_id` cycle would loop `subtree` indefinitely and hang the plan — the exact exposure76926deset out to close, left half-done on the descendant side. Add a `depth` column + `WHERE s.depth < 64` to `subtree`, mirroring `app_chain`. Defense-in-depth: the reparent cycle-guard already prevents `parent_id` cycles, so this hardens against an unreachable state — but that is precisely the bar76926deapplied. Surfaced by a post-adoption audit of the §7/§6 ownership code. Verified: 416 manager-core lib tests; 12 ownership/create/divergence/approval journeys (incl. plan_previews_ownership_and_blast_radius, which drives this query); clippy -D warnings + fmt clean. Co-Authored-By: Claude Opus 4.8 <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.