73c634ae0d
`resolve_owning_group`'s ancestor-chain CTE is the isolation boundary for EVERY group shared collection — kv, docs, files, topics, queues. Its own doc says so. Yet no test exercised the actual SQL: the tests that claimed to (`unrelated_app_gets_collection_not_shared` in the three older group services, `realtime_authority`'s SSE 404) inject a `FakeResolver` HashMap the test itself populates — the foreign app resolves to `None` only because the test never inserted it. They prove the service propagates a `None`; they cannot see the query that produces it. Dropping `JOIN chain c ON gc.group_id = c.group_owner` would let ANY app resolve ANY group's shared collection — a cross-tenant breach — and the whole unit suite would stay green. This drives the real query over a real tree: a descendant resolves, a sibling-subtree app gets nothing, the kind filter is part of the boundary (a kv and a docs collection of one name are distinct stores), nearest-declaration shadows (security-relevant — a deep app must reach the nearer group's store), an app-owned marker shares with nobody, and lookup is case-insensitive. Mutation-verified: with the chain join dropped, the boundary assertion fires — and under that breach `app_mid` resolves a FOREIGN group's `catalog` left in the DB by another suite, i.e. the leak reproduces live. 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.