Operational Dotabase Kits

Description

Operational Dotabase Kits provision the Dots internal operating system for customers, people, incidents, support, feedback, and vendors/costs.

Typed internal definitions describe the six databases and their supported schemas, views, behaviors, and widgets. A Dots-tenant-only provisioner creates or additively reconciles them, while the customers projection summarizes fleet identity and metrics into owned fields. Tenant content is not copied into this internal operating set.

User Story

As a platform operator, I manage support and customer health from structured, linked Dotabases instead of disconnected spreadsheets. I provision the internal kit in the authorized Dots tenant and use its saved views for people, incidents, feedback, vendors, and costs. The customer projection refreshes only its declared identity and metric fields. I walk away with a consistent operating workspace while retaining human-owned notes and decisions in the same records.

Extension Surface

Fixed core: this is a Dots-tenant dogfood kit, not a general marketplace installer.

packages/dotabases/src/seed/provision-operational.ts enforces the intended provisioning boundary. The definitions are platform-owned and invocation is restricted; customers cannot install the kit as an arbitrary template through this capability.

Capabilities & Limits

• Capability: Executes the scoped workflow described above through the cited live implementation paths.
• Capability: Preserves typed validation and applicable tenant, schema, lifecycle, or service boundaries.
• Limit: Provisioning is deliberately restricted to the Dots tenant. The customer projection owns only identity and metric fields. The kit can establish six operational Dotabases, reconcile supported additive changes, and maintain bounded customer fleet summaries. It cannot expose tenant content, overwrite independently curated operator fields, or serve as a generic CRM installer. Wider reusable templates require a separately designed and governed surface.

Implementation Map

• packages/dotabases/src/seed/provision-operational.ts
• packages/dotabases/src/seed/operational/index.ts
• packages/dotabases/src/services/customers-projection.ts

Related Features

Creates Dotabase Workspaces and uses Version and Activity Trails.

Operationally, these relationships preserve a clear ownership boundary around Operational Dotabase Kits. Neighboring features can invoke, supply, or consume its results, but `packages/dotabases/src/seed/provision-operational.ts` remains the grounded implementation authority for this capability. That distinction prevents the catalog claim from widening into adjacent rendering, transport, or governance work. Teams can therefore combine the feature with the named dependencies while still diagnosing configuration, validation, and lifecycle behavior at the package boundary that owns it.