Modules Catalog

This catalog follows the current TramAI repository inventory exposed by the TramAI MCP.

Today that inventory contains 41 framework modules plus 4 reference examples.

The important thing is not the raw count. It is the compatibility split:

• the 0.4.0 release-line foundations that most consumers start with
• the runtime and transport modules that extend orchestration into server, MCP, scheduling, and platform flows
• the sovereign and security modules that are implemented, but still evolving quickly
• the reference examples used to exercise end-to-end scenarios

Start Here

For a normal JVM application, begin with:

dependencies {
    implementation(platform("dev.tramai:tramai-bom:0.4.0"))
    implementation("dev.tramai:tramai-standalone") // or tramai-spring
    implementation("dev.tramai:tramai-openai")     // or another provider
}

Add tramai-testing for tests, tramai-observability for telemetry, and tramai-orchestration when the work is multi-step.

Release-Line Foundations

These are the modules that anchor the main 0.4.0 developer experience described across the site.

Detailed pages are available for those modules in this section of the site.

Provider And Context Modules

The current repository also includes dedicated provider and context modules beyond the basic getting-started path.

These modules are part of the current framework story and should not be described as hypothetical or future-only work.

Runtime, Transport, And Platform Modules

These modules extend TramAI beyond typed interface calls into workflow execution surfaces and operational tooling.

Treat these as real, implemented modules. They are not "planned", but they do evolve faster than the narrowest core surface.

Sovereign And Security Modules

The sovereign/runtime docs exposed by the TramAI MCP show these modules as implemented or implemented-and-evolving. They should no longer be documented as roadmap-only.

For 0.4.x, the security story should be framed as preview/evolving, not absent. The sovereign profile is a distinct part of the current framework, not a speculative future module.

Reference Examples

The current MCP inventory also exposes four example applications:

• examples:sovereign-document-intelligence
• examples:sovereign-offline-verification
• examples:spring-sovereign-starter
• examples:support-agent

Those examples are useful for validation and integration testing, but they are not framework modules.

Practical Reading Order

1. Start with tramai-standalone or tramai-spring.
2. Pick one provider module.
3. Add tramai-testing and tramai-observability.
4. Add tramai-orchestration only when the work is multi-step.
5. Add server, MCP, scheduler, platform, or sovereign modules only when your runtime needs them.