the-lab-doctrine

What problem does it solve?

Canonical playbook for implementing, extending, or auditing features across the V.O.I.D. / The Lab Industries monorepo. Use whenever the user asks to add a feature, endpoint, event, page, screen, or data field — before any code is authored. Captures the role→app matrix, backend package topology, the six-step mutating-handler shape, the dual event path (transactional outbox + EmitNotification), Spanner/cache/idempotency primitives, WebSocket hub discipline, auth scoping, H3 spatial rules, cross-role sync, and the local-simulator + physical-device dev loop so a new feature lands coherently across every surface that consumes it.

Core Features & Use Cases

• Canonical mapping of roles to apps and the end-to-end feature wiring across backend, events, caches, and clients.
• The six-step mutating-handler pattern, dual event paths, and idempotent, fault-tolerant workflows.
• Guidance for multi-tenant scope, WebSocket hubs, and spatial rules to ensure consistency across surfaces.

Quick Start

Follow this playbook at the outset of a feature to ensure end-to-end wiring across every surface before any code is authored.