Verdant™ Documentation

Enterprise Feline Productivity Optimization Suite - Implementation Guide

Quick Start

Get started with Verdant™ in three simple steps:

  1. Fork the Repository: Visit github.com/mesopera/verdant and click "Fork"
  2. Download the Engine: Get the latest verdant-engine.exe from the releases page
  3. Configure & Run: Follow the setup instructions below

Installation

Prerequisites

Setup Process

Step 1: Authentication

Run the authentication wizard to configure GitHub access:

verdant-engine.exe auth

This will guide you through creating a GitHub Personal Access Token and detecting your forked repository.

Step 2: Configuration (Optional)

Review and adjust settings:

verdant-engine.exe config

Configuration file location: %LOCALAPPDATA%\Verdant\config.toml

Step 3: Install as Windows Service

verdant-engine.exe install
verdant-engine.exe start
⚠️ Important: The engine requires full repository access to create commits. Ensure your GitHub token has the repo scope enabled.

Configuration Options

Edit config.toml to customize behavior:

[schedule]
mode = "aggressive_random"     # gentle, balanced, aggressive, aggressive_random, turbo
min_interval_minutes = 30      # Minimum time between commits
max_interval_minutes = 180     # Maximum time between commits
timezone_optimization = true   # Spread commits across timezones
turbo_multiplier = 1.0         # Set to 11.0 for maximum intensity 🚀

[content]
commit_message_style = "absurd_professional"  # normal, professional, absurd_professional

[service]
auto_start = true              # Start on Windows boot
log_level = "info"             # debug, info, warn, error

Advanced Features

Turbo Mode

Turn it up to 11 by setting turbo_multiplier = 11.0 in your configuration. This dramatically increases commit frequency for maximum graph optimization.

Timezone Optimization

The engine intelligently distributes commits across multiple timezones to simulate a global development team, creating a more organic-looking contribution pattern.

Content Generation

The engine automatically generates various types of corporate content:

Monitoring

Track your optimization progress:

Troubleshooting

Service Won't Start

No Commits Being Created

Building from Source

# Clone the repository
git clone https://github.com/mesopera/verdant.git
cd verdant/verdant-engine

# Build release binary
cargo build --release

# Binary will be at: target/release/verdant-engine.exe

Architecture

Verdant™ consists of two main components:

Support

For issues, questions, or contributions:

License

Verdant™ is open source software licensed under the MIT License.