Description
This command family makes the Dotabase data primitive fully operable without opening the web application, from initial creation through schema and behavior evolution. dots dotabases resolves human-friendly references, binds create and update schemas, exposes additive schema operations, protects destructive replacement with explicit force gates, and manages behavior and derivation bindings. Server-authored scaffolds prevent agents from inventing system properties.
The workflow is designed for operators and coding agents. It uses the same authenticated, company-scoped service contracts as the rest of Dots, so terminal or protocol convenience never creates a second source of truth. Inputs are validated before or at the route boundary, and outputs preserve identifiers and structured details needed for a reliable next step.
Selling Points
- Lets agents build a complete knowledge store through reproducible commands and checked JSON inputs.
- Protects existing properties and behavior bindings from accidental drops during whole-array replacement.
- Adds selection options through a race-safe delta operation instead of lossy read-modify-write loops.
- Carries creation provenance and operating-manual seeds into the first durable Dotabase record.
- Supports cross-Dotabase derivation while keeping bindings inspectable and independently toggleable.
User Story
A knowledge architect scaffolds the canonical system properties, appends domain-specific fields, creates a Dotabase with behavior bindings, and later adds a status option without replacing the existing roster. They finish with a schema that parses against the live service contract and retains every prior configuration. The result is a concrete, inspectable outcome that another person or automation can continue from without reconstructing hidden state.
Extension Surface
The command surface is automatable: packages/cli/src/commands/dotabases.ts exposes the supported lifecycle and schema verbs over fixed API contracts. Behavior definitions may be pluggable elsewhere, but this CLI family itself does not accept command registrations. The rating reflects the most-open supported seam that is true for this capability, not a transitive implementation detail. The cited path is the operational proof: consumers can use the documented seam, while unsupported changes still require a core release.
Capabilities & Limits
- Capability: Create, describe, update, derive, delete, seed, and inspect Dotabase activity.
- Capability: Scaffold, set, append, rename, retype, and extend schemas and option rosters.
- Capability: List and replace behavior bindings plus create, toggle, list, and delete derivation bindings.
- Limit: Whole-schema replacement and retyping remain migration-sensitive and require explicit force; the CLI does not invent data migration policy.
The limit is intentional product truth rather than missing documentation. Calls also remain subject to authentication, tenant selection, schema validation, and the permissions enforced by the authoritative service.
Implementation Map
packages/cli/src/commands/dotabases.tspackages/cli/src/services-factory.tsdocs/cli/dotabases-commands.md