The Road to Launch

Seven backend applications on Frappe version sixteen: five MyRide applications and two ARK tenancy applications. A hundred and five record types. Roughly eight hundred and seventy framework-free tests, green, plus a claims guard that fails the build if a retired proof number appears and a tenancy guard that fails it if anyone writes a client-ID column.

Four Next.js sites — the company site with about sixty routes, the publication with about forty, the seasonal site with about twenty-five, and the office portal — typecheck, test and build. A local development bench with every application installed, migrated, and seeded with a full Winnipeg day. Seventy-six commits in four days, every step reported and gated.

Be precise about the gap between exists and wired. The command centre reads live from the site; the crew portal's five role views still render fixtures, visibly labelled. Staff sign-in is a role switcher because the auth host does not exist yet. The communications control plane composes, scans and records every post and delivers none — no workspace has been chosen. The agents are governed and registered but no language model is connected; the provider is a fixture that stamps every response as such. The lab runs on the framework's own desk for version one.

None of these is a hole. Each is a door waiting on a key.

Before a single real person books a drive, the five Express questions need their consent line: the legal basis, the wording of contact permission, and how channel and hours are captured. The platform records consent per channel and refuses to message without it. The mechanism is built. The words are not signed.

This is owner plus legal, and it blocks all real traffic. It is first on every list because nothing else matters until it is done. One signature, then a person can be put on the site.

Every conditional flag in the platform names who decides it and what it waits on. None of these is a build task. Each is a conversation, then a ledger entry, then a flag flipped.

Nothing can deploy from a laptop, so the first move is an organisation with private repositories: the monorepo and the seven application repos, which are already clean local histories with no remote. Then the host of record, by the owner's own document: prove the software before running a cloud company. A private bench, version sixteen, the runtime pinned at creation because neither is cheaply corrected afterwards. The applications at the exact commits in the lockfile — never branch heads. Three sites: dev, staging, production. The business locale on each regardless of where it is hosted.

The discipline, said aloud: dev and staging carry synthetic data only. That is what keeps the residency question from blocking engineering.

Two things the runbook treats as launch requirements rather than someday tasks. The host takes backups; ARK verifies a restore. A backup that has never been restored is a hypothesis. And production access is restricted to named humans, with every sensitive read logged — the lab already demands a reason before it opens a record.

Four integrations, each behind a boundary the platform already draws. Communications: choose the workspace and its retention, store the credential in the vault, flip the transport flag — the channels, the noise rules and the privacy scanner are already running against a recording transport. A model provider: implement one protocol against the model you choose; connecting it changes no agent's autonomy. An automation layer for SMS, ad-platform conversions and lenders — the platform never speaks to a carrier directly, so every external send has one place to be observed and revoked. And commercial data providers, each earning enabled through a twelve-step activation contract, never by someone pasting a key.

Launch posture is a private service, not a network. No empty forums, no member counters, no “thousands of members”. The first hundred Winnipeg garages, with the active high-touch caseload hard-capped between fifty and a hundred until the unit economics are real.

The cap is a feature. “We are accepting a hundred Winnipeg vehicle owners into the first MyRide market” is true scarcity, and true scarcity is the only kind the brand allows.

MyRide is tenant number one of a platform. The tenancy layer is extracted and tested: a configuration file per organisation, blueprints for what an automotive marketplace or a local service business installs, a twelve-step onboarding runbook that reports done, planned or blocked honestly. Isolation is structural — one site and one database per client, never a client-ID column, and a guard that fails the build if one appears.