Description
Knowledge Graph Edge Management lets users and agents turn isolated Dots into an explicit, inspectable network of typed relationships. dots edges creates individual or bulk edges, lists incident relationships by type and direction, reads one edge with reasoning and confidence, counts active edges for a Dotabase, graduates trusted lessons, and deletes a named edge under confirmation.
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
- Makes relationship provenance visible instead of reducing the graph to unlabeled links.
- Supports bulk enrichment campaigns while retaining per-edge reasoning and confidence.
- Provides a census that measures the actual edge table rather than stale row projections.
- Lets operators inspect both incoming and outgoing context before changing a relationship.
- Keeps destructive removal explicit and addressable by a concrete edge identifier.
User Story
An agent enriches a catalog by bulk-creating typed implementation edges, checks the resulting census, opens one relationship to review its reasoning, and removes a mistaken edge by id. The final graph is both denser and auditable. The result is a concrete, inspectable outcome that another person or automation can continue from without reconstructing hidden state.
Extension Surface
The CLI family is automatable: packages/cli/src/commands/edges.ts exposes the route-backed graph vocabulary. Custom edge types may be configured separately, but new edge-management verbs require core changes. 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: Single and bulk typed-edge creation with provenance fields.
- Capability: Incident listing, direct read-back, direction/type filtering, and Dotabase-wide census.
- Capability: Confirmed deletion plus the system-trust lesson-to-guard graduation seam.
- Limit: The CLI does not infer semantic relationships by itself; callers must supply valid endpoints, an allowed verb, and defensible reasoning.
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/edges.tspackages/cli/src/services-factory.tsdocs/cli/rows-and-edges-commands.md