Module Design

TramAI is no longer accurately described as a small set of published modules plus a few planned ones.

The current repository inventory exposed by the TramAI MCP contains 41 framework modules and 4 reference examples. The more useful distinction is:

release-line foundations used by most consumers
runtime and platform modules that build on orchestration
sovereign and security modules that are implemented but still evolving quickly

Compatibility Buckets

Bucket	Meaning
Release-line foundation	Safe starting point for most applications and the main surface emphasized by the site
Runtime/platform	Implemented operational modules for workflow transport, scheduling, and control planes
Sovereign/security preview	Implemented modules with active design and compatibility movement in `0.4.x`

Current Module Shape

Layer	Modules
Core	`tramai-core`, `tramai-engine`, `tramai-structured`, `tramai-bom`
App entry points	`tramai-standalone`, `tramai-spring`
Providers	`tramai-openai`, `tramai-anthropic`, `tramai-ollama`, `tramai-gemini`, `tramai-deepseek`, `tramai-bedrock`, `tramai-azure-openai`, `tramai-spring-boot-starter-local-provider-openai`
Observability and tests	`tramai-observability`, `tramai-testing`
Workflow/runtime	`tramai-orchestration`, `tramai-scheduler`, `tramai-server`, `tramai-mcp`, `tramai-platform`, `tramai-dashboard`
Memory and retrieval	`tramai-memory`, `tramai-memory-store`, `tramai-embedding`, `tramai-rag`, `tramai-vectorstore-spi`, `tramai-vectorstore-chroma`, `tramai-vectorstore-pgvector`
Sovereign/security	`tramai-security`, `tramai-sovereign`, `tramai-persistence-file`, `tramai-persistence-jdbc`, sovereign Spring Boot starter modules

Dependency Direction

tramai-core
  ├─ tramai-engine
  │   ├─ tramai-orchestration
  │   │   ├─ tramai-scheduler
  │   │   └─ tramai-server
  │   │       ├─ tramai-mcp
  │   │       ├─ tramai-platform
  │   │       └─ tramai-dashboard
  │   ├─ tramai-testing
  │   └─ tramai-observability
  ├─ tramai-structured
  ├─ tramai-standalone
  │   └─ tramai-spring
  ├─ provider modules
  ├─ memory / embedding / vectorstore modules
  └─ security / sovereign / persistence modules
      └─ sovereign Spring Boot starter modules

Two corrections matter here:

tramai-openai is not the umbrella for Azure OpenAI, DeepSeek, and Bedrock at the packaging level. Those exist as dedicated modules in the current inventory.
tramai-security, tramai-sovereign, and the sovereign persistence modules should no longer be modeled as "planned only".

Design Rules

tramai-core remains the shared contract layer.
Execution semantics belong in tramai-engine and tramai-orchestration, not in provider modules.
Providers stay thin and provider-specific.
Transport surfaces such as HTTP and MCP layer on top of workflow/runtime modules instead of redefining execution semantics.
Sovereign/security concerns remain explicit modules rather than hidden flags inside the core runtime.

Reading Guidance

If you are trying to understand the project quickly:

Read tramai-core, tramai-engine, and tramai-structured as the base.
Pick tramai-standalone or tramai-spring.
Pick a provider module.
Add orchestration and runtime modules only when you need workflow execution outside a single typed call.
Treat sovereign/security docs as current capabilities in preview, not as absent roadmap placeholders.