Rails Baseline Client Workspace Provisioning (Onboarding)

Rails Baseline Client Workspace Provisioning (Onboarding)

1. 01

   Purchase the founding release at $129 one-time and clone the Rails Baseline source into a fresh repository

   Confirm the license covers products the agency owns before wiring it into a client engagement. The one-time fee buys the 1.x source, architecture and agent guidance, extension recipes, and the production deployment baseline.

2. 02

   Run the documented setup against PostgreSQL and Docker, then verify the three core modules load

   Authentication, Stripe billing, and multi-account tenancy must all boot cleanly before any client-specific work begins. A broken tenancy layer discovered after kickoff costs more than the setup hour it takes to catch it now.

3. 03

   Read AGENTS.md and ARCHITECTURE.md before writing a single line of client code

   These files define the canonical patterns for entitlements, limits, and background jobs. Pointing coding agents at them first is what keeps agent-generated features inside the architectural contracts instead of forking them.

4. 04

   Map the client's plan tiers onto the existing entitlements and limits contracts

   Rails Baseline ships stable patterns for entitlements and limits, so most tier logic is configuration rather than new models. Only extend the contracts when a client requirement genuinely falls outside them.

5. 05

   Configure Pundit authorization policies per role the client actually has

   Start from the shipped authorization patterns and add policies only for roles in the signed scope. Every extra policy is surface area the delivery team maintains on retainer.

6. 06

   Wire the client's Stripe account into the billing module and run a live test transaction

   Verify webhook handling and subscription state changes end to end. Billing bugs found in production damage the retainer relationship faster than any other defect class.

7. 07

   Stand up staging and production environments with CI/CD and environment variables separated

   Keep Stripe keys, database credentials, and any API keys distinct per environment. The production deployment baseline in the kit assumes this split.

8. 08

   Hand off with a written extension guide naming the files agents should read first

   Document which contracts are stable, which are client-specific, and where new models belong. This is the artifact that lets the client's own developers or the agency's next agent session extend the app without rework.