TramAI

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

BucketMeaning
Release-line foundationSafe starting point for most applications and the main surface emphasized by the site
Runtime/platformImplemented operational modules for workflow transport, scheduling, and control planes
Sovereign/security previewImplemented modules with active design and compatibility movement in 0.4.x

Current Module Shape

LayerModules
Coretramai-core, tramai-engine, tramai-structured, tramai-bom
App entry pointstramai-standalone, tramai-spring
Providerstramai-openai, tramai-anthropic, tramai-ollama, tramai-gemini, tramai-deepseek, tramai-bedrock, tramai-azure-openai, tramai-spring-boot-starter-local-provider-openai
Observability and teststramai-observability, tramai-testing
Workflow/runtimetramai-orchestration, tramai-scheduler, tramai-server, tramai-mcp, tramai-platform, tramai-dashboard
Memory and retrievaltramai-memory, tramai-memory-store, tramai-embedding, tramai-rag, tramai-vectorstore-spi, tramai-vectorstore-chroma, tramai-vectorstore-pgvector
Sovereign/securitytramai-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:

  1. 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.
  2. tramai-security, tramai-sovereign, and the sovereign persistence modules should no longer be modeled as "planned only".

Design Rules

  1. tramai-core remains the shared contract layer.
  2. Execution semantics belong in tramai-engine and tramai-orchestration, not in provider modules.
  3. Providers stay thin and provider-specific.
  4. Transport surfaces such as HTTP and MCP layer on top of workflow/runtime modules instead of redefining execution semantics.
  5. 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:

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