5cbb6ca427
Audit of feat/v1.1.7-secrets-email against the v1.1.7 dispatch prompt. All gates green; awk-summed 617 tests pass (matches HANDBACK §8 exactly — the v1.1.6 retro discipline lesson landed). Three flagged items reviewed and resolved: - Brief-internal contradiction on TriggerEvent::DeadLetter field names: agent built from the real variant, flagged not reinterpreted (the v1.1.6 retro discipline working again). - inbound_secret stored encrypted (user-approved deviation): correct call. Encryption-at-rest of credentials is the right default; the brief's plaintext recommendation was a premature optimization. The microsecond decrypt is negligible vs the HMAC + DB round-trip already on the path. - Latent finding: clippy --all-targets didn't pass at v1.1.6 HEAD. Four pre-existing warnings the v1.1.6 audit missed (likely due to cargo incremental cache interaction). Agent fixed in dedicated commit. Real audit oversight in my v1.1.6 review; discipline fix folded into v1.1.8 prompt recommendations. The v1.1.1 dead-letter handler bug (silently broken across six releases) is finally wired. Two-phase realtime key migration ships with phase-2 (plaintext column drop) deferred to v1.1.8.
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.