450badaabf
APPROVE — final v1.1.x release lands clean. Full scope: queue::* + queue:receive trigger + dispatcher queue arm + visibility-timeout reclaim + invoke()/invoke_async + retry::* (with → run per Rhai reserved keyword). All five F1-F5 follow-ups from the v1.1.8 retro implemented; seven deviations transparently flagged in HANDBACK §7 with sound rationale. §8 attestation discipline visibly leveled up from v1.1.8: schema-snapshot re-blessed in-branch, literal fmt/clippy output, F4 grep verification, four new DB-gated integration binaries (queue_e2e 4, invoke_e2e 4, retry_e2e 3, migration_queue_messages 4) matching the brief's non-negotiable test-density minimums. Reviewer-independent verification reproduced all material claims: fmt green, clippy green (incremental), F4 grep returns exactly one hit, schema replay matches the committed golden, all 15 new DB-gated tests pass against a fresh dev Postgres. Aggregate lighter-slice attestation: 666 passed / 0 failed across the load-bearing crates — matches agent's claimed ~660.
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.