joshuaandClaude Opus 5.5 ea1575f716 Contracts: event, event feed, church, identity, sign-in return, Hub protocol v2
- crosscode.event/1 and crosscode.event-feed/1 (feed, event.changed
  webhook), with session and registration rules; parseEventFeed skips
  and reports bad events instead of failing the whole feed.
- crosscode.church/1: branding, campuses, service times, contact, links.
- crosscode.identity/1: sign-in claims and the user.updated /
  user.deleted / user.export back-channel calls and replies.
- Sign-in return helpers (isSafeReturnPath, encodeState/decodeState,
  isRegisteredRedirectUri) so every product returns people to the page
  they came from in the same safe way.
- Hub protocol v2: product on register/heartbeat, stats per product,
  install public key, linked products, customerId/product in licences.
- @crosscode/contracts/signing (Node only): the Hub's HMAC scheme.
- Samples for every contract in samples/, checked by the tests (120).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-04 09:47:40 +02:00

Cross Code platform

The monorepo for the Cross Code products that come after Cross Events, and the formats they share. The plan is in hope-events/docs/ROADMAP-v3.md (decided 2026-11-03).

Folder What Status
packages/contracts @crosscode/contracts: the shared JSON formats (zod schemas, JSON Schema, TypeScript types, sample payloads) used by every product, including Cross Events and the Hub Phase 0, in progress
packages/ui @crosscode/ui: shared UI for the Website, App and Accounts Placeholder, filled in during the Website phase
apps/accounts Accounts: the per-church sign-in (OpenID Connect) Placeholder (phase 3)
apps/website Church Website Placeholder (phase 4)
apps/app Church App (PWA) Placeholder (phase 6)

Cross Events (joshua/hope-events) and Cross Code Hub (joshua/events-hub) stay in their own repos and install @crosscode/contracts from Gitea's package registry.

Rules (ROADMAP-v3 §1)

  1. No shared databases, ever. Products only talk over HTTPS using the contracts.
  2. The Hub is never on the runtime path.
  3. One maintained codebase per product. Nothing is built specially for one church.
  4. The origin of a record owns it. Copies elsewhere are read-only and link back to the origin.

Working on it

Node 20 or newer, npm workspaces.

npm install
npm run check      # lint + typecheck + tests + build, for every workspace
npm run build      # build every workspace
npm test           # test every workspace

Work in a workspace with npm run <script> -w packages/contracts.

Stack (ROADMAP-v3 §8): TypeScript, zod, Jest, ESLint here; the apps add Next.js, Express, Prisma, PostgreSQL and pg-boss, as in Cross Events. PM2 and nginx, no Docker.

Releasing

Each package and app is versioned and tagged on its own, as <name>@<version> (e.g. contracts@1.0.0). Branch → merge → tag → push, with a CHANGELOG entry. Run npm run check first.

S
Description
No description provided
Readme
5.9 MiB
Languages
TypeScript 66.6%
JavaScript 31.6%
Shell 1.7%
CSS 0.1%