Start from the current platform reality, not the historical scaffolding.
The repo already has authoritative onboarding, deployment ADRs, target taxonomy, and trust-graph docs. This page surfaces the shortest path into those materials and the commands developers actually need to get moving.
Partner deployment does not depend on GitHub team seats. Licensed recipe bundles are unlocked by a Social Fabric-issued badge or credential entitlement. When policy allows it, an authorized lodge node can use that badge-gated bundle to seed another organization node or grant cloud-served access to the same organization surface.
Authoritative Reading List
These are the documents that should shape development decisions before anyone invents a new deployment lane.
Peter B Stories Custom Onboarding
Tenant-specific onboarding flow, offsite alias model, plugin publication path, and internal Gitea mirror plan.
GitHub Ownership And Distribution
Canonical repo ownership plan plus the badge-gated bundle distribution model for partners and lodge operators.
Contributor Onboarding
Shortest current orientation path into the active platform.
Deployment Taxonomy ADR
Authoritative deployment target model and controller boundaries.
Shared Platform Boundary ADR
Which services belong to the shared platform and which belong to tenant nodes.
Trust Graph Query Layer
Current read-side projection and query surface for explainability.
Working Commands
These commands cover the main public site and the core verification lane that now includes the player service contracts.
Fresh Portal
cd services/sf-portal && deno task startPublic web entrypoint for developers, supporters, and community narrative.
Platform Contracts
deno task test:platform-contractsFast cross-surface contract lane, including gateway and player service coverage.
Shared Backend
cd shared-backend/service && ./scripts/start-local-backend.shCanonical local launcher for the Rust GraphQL backend.