SystemPrompt

Extensible AI agent orchestration framework

What is SystemPrompt?

SystemPrompt provides a foundational platform for building AI agent orchestration systems:

• Agent Orchestration: Multi-agent lifecycle management via A2A protocol
• MCP Protocol: Model Context Protocol server and client implementations
• Database Abstraction: Unified interface supporting PostgreSQL
• HTTP API Framework: REST API with OAuth2 authentication
• Extension System: Extensible architecture with compile-time registration
• Configuration: Profile-based configuration with startup validation
• Structured Logging: Context-aware logging with request tracing

Installation

Add to your Cargo.toml:

[dependencies]
systemprompt = "0.0.1"

Feature Flags

[dependencies]
# Core only (traits, models, extension framework)
systemprompt = "0.0.1"

# With database support
systemprompt = { version = "0.0.1", features = ["database"] }

# With API server
systemprompt = { version = "0.0.1", features = ["api"] }

# Full functionality (all modules)
systemprompt = { version = "0.0.1", features = ["full"] }

Using Individual Crates

For finer-grained control, depend on specific crates:

[dependencies]
systemprompt-models = "0.0.1"
systemprompt-api = "0.0.1"
systemprompt-database = "0.0.1"
systemprompt-mcp = "0.0.1"
systemprompt-agent = "0.0.1"

Architecture

SystemPrompt uses a layered crate architecture with strict dependency rules:

crates/
├── shared/           # Pure types, zero internal dependencies
│   ├── traits/       # Core trait definitions (LlmProvider, ToolProvider, Job)
│   ├── models/       # Data models, API types, config structs
│   ├── identifiers/  # Typed IDs (UserId, TaskId, etc.)
│   ├── client/       # HTTP client for external APIs
│   └── extension/    # Extension framework for customization
│
├── infra/            # Stateless infrastructure utilities
│   ├── database/     # SQLx abstraction, connection pooling
│   ├── events/       # Event bus, broadcasters, SSE
│   ├── security/     # JWT validation, token handling
│   ├── config/       # Configuration loading
│   ├── logging/      # Tracing setup, log sinks
│   ├── cloud/        # Cloud API, tenant management
│   └── loader/       # Module loader
│
├── domain/           # Bounded contexts with SQL + repos + services
│   ├── users/        # User identity (User, Role)
│   ├── oauth/        # Authentication (Token, Client, Grant, Session)
│   ├── files/        # File storage (File, FileMetadata)
│   ├── analytics/    # Metrics & tracking (Session, Event, Metric)
│   ├── content/      # Content management (Content, Category, Tag)
│   ├── ai/           # LLM integration (Request, Response, Provider)
│   ├── mcp/          # MCP protocol (Server, Tool, Deployment)
│   └── agent/        # A2A protocol (Agent, Task, Context, Skill)
│
├── app/              # Orchestration, no business logic
│   ├── runtime/      # AppContext, StartupValidator, lifecycle
│   ├── scheduler/    # Job scheduling, cron execution
│   ├── generator/    # Static site generation
│   └── sync/         # Sync services
│
└── entry/            # Entry points (binaries, public APIs)
    ├── api/          # HTTP gateway, route handlers, middleware
    └── cli/          # Command-line interface

systemprompt/         # Umbrella crate: Public API for external consumers

Dependency Flow

UMBRELLA (systemprompt) ← External consumers
        │
    ENTRY (api, cli)
        │
    APP (runtime, scheduler, generator, sync)
        │
    DOMAIN (users, oauth, ai, agent, mcp, ...)
        │
    INFRA (database, events, security, config, logging, cloud)
        │
    SHARED (models, traits, identifiers, client, extension)

Domain crates cannot depend on each other - use traits or events for cross-domain communication.

Available Crates

Shared Layer

Infrastructure Layer

Domain Layer

Application Layer

Entry Layer

Extension Framework

Extensions enable downstream projects to extend core functionality without modifying it.

use systemprompt_extension::*;

struct MyExtension;
impl Extension for MyExtension { ... }
impl ApiExtension for MyExtension { ... }

register_extension!(MyExtension);
register_api_extension!(MyExtension);

Available extension traits:

Extensions are discovered at runtime via the inventory crate.

Development

Prerequisites

• Rust 1.75+
• Docker (for PostgreSQL containers)

Building

# Clone repository
git clone https://github.com/systempromptio/systemprompt-core
cd systemprompt-core

# Build all crates
cargo build --workspace

# Run tests (tests are in separate crates)
cargo test --manifest-path crates/tests/Cargo.toml

# Build specific crate
cargo build -p systemprompt-api

# Run CLI
cargo run -p systemprompt-cli -- --help

Code Quality

SystemPrompt enforces strict code quality through automated tooling:

# Format code
cargo fmt

# Run clippy with strict rules
cargo clippy --workspace

Standards:

• No unsafe code (forbidden)
• No .unwrap() (denied)
• Low cognitive complexity
• Pedantic clippy lints enabled
• All tests in separate test crates

Versioning

Follows Semantic Versioning:

• Major: Breaking API changes
• Minor: New features, backward compatible
• Patch: Bug fixes, backward compatible

Current version: 0.0.1

License

FSL-1.1-ALv2 (Functional Source License) - see LICENSE for details.

Links

• GitHub Repository
• Issues
• Documentation
• Website