OUTCOME PLAYBOOK
Ship a SaaS platform
Carry one tenant request from identity and project administration through runtime health, usage, billing, and an SLO release decision.
- 1. Choose
- 2. Install
- 3. Run
- 4. Verify
- 5. Harden
- 6. Operate
#Choose the package boundaries
Required packages establish the local success path. Production and operate packages close durability and evidence boundaries.
Required
1. Identify
@absolutejs/authResolves the user, session, organization, and tenant context.
Required2. Administer
@absolutejs/adminMaps project roles to capabilities and fail-closed server decisions.
Required3. Run
@absolutejs/runtimeConnects request lifecycle, health, and operational state.
Production4. Account
@absolutejs/metering + billingRecords billable dimensions and turns them into account charges.
Operate5. Release
@absolutejs/health + slo + deployVerifies releases and blocks promotion on unhealthy objectives.
#Prerequisites
A durable user, tenant, project, and membership model.
A database transaction boundary shared by project mutations and usage evidence.
A release environment with observable health checks.
#Install the complete surface
BASH
bun add @absolutejs/auth @absolutejs/admin @absolutejs/runtime @absolutejs/metering @absolutejs/billing @absolutejs/health @absolutejs/slo @absolutejs/deploySmallest useful file tree
TXT
src/
auth.ts # identity and tenant context
admin.ts # project roles and server authorization
runtime.ts # request lifecycle and health
usage.ts # metering and billing dimensions
release.ts # deploy verification and SLO gate#Run and verify
Protect one action
Resolve a tenant-scoped user and authorize one Admin capability on the server.
Proof of success: Viewer is denied; administrator succeeds for the same project.
- 1. Choose
- 2. Install
- 3. Run
- 4. Verify
- 5. Harden
- 6. Operate
#Expected results
A tenant-scoped administrator can perform an allowed project action.
The same tenant and operation identifiers appear in usage, health, and audit records.
A release gate can distinguish healthy delivery from budget or SLO exhaustion.
#Development to production
DevelopmentSingle process and memory health historyProductionDurable shared stores and external probes
All instances and release operators need the same tenant and health truth.DevelopmentManual invoice inspectionProductionIdempotent billing export and reconciliation
Usage acceptance and money movement fail independently.#Failure decisions
A project action crosses tenant scope.
Check firstCompare the authenticated tenant with the project resource tenant before querying data.
ThenReject before Admin navigation or data is produced.
The SLO gate has incomplete telemetry.
Check firstSeparate a missing metric from a failing objective.
ThenBlock release on unknown evidence instead of treating it as healthy.