Description
Row and Page Content Management is the CLI's complete authoring and maintenance surface for the records users keep in Dots. dots rows covers reads, counts, search modes, identity resolution, outlines, versions, individual and bulk creation, body edits, lifecycle actions, reinforcement, consolidation, and verification. dots pages exposes page lists plus outline and section reads for targeted retrieval.
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
- Gives agents stable human-id workflows instead of requiring opaque database UUIDs.
- Supports precise section and outline reads that avoid moving an entire long document.
- Combines bulk creation and import with individual correction and lifecycle controls.
- Preserves recoverability through archive and restore before hard deletion is considered.
- Exposes verification and consolidation as first-class content quality operations.
User Story
A research agent resolves a report title to its canonical row, reads only the relevant outline section, appends new evidence, verifies the result, and archives a duplicate after consolidation. The agent walks away with canonical identifiers and formatted records suitable for the next automation step. The result is a concrete, inspectable outcome that another person or automation can continue from without reconstructing hidden state.
Extension Surface
The family is automatable: packages/cli/src/commands/rows.ts and packages/cli/src/commands/pages.ts bind a fixed set of record operations to public routes. Schema configuration changes accepted values, but it does not add new row commands. 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: Flexible list, count, search, resolve, detail, outline, section, and version reads.
- Capability: Individual, bulk, import, update, append, reinforce, consolidate, and verification writes.
- Capability: Archive, restore, and explicit delete lifecycle controls.
- Limit: Commands remain constrained by each Dotabase's schema, operating manual, permissions, and loss-protection rules for rich bodies.
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/rows.tspackages/cli/src/commands/pages.tsdocs/cli/rows-and-edges-commands.md