Agent Workflow

Thinai is designed to be read by coding agents as well as people. The model describes the domain; the agent implements code using the repository’s conventions. There is no code generator.

Interfaces

Use whichever interface is available:

• LSP — diagnostics, completion, definitions, references, document symbols, hover, formatting, and code actions.
• CLI — model export, context slices, impact, validation, and an MCP server.
• MCP — structured model queries for agents that support tool calling.

All three read the same model. The model remains the source of truth.

Install the CLI with npm install -g thinai-cli@alpha or run it with npx thinai-cli@alpha. The commands below assume thinai-cli is on PATH.

Inspect the model

thinai-cli inspect path/to/model.tni --out model.json

The output uses the thinai-model-v1 schema. Element IDs are canonical and kind-prefixed:

Aggregate:Ordering.Order
Field:Ordering.Order.Order.id
IntegrationEvent:Ordering.OrderPlacedV1

Request a context slice

Prefer one aggregate, bounded context, module, or contract over loading the whole model.

thinai-cli context path/to/model.tni Aggregate:Ordering.Order --format md

The slice includes the root, its members, relevant dependencies, contracts, and the relationships between included elements. Module and cross-context visibility metadata is preserved.

Report impact

thinai-cli impact path/to/model.tni ValueObject:Ordering.Order.OrderId --json

The report lists the changed element, its descendants, incoming references, and the elements that reference it.

Validate

thinai-cli validate path/to/model.tni

The CLI validates the source file and its transitive imports. It does not discover separate files that import the source file. Use a workspace-aware client for the complete import-connected model.

MCP server

thinai-cli mcp path/to/model.tni

The server is read-only. Available tools:

• list_elements
• search_elements
• get_element
• get_context
• get_dependencies
• get_visibility
• validate_model
• impact_of_change

Use MCP when the agent supports structured tool calls but not LSP or shell commands. Use the CLI when shell access is available. Use LSP for editor and agent navigation.

Workflow

1. Locate the model and the relevant bounded context.
2. Request a context slice.
3. Respect module exposure and cross-context boundaries.
4. Implement code using the repository’s language and framework conventions.
5. Validate the model and run the repository’s tests.
6. Check that every touched aggregate, event, contract, and exposed operation has a code counterpart.

Model rules to preserve

• identifier fields reference a value object declared in the same aggregate.
• Module visibility requires exposure and, for sibling modules, depends on.
• Cross-context use requires a mirror, shared kernel, integration event, or published query contract.
• Domain events are context-private; integration events are cross-context contracts.
• Data objects are boundary shapes, not domain state.
• Primitives are string, boolean, integer, decimal, date, time, and instant.

A deterministic conformance manifest and thinai verify workflow are planned after the first alpha.