Business problem
Why this system exists
Move and rental-turn cleaning requires reliable handoffs across customers, operators, and crews without letting automation bypass human judgment or production safety gates.
Local-service operations
KeyTurn Cleaning Company OS
Production Prelaunch — Controlled LaunchA multi-surface operating system connecting a public cleaning website, internal CRM, crew portal, Supabase data boundaries, and guarded automation controls.
Verified media
Rendered application evidence, labeled at its actual stage.
Role evidence
What the repositories support
Repository evidence supports the system architecture, application implementation, control design, test coverage, documentation, and prelaunch deployment work.
Repository group
- Pwarner96/Keyturn — canonical monorepo; intended private
System architecture
Verified boundaries from interface to accountable data.
This diagram summarizes repository-supported components and controls. It does not imply that disabled providers or undeployed services are active.
- Role-specific surfacesPublic website · internal CRM · crew portal
- Application boundaryNext.js routes · typed workflows · server-side validation
- Control boundaryAuthentication · authorization · approval gates · audit evidence
- Data and adaptersSupabase/PostgreSQL · guarded external-provider adapters
Core workflow
A controlled path from source to accountable action.
- 01Capture a scoped service request
- 02Review estimate and operating context
- 03Coordinate CRM and crew work
- 04Require approval before guarded actions
AI boundary
Assistance without invented authority
Governed agent infrastructure is implemented with typed tools, budgets, containment, audit evidence, and deterministic fallback. Live providers and autonomous external actions remain disabled.
Human approval points
- Human estimate review
- Explicit approval before write-capable actions
- Owner-controlled provider and launch gates
Security controls
- Surface-specific authentication and authorization
- Supabase row-level security and server-only secrets
- Fail-closed staging and local-origin write guards
Reliability controls
- All-surface CI and production builds
- Idempotency, validation, and audit trails
- Deterministic behavior when providers are disabled
Current limitations
- Production prelaunch is not the same as live operations.
- Messaging, payments, and autonomous or external agent actions remain disabled pending owner approval.
- Repository source is not linked from this portfolio; this page exposes only sanitized evidence and real public/local captures.
Evidence before adjectives