47072c481d
The heart of multi-repo ownership: an apply now claims/verifies node ownership before it reconciles, so two repos can't clobber each other's subtree. - Pure policy (DB-free, unit-tested): `decide_group_claim` (unclaimed→claim, owner→noop, foreign→conflict unless --takeover, no-project-into-claimed→ conflict) and `decide_app_owner` (an app must match its nearest claimed ancestor; an unclaimed subtree stays open — backward-compatible). - Execution under the per-node advisory lock: `upsert_project_tx` (first apply registers the project), `read/write_group_owner_tx`, `claim_group_owner` (takeover additionally requires `GroupAdmin` — ownership ⟂ RBAC), `check_app_owner_single` + tree `nearest_claimed_in_tx` (in-tree Phase-A claim overlays committed ancestors). No structure_version bump — a claim isn't a diff change, so it must not churn a pending bound plan. - `apply`/`apply_owner`/`apply_tree` take an `OwnershipClaim` (project + takeover + principal); the claim slots after the lock, before load_current, so a conflict short-circuits before any diff work. - New `ApplyError::OwnershipConflict` → HTTP 409 (actionable); wired through `ApplyRequest`/`TreeApplyRequest` (both `#[serde(default)]`, so the existing CLI stays compatible until it learns [project]). 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.