ca360d84cb
Phase 3 (group-inherited config) is implemented, so fold the outcome back into the design doc (per its own "before it drifts" note) — and flag the one deliberate divergence from the plan. §5.1 / §11.3 / §12 prescribed a *materialized* per-app effective view with a generation counter and fan-out invalidation. We shipped **live, resolve-on-read inheritance** instead: one recursive CTE per `vars::get`/`secrets::get`/`config/effective`, no cache. The org tree is small and there was no pre-existing config cache to fight, so this is cheap and sidesteps §10's unsolved invalidation SLA. Records, mirroring the Phase 1/2 status blocks: * a "Status (Phase 3): ✅ shipped" block in §11.3 with the full surface (0048/0049 schema incl. `apps.environment`, the §3 resolver, vars SDK + CRUD, group-secret AAD + inherited read, the two secret gates, masked `config/effective`, `--explain`) and the live-vs-materialized rationale; * §5.1 runtime-model bullet annotated as the deferred (Phase-4 script inheritance) design, not Phase-3 runtime; * §10 "invalidation SLA" and "inherited-membership revocation lag" marked moot/resolved — no cache means immediate propagation; * §12 resolver contract + the header framing updated to live resolution. 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.