LMM Forge

Access policy: Access from China is prohibited.

LMM Forge is a production-grade, web-first bounty collaboration system for open-source maintenance, with delivery tracking, review/audit trails, and settlement workflows.

Table of Contents

• Overview
• Architecture
• Quick start
• Deployment and upgrades
• What LMM Forge supports
• Repository layout
• Documentation and operations
• Workflow and command reference
• Contribution and support
• Security and legal
• License and attribution

Overview

LMM Forge is a maintained derivative of QuantumNous/new-api with retained upstream compatibility and additional product features for bounty management.

Key differentiators:

• Public bounty board with authenticated workflow controls
• Evidence-driven acceptance for Issue/PR submissions
• Escrowed reward handling with transparent settlement state
• Dispute-aware delivery lifecycle and rating trail

FORK.md captures the formal fork and attribution constraints that govern derivative distribution and branding.

Architecture

Concern	Status
Frontend	Shared React application in apps/web
Default backend	Go provider CLI/service in apps/api-go
Preview backend	Rust provider CLI/service in apps/api-rust (not default production traffic)
LMM CLI	Rust setup tool in apps/lmm (preview: discovery, planning and read-only OAuth login)
Deployment	Signed package transactions or existing standalone systemd upgrades; see deployment and upgrades
Packaging	Provider binaries and immutable runtime assets in packaging/

For existing standalone installations on systemd Linux, see standalone systemd deployment.

Providers install real lmm-api-go or lmm-api-rs binaries. Production and operator actions always enter through the one-hop lmm-api provider symlink. The frontend is released independently.

Quick start

Prerequisites

• git, bun, just
• Database + cache services suitable for local development
• Optional: Go toolchain for native backend work, Rust toolchain for Rust preview runs

Bootstrap

git clone https://github.com/TokenNotIncluded/api.lmm.best.git
cd api.lmm.best
just setup

Run local services

just infra-up   # Starts default PostgreSQL + Valkey when docker-compose.dev.yml exists
just dev        # Starts web + Go backend together

Alternative flows:

just dev-web
just dev-go
just dev-rust

Open http://localhost:3000 and complete the setup flow.

Production-style local checks

just build
just test

Deployment and upgrades

Local development commands are not production installers. Choose the path that matches the existing installation; do not replace package-owned files manually.

Installation	Entry point	Guide
Standalone Go on systemd	sudo bash scripts/lmm-api-deploy.sh systemd doctor, then upgrade and explicit confirm	Standalone workflow
Package-owned Go/Web	Installed /usr/bin/lmm-api-deploy production signed-plan workflow	Package transactions

bash scripts/lmm-api-deploy.sh --help works without a compiled backend. The standalone workflow updates an existing server, not a clean installation. Backend and frontend versions remain independent. Neither path is automatically run against production when code is merged or a release is published.

What LMM Forge supports

• Challenge publication and acceptance
• Contributor submission and evidence intake
• Multi-step review with payout and dispute logic
• User and administrator workflow surfaces for accountability and governance
• Session and security controls documented under authentication contracts
• Operational guardrails for upgrades, cutovers, and cache/auth topology constraints

See docs/open-source-bounties.md for full bounty behavior and settlement rules.

Repository layout

Path	Purpose
apps/web	Shared React frontend
apps/api-go	Go API backend and production default
apps/api-rust	Rust preview backend
deploy	Migration/cutover/deploy documentation and scripts
packaging	Packaging workflows and local package content
docs	Operational guides, legal policy, and API references

Documentation and operations

• docs/README.md: canonical docs index
• docs/authentication.md: authentication and session model
• docs/seamless-upgrades.md: upgrade workflow and constraints
• docs/postgresql-migration.md: migration rehearsal contract
• docs/postgresql-cutover.md: production cutover contract
• docs/valkey-lmm-api.md: dedicated cache architecture
• docs/rust-blue-green.md: ownership and route migration checkpoints
• docs/openapi/api.json: admin API spec
• docs/openapi/relay.json: relay API spec
• docs/legal: legal policy corpus
• THIRD-PARTY-LICENSES.md: dependency and license inventory

Workflow and command reference

Primary command groups

just setup           Install workspace dependencies
just dev             Frontend + Go backend in one process group
just build           Build frontend and Go backend artifacts
just test            Run backend and frontend tests
just check           Formatting, lint, typecheck, and contract checks
just deploy-production  Promote an already-staged signed package release plan

Additional commands

• just infra-up / just infra-down for local infrastructure
• just dev-go, just dev-web, just dev-rust for focused runs
• just clean-generated to clear generated build artifacts
• just docker or just package for environment-specific release outputs

Contribution and support

• Contributing requirements: CONTRIBUTING.md
• Support model: SUPPORT.md
• Code of Conduct: CODE_OF_CONDUCT.md
• Issue workflows: use GitHub Issue templates in .github/ISSUE_TEMPLATE

Security and legal

Security policy is maintained at: SECURITY.md

Legal documents:

• docs/legal/user-agreement.md
• docs/legal/privacy-policy.md
• docs/legal/terms-of-service.md

License and attribution

This repository is distributed under AGPL-3.0. See LICENSE.

Fork attribution and required notices are preserved in NOTICE.