Distribution Department

Marketplace listings, SEO optimization, affiliate programs, partnerships.

Overview

The Distribution department manages distribution channels for a solo SaaS business: marketplace listings across platforms, SEO keyword tracking with position monitoring, and affiliate partner management with commission tracking. The engine provides three manager subsystems backed by ObjectStore.

Current Status: Skeleton

The distro engine has manager structures but minimal business logic (~390 lines total across lib.rs and three manager modules). The managers provide CRUD operations:

• MarketplaceManager – add_listing(sid, platform, name, url), list_listings(sid), publish_listing(sid, listing_id). Creates listings with ListingStatus (Draft/Published/Archived) and tracks revenue per listing.
• SeoManager – add_keyword(sid, keyword, position, volume), list_keywords(sid), track_ranking(sid, keyword_id, new_position). Tracks keyword positions and search volume.
• AffiliateManager – add_partner(sid, name, commission_rate), list_partners(sid), track_commission(sid, partner_id, amount). Manages affiliate partners with commission rates.

The department is fully registered and bootable – it appears in the department registry, responds to chat, and has 4 agent tools wired. However, it needs the following to be production-ready:

• Automated marketplace listing sync with real platforms
• SEO position history and trend analysis
• Affiliate link generation and click tracking
• Revenue attribution across channels
• Automated SEO audit recommendations via AgentPort
• Scheduled ranking checks via job queue

Engine Details

Crate: distro-engine (~390 lines)

Struct: DistroEngine

Constructor:

#![allow(unused)]
fn main() {
DistroEngine::new(
    storage: Arc<dyn StoragePort>,
    events: Arc<dyn EventPort>,
    agent: Arc<dyn AgentPort>,
    jobs: Arc<dyn JobPort>,
)
}

Managers:

Implements: rusvel_core::engine::Engine trait (kind: "distro", name: "Distribution Engine")

Manifest

Declared in dept-distro/src/manifest.rs:

id:            "distro"
name:          "Distribution Department"
description:   "Marketplace listings, SEO optimization, affiliate programs, partnerships, API distribution channels"
icon:          "!"
color:         "teal"
capabilities:  ["marketplace", "seo", "affiliate"]

System Prompt

You are the Distribution department of RUSVEL.

Focus: marketplace listings, SEO optimization, affiliate programs, partnerships, API distribution channels.

Tools

Tools registered at runtime via dept-distro/src/tools.rs (4 tools):

Personas

None declared in the manifest.

Skills

None declared in the manifest.

Rules

None declared in the manifest.

Jobs

None declared in the manifest. Future candidates:

• Scheduled SEO position checks
• Marketplace listing status sync
• Affiliate commission payouts

Events

Defined Constants (engine)

These constants are defined in the engine but are not yet emitted automatically by the manager methods. They are not listed in the manifest’s events_produced.

Consumed

None.

API Routes

None declared in the manifest. The department is accessible via the standard parameterized routes:

• GET /api/dept/distro/status – department status
• POST /api/dept/distro/chat – SSE chat

CLI Commands

Standard department CLI:

rusvel distro status    # One-shot status (alias: "distribution")
rusvel distro list      # List items
rusvel distro events    # Show events

Entity Auto-Discovery

The standard CRUD subsystems are available at /api/dept/distro/*:

• Agents, Skills, Rules, Hooks, Workflows, MCP Servers

Chat Flow

sequenceDiagram
    participant U as User
    participant API as /api/dept/distro/chat
    participant Agent as AgentRuntime
    participant Tool as distro.* tools
    participant Engine as DistroEngine
    participant Store as StoragePort

    U->>API: POST "Show me an SEO report"
    API->>Agent: run_streaming(system_prompt, tools)
    Agent->>Tool: distro.seo.analyze(session_id)
    Tool->>Engine: seo().list_keywords(sid)
    Engine->>Store: objects.list("keywords")
    Store-->>Engine: Vec<Keyword>
    Tool->>Tool: compute avg position, aggregate
    Tool-->>Agent: {"keyword_count": 5, "avg_position": 12.4, "keywords": [...]}
    Agent->>Tool: distro.analytics.report(session_id)
    Tool->>Engine: marketplace().list_listings(sid)
    Tool->>Engine: affiliate().list_partners(sid)
    Tool->>Engine: seo().list_keywords(sid)
    Engine-->>Tool: aggregated data
    Tool-->>Agent: full analytics report JSON
    Agent-->>API: SSE chunks
    API-->>U: "SEO Report: 5 keywords tracked, avg position 12.4. ..."

Extending the Department

Adding automated SEO audits

1. Add an audit(sid) method to SeoManager that calls AgentPort with keyword data for AI-powered recommendations
2. Register a distro.seo.audit tool in dept-distro/src/tools.rs
3. Add a scheduled job kind for periodic audits
4. Emit distro.seo.ranked events when position changes are detected

Adding marketplace sync

1. Implement platform-specific adapters (similar to content-engine’s LinkedIn/Twitter adapters)
2. Add a sync_listing(sid, listing_id) method that fetches live data from the platform
3. Wire a job kind for periodic sync

Adding revenue attribution

1. Extend MarketplaceManager to track revenue per listing over time
2. Extend AffiliateManager to compute total commissions earned per partner
3. Add a distro.revenue.attribution tool that breaks down revenue by channel
4. Wire the data into the analytics report tool

Port Dependencies