Resources Hub

New to the platform: what it is, how a rollout is shaped from first pilot to portfolio, and where daily work happens. Read these first — every other section assumes this orientation.

• Getting startedWelcome to the MCV platform — shared infrastructure built for scale across every brand and business line.
• Venture & brand onboardingHow a new venture plugs into the platform: the consumption contract, the SDK wrapper pattern, identity handoff, isolation rules, and telemetry duty.
• Pilot rollout checklistThe bounded-pilot shape we recommend: one workflow, named owners, explicit proof criteria, and an expansion decision made on evidence.
• Operator consoleInstitutional-grade control room patterns for daily operations — departments, approval gates, live monitoring, and the console boundary.

The structural model underneath every venture: tenant hierarchy, database-level isolation, the layer model, decision logic, and the audit trail. These docs explain why the boundaries exist and how they hold under load.

Triangle secure sign-on, end to end: the public-to-console handoff, session and token mechanics, and how grants resolve per brand. Read these before touching any credentialed surface.

• Triangle: secure sign-onSecure sign-on at the front door — the handoff from public site into the operator console, and how permissions resolve per brand.
• Triangle sessions & tokensThe two-layer session model, the token exchange step by step, lifetimes and rotation, storage discipline, and why invite tokens get their own keys.

The shared record and the shared book: data fabric orientation, isolation mechanics, billing splits, and royalty metering. How operational data and money movement stay separated per brand.

• Data fabric orientationMap authority, identity, lineage, freshness, and failure behavior before connecting an operational source.
• Billing & treasury splitsHow revenue and fees are recorded once on a shared ledger and split across brand, region, and location nodes — with every split reconstructable.
• Royalty metering & the ledgerHow platform usage fees are metered: an append-only, platform-signed, hash-chained ledger with a nightly parity check and a monthly invoicing loop.
• Database isolation mechanicsThe row-level machinery under per-brand isolation: the tenant column, the three standard policies, transaction-scoped context, and the guarded bypass.

Governed automation: the boundaries every agent contract declares and the approval gates in front of irreversible actions. What agents may do unattended — and what always waits for a human.

Running the platform day to day: rosters and constraints, incident readiness, and the support surfaces operators actually use. The operational playbook once the pilot is live.

• Scheduling constraints & the roster engineHow rosters are built from declared constraints — availability, qualifications, hour limits, demand — with conflicts surfaced before publication, not discovered on the floor.
• Support and incident readinessSeparate public orientation from credentialed incident operations while preserving ownership and recovery evidence.

Building on the platform: the API map, the endpoint reference for the console’s published surfaces, versioning policy, webhooks and events, and the checklist that decides whether an integration is done.

Per-vertical operating loops — fitness, capital, dining, property, construction, and counsel. Same substrate, tuned workflows, one doc per lane.

• Membership health & retention loopHow engagement telemetry, visit records, and policy-gated outreach form the retention loop on the fitness lane.
• Capital ledger governanceHow splits, gated transfers, and consolidated statements keep the capital record disciplined from location to fund.
• Floor & service operationsFloor balance, phone coverage, kitchen sequencing, and payout math — the operating shape of a service night on the dining lane.
• Tenant record & rollout postureThe tenant lifecycle record, rent ledger, and vendor dispatch model — and the staged-rollout posture the property lane ships under.
• Field record disciplineEnter once in the field, verify before dispatch, sign changes on site — the record discipline and staged-rollout posture of the construction lane.
• Counsel lane design principlesThe design commitments under review for the legal practice lane — stated as direction, with nothing presented as available.