Captain.Food
Your dishes, your prices, your customers.
Local-first food ordering & delivery for independent restaurants and food trucks.
100 % of your orders. 0 % commission — for real.
The mission
Delivery platforms take 25–30 % of every order from the restaurants that cook it. Captain.Food
gives independent restaurateurs their orders back: their own ordering site, their own prices,
their own customer relationship — with zero commission, governed as a cooperative of the
social and solidarity economy (ESUS/SCIC) so it can never turn against its members.
V0 validates product–market fit in Tours (France), with a mobile-first web UX and a
backend that can evolve towards CQRS + an event log.
How this repo works
The specs/*.yaml DSL is the source of truth; everything else is generated and derived —
no LLM in the generation loop.
specs/ — the domain & architecture model: scalars, entities, events, commands, errors,
actors (aggregates + process managers), views (read models), the GraphQL API surface, story map,
behaviour tests, observability contracts, and C4 (specs/architecture/).tools/codegen-rs/ — a deterministic Rust generator/validator (ADR-0034). It
validates referential integrity + behaviour-test coverage + observability + C4 in one gate, then emits
artifacts. (It began as a TypeScript tool, ported to Rust at parity — byte-identical artifacts + the same
validation issue set — after which the TypeScript codegen was retired.)specs/generated/ — the committed generated artifacts: the GraphQL SDL, the
View_* SQL DDL, the Structurizr/Mermaid C4, and the navigable product documentation
(documentation.generated.md / .html). tools/codegen-rs/out/ is ephemeral build scratch.
make validate # the single blocking gate — must be 0 errors (needs a Rust toolchain: cargo)
make generate # regenerate every artifact from the specs
The ci workflow (first badge) is the whole gate, on every branch push and every PR: it builds
the full Cargo workspace, runs the complete behaviour-test suite, runs the spec validator (must be
0 errors), then regenerates every artifact and fails on any spec↔generation drift — so
specs/generated/ is always in sync. The db-migrate workflow (second badge) applies
migrations/*.sql only after ci succeeds on main (ADR-0043). The build-image workflow (third
badge) — also gated on a green ci/main (ADR-20260721-175411) — builds the server image in GitHub Actions (free on
this public repo, not on Render's metered build pipeline), pushes it to GHCR, and triggers Render to
deploy it by immutable digest via a deploy hook; Render only pulls the image, never compiles Rust.
The render deploy badge probes the live service's /health (which gates on the migrated schema
version and reports the running build's version), so green means deployed, migrated, and answering.
The render commit badge is the precise one: the render-status workflow asks the Render API for the
latest deploy and republishes it as <status> @ <sha> plus a render/deploy commit status on the exact
deployed commit (needs only the RENDER_API_KEY repo secret — the service id is discovered by name; skips gracefully until set).
Rollback (ADR-20260721-175411): production always runs a content-addressed image, so rolling back is
redeploying a previous one — no rebuild, no revert commit. Re-hit the Render deploy hook with a prior
build's reference:
# roll back to a known-good commit (find it in Render's deploy history or the `render commit` badge)
curl -fsS -X POST "$RENDER_DEPLOY_HOOK_URL&imgURL=ghcr.io/thecaptaincompany/captain-food:sha-<previous-commit>"
# strongest form: pin the exact digest instead of the sha tag
curl -fsS -X POST "$RENDER_DEPLOY_HOOK_URL&imgURL=ghcr.io/thecaptaincompany/captain-food@sha256:<digest>"
Confirm the rollback landed by reading version from https://live.captain.food/health.
Operating model
Planning is separate from execution, the DSL is never edited by execution loops, and the gates are
executable & blocking. See docs/PLAYBOOK.md, the topic rules in
docs/claude/, and the decisions in docs/adr/ (with the full
Nov 2025 – Jun 2026 history in docs/adr/HISTORY.md).
Repository convention: all content is written in English.
License
Captain.Food is released under the Captain.Food Coopyleft License — a copyleft license
inspired by CoopCycle's Coopyleft. It adopts the
GNU Affero General Public License v3 for study, execution, modification and redistribution,
but reserves commercial use to cooperatives, non-profit and limited-profit organizations
of the social and solidarity economy. See LICENSE.md for the full terms and
LICENSES/AGPL-3.0.txt for the AGPL v3 text.
