f2b16da2b5
invoke_service::resolve and enqueue_async performed no authz check — no AppInvoke capability existed. Same-app isolation was preserved (cross-app guards work), but within one app an anonymous public-HTTP script could trigger any other script (e.g. an admin-only worker that hits secrets/files/external HTTP). Worse: invoke_async runs the callee with principal: None, so the callee could hold capabilities the original public caller shouldn't. - Add Capability::AppInvoke(AppId). app_id() / scope_for_capability (script:write) / role_satisfies (editor+) are all updated. - InvokeServiceImpl gains an optional `authz: Option<Arc<dyn AuthzRepo>>` + a `with_authz` builder. When set, resolve() runs script_gate on AppInvoke before doing the cross-app id check. - picloud/src/lib.rs wires it: `InvokeServiceImpl::new(...).with_authz(...)`. - Anonymous callers (cx.principal == None) continue to skip the check via script_gate, preserving the public-HTTP convention. Existing 5 invoke_service unit tests still pass (the tests use the authz-less constructor, so the gate is a no-op there). AUDIT.md anchor: F-S-012. Co-Authored-By: Claude Opus 4.7 (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.