64ad978a89
Audit of feat/v1.1.6-realtime-client against the v1.1.6 dispatch prompt. All gates green; clippy clean; ~550 tests pass (HANDBACK §8 claimed 482 — minor count-discrepancy flagged for retro, not a blocker). Both flagged items verified and resolved: - §4-vs-§8 publish-ordering contradiction in the brief: the agent picked §8 (broadcast AFTER outbox commit) and explicitly flagged the contradiction. Confirmed correct — §8's ordering protects against subscribers being told an event happened that subsequently failed to durably commit. §4's broadcast-first phrasing was a latency-optimization aside; §8 is the dedicated numbered spec. The v1.1.4 retro discipline lesson (flag-don't-reinterpret) worked. - Latent finding: dead_letter trigger handlers never fire — verified via grep. list_matching_dead_letter has no production caller; the bug predates v1.1.6 (shipped silent since v1.1.1). Correctly out-of-scope for v1.1.6. The dispatcher e2e test for dead_letter asserts the wired behavior (row created) with inline docs explaining why it's not asserting handler-fire. Fix folded into v1.1.7 prompt recommendations along with a retroactive CHANGELOG note. Three v1.1.5 follow-ups landed: six dispatcher e2e tests gated on DATABASE_URL, empty-blob relaxed, orphan tmp-sweeper. HMAC signing key persisted to app_secrets table (recommended path); streaming- fetch SSE in the client lib unlocks bearer-header auth + 401 detection + Last-Event-ID resume.
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.