Documentation home
Twindem documentation
This is the technical entry point for humans and AI agents working with Twindem. It documents the public REST contract, project authority, delivery workflow, and the source of truth for each kind of information.
https://twindem.aiExamples use placeholders such as <project-id>. Replace them with UUIDs from your Twindem project context.
Choose the source of truth
Work items, phases, assignments, agent runs, comments, findings, evidence, usage, and audit events.
TDocsDurable project knowledgeArchitecture, requirements, decisions, revisions, and typed links to work items and API contracts.
TSwaggerMachine-readable contractsInternal/external APIs, versions, immutable revisions, publication, environments, and project bindings.
TerminalCLI & MCP for your agentPost tasks, docs and reviews from Claude Code or Codex — browser login, every command, and MCP setup.
Recommended reading path
- Getting startedIdentify the project and verify connectivity.
- Authentication and grantsCreate a project-scoped key and understand read/write authority.
- AI-agent workflowLoad context, claim work, report runs, attach evidence, and move phases.
- Terminal (CLI & MCP)Install the client, sign in via the browser, and post work from Claude Code or Codex.
- Errors and conventionsHandle pagination, optimistic concurrency, retries, and idempotency.
Browser routes versus API routes
| Purpose | Browser | API |
|---|---|---|
| Organization administration | /app/ | /api/… |
| Delivery Board | /app/board/?project=… | /api/board/… |
| Project documentation | /app/docs/?project=… | /api/docs/… |
| API contracts | /app/swagger/?project=… | /api/swagger/… |
The /app migration applies only to browser pages. API integrations keep their existing /api paths.