ADR-057: Project Rename to "idempiere-hub"

Status: ACCEPTED

Date: 2025-12-15

Supersedes:

All temporary naming discussion documents
Informal "idempiere-cli" identity

Context and Problem Statement

The project name "idempiere-cli" no longer accurately reflects the system's architecture, purpose, or vision:

Current Mismatch

Name implies: CLI-focused tool Reality:

Codebase Distribution:
├─ 74% Shared Intelligence Infrastructure
├─ 19% CLI Interface
├─ 4%  Chat API Interface
└─ 3%  MCP Interface

Evolution Timeline

2023-2024: Started as CLI for iDempiere plugin development
2024 Q4: Added MCP server for IDE integration
2024 Q4: Added Chat API for iDempiere UI integration
2025 Q1: Evolved to hub architecture (ADR-048)
2025 Q1: Vision expanded to central service for consultants

Vision: Central Intelligence Service

What we're building:

┌───────────────────────────────────────────────────────────────┐
│              iDempiere Hub (Central Service)                  │
├───────────────────────────────────────────────────────────────┤
│                                                               │
│  Core Value:                                                  │
│  • Build software from specifications automatically          │
│  • Automate support responses for consultants                │
│  • Generate documentation automatically                       │
│  • Consultant efficiency multiplier                           │
│  • Shared intelligence across all users                       │
│                                                               │
│  Infrastructure (74% of codebase):                            │
│  • 40+ specialized tools                                      │
│  • RAG knowledge base (Wiki + KB + AD metadata)              │
│  • Multi-LLM support (Ollama, Claude, GPT, Bedrock)          │
│  • Guardrails &amp; security                                      │
│  • Observability &amp; cost tracking                              │
│                                                               │
│  Interfaces (26% of codebase):                                │
│  • CLI (19%) - Terminal interface                            │
│  • Chat API (4%) - REST API for iDempiere UI                 │
│  • MCP (3%) - IDE integration                                │
└───────────────────────────────────────────────────────────────┘
              ▲              ▲              ▲
              │              │              │
        Consultant A   Consultant B   Agency Team

Problem Statement

Questions to answer:

How do we name a system that's 74% infrastructure, 26% interfaces?
How do we convey "central service for consultants"?
How do we reflect the hub architecture (ADR-048)?
How do we avoid tying identity to specific interface (CLI, API, etc.)?

Decision Drivers

Must Have

✅ Reflects hub architecture (central service + multiple interfaces)
✅ Conveys intelligence/automation value
✅ Not tied to specific interface (CLI, MCP, API)
✅ Professional, technical, timeless
✅ Simple, memorable

Nice to Have

✅ Industry precedent (Docker Hub, TensorFlow Hub)
✅ Scalable (works for SaaS, self-hosted, enterprise)
✅ Consultant/professional audience clear

Avoid

❌ Marketing/trendy terms (autopilot, copilot)
❌ Interface-specific names (cli, api, terminal)
❌ Overly technical jargon
❌ Generic (platform, framework without context)

Options Considered

Final Round (14 options evaluated)

Name	Architecture Fit	Clarity	Simplicity	Service Model	Score
hub	✅✅✅	✅✅✅	✅✅✅	✅✅✅	12/12
agent	✅✅✅	✅✅✅	✅✅✅	✅✅	11/12
cloud	✅✅	✅✅✅	✅✅✅	✅✅✅	10/12
engine	✅✅	✅✅	✅✅✅	✅✅	9/12
automation	✅✅	✅✅✅	✅✅	✅✅	9/12
studio	✅✅	✅✅	✅✅	✅✅	8/12
devkit	✅	✅✅	✅✅✅	✅	7/12
toolkit	✅	✅✅	✅✅	✅	6/12

Why "hub" Won

Scoring Evolution:

Initial evaluation (local tool context): 10/12
Final evaluation (central service context): 12/12

Decision Factors:

Perfect Architectural Match

Hub &amp; Spoke Model:

         ┌─────────────┐
         │   Hub       │
         │  (Central)  │
         └──┬───┬───┬──┘
            │   │   │
         ┌──┘   │   └──┐
         │      │      │
      Spoke  Spoke  Spoke
      (User A) (User B) (Agency)

Industry Precedent
- Docker Hub: Central registry for container images
- TensorFlow Hub: Central repository for ML models
- GitHub Hub: Central platform for code collaboration
- Azure IoT Hub: Central message broker
Central Service Clarity
- "Hub" immediately conveys central/shared service
- Multiple consultants connecting to one hub
- Shared intelligence across all users
Flexibility
- Works for SaaS deployment
- Works for self-hosted (enterprise)
- Works for local development
- Not tied to deployment model
Simple & Memorable
- 3 letters
- Universal understanding
- Easy to remember and type
Not Interface-Specific
- "Hub" describes architecture, not interface
- Supports CLI, MCP, API, and future interfaces
- Doesn't become outdated as interfaces evolve

Decision

Rename project to: idempiere-hub

Tagline: > "Central intelligence hub for iDempiere"

Positioning: > "iDempiere Hub is a central intelligence service that helps consultants build iDempiere solutions faster. Connect to the hub, describe what you want to build, and let AI generate code, support docs, and automate repetitive tasks."

Consequences

Positive

✅ Accurate Identity
- Name matches reality (hub architecture)
- Conveys central service model
- Not misleading
✅ Future-Proof
- Not tied to specific interface
- Scalable (SaaS, self-hosted, enterprise)
- Room for new features/interfaces
✅ Professional
- Industry standard pattern
- Enterprise-appropriate
- Technical without jargon
✅ Memorable
- Short (3 letters)
- Easy to remember
- Universal understanding
✅ Marketing Value
- Clear value proposition
- Consultant audience clear
- Central service benefits obvious

Negative

⚠️ Migration Effort
- Repository rename
- Package refactoring (org.idempiere.cli.* → org.idempiere.hub.*)
- Documentation updates
- User communication
- Estimated: 2-3 weeks
⚠️ Breaking Changes
- Maven artifact ID change
- Package names change (major version)
- MCP server name change in Claude Desktop config
- Users must update configurations
⚠️ Brand Recognition Loss
- Existing "idempiere-cli" users need education
- GitHub stars/forks stay with old repo (redirect needed)
- Search engine rankings reset

Risks and Mitigation

Risk	Impact	Mitigation
User confusion	Medium	Clear communication, migration guide, redirect
Broken dependencies	High	Deprecation period, backward compatibility
Lost discoverability	Low	GitHub redirect, SEO optimization
Community resistance	Low	Explain rationale, community feedback period

Implementation Plan

Phase 1: Non-Breaking Rename (v2.0.0) - 1 week

Changes:

✅ GitHub repository: idempiere-cli → idempiere-hub
✅ Binary name: idempiere-hub-runner.jar → idempiere-hub.jar
✅ Documentation: All references updated
✅ README, USER_GUIDE, FEATURES
❌ Keep package names unchanged: org.idempiere.cli.* (backward compat)

Deliverables:

v2.0.0 Release:
├─ New repository: github.com/cloudempiere/idempiere-hub
├─ Old repository: Redirects to new
├─ Binary: idempiere-hub.jar
├─ Packages: org.idempiere.cli.* (unchanged)
├─ Maven: com.cloudempiere:idempiere-hub:2.0.0
└─ Docs: All updated to &quot;idempiere-hub&quot;

Migration Guide for Users:

# Old
git clone github.com/cloudempiere/idempiere-hub
java -jar idempiere-hub-runner.jar

# New (v2.0.0)
git clone github.com/cloudempiere/idempiere-hub
java -jar idempiere-hub.jar

# Functionality identical, just renamed

Phase 2: Package Refactoring (v3.0.0) - 2 weeks

Changes:

✅ Package rename: org.idempiere.cli.* → org.idempiere.hub.*
✅ Class names: Keep (CliRouterAgent, etc. are fine)
✅ Maven coordinates: com.cloudempiere:idempiere-hub:3.0.0
✅ Major version bump (breaking changes)

Migration for Developers:

&lt;!-- Old (v2.x) --&gt;
&lt;dependency&gt;
    &lt;groupId&gt;com.cloudempiere&lt;/groupId&gt;
    &lt;artifactId&gt;idempiere-cli&lt;/artifactId&gt;
    &lt;version&gt;1.68.0&lt;/version&gt;
&lt;/dependency&gt;

&lt;!-- New (v3.x) --&gt;
&lt;dependency&gt;
    &lt;groupId&gt;com.cloudempiere&lt;/groupId&gt;
    &lt;artifactId&gt;idempiere-hub&lt;/artifactId&gt;
    &lt;version&gt;3.0.0&lt;/version&gt;
&lt;/dependency&gt;

Phase 3: Service Platform Features (v3.5.0+) - Ongoing

New Features:

# Hub authentication
idempiere-hub login --email user@example.com

# Build from specifications
idempiere-hub build --spec order-automation.yaml

# Automated support
idempiere-hub support ask &quot;how to create callout?&quot;

# Documentation generation
idempiere-hub docs generate --module my-plugin

# Knowledge sharing
idempiere-hub knowledge contribute --from solved-issues/

Migration Checklist

Repository & GitHub

[ ] Create new repo: github.com/cloudempiere/idempiere-hub
[ ] Transfer code from idempiere-cli
[ ] Set up redirect: idempiere-cli → idempiere-hub
[ ] Update GitHub description, topics, about
[ ] Update GitHub workflows (CI/CD)
[ ] Create v2.0.0 release with migration notes

Code Changes (v2.0.0)

[ ] Update binary name: IdempiereCli.java → IdempiereHub.java (main class)
[ ] Update pom.xml: artifact ID, name, description
[ ] Update MANIFEST.MF: bundle name
[ ] Update native image config
[ ] Keep packages unchanged: org.idempiere.cli.*

Documentation

[ ] README.md - Full rewrite with new positioning
[ ] USER_GUIDE.md - Update all command examples
[ ] FEATURES.md - Update feature descriptions
[ ] CONTRIBUTING.md - Update repository references
[ ] CLAUDE.md - Update project description
[ ] All ADRs - Add reference to ADR-057
[ ] CHANGELOG.md - Document rename in v2.0.0

Configuration Files

[ ] Docker: Dockerfile, image name
[ ] MCP: Server name in examples
[ ] GitHub Actions: Workflow names, artifact names
[ ] Maven: pom.xml artifact coordinates
[ ] NPM: Package name (if published)

User Communication

[ ] Blog post: "Why we're renaming to idempiere-hub"
[ ] GitHub announcement issue
[ ] Update wiki.idempiere.org references
[ ] Email existing users (if applicable)
[ ] Social media announcement

Marketing Materials

[ ] Update tagline everywhere
[ ] Create new logo/icon (optional)
[ ] Update website (if exists)
[ ] Update demo videos/screenshots
[ ] SEO optimization for "idempiere hub"

Positioning & Messaging

Elevator Pitch (30 seconds)

> "iDempiere Hub is a central intelligence service for iDempiere consultants. Connect to the hub, describe what you need—whether it's building a custom workflow, automating support, or generating documentation—and let AI handle it. Shared intelligence across all consultants means everyone gets smarter together."

Key Messages

Central Service
- "One hub, many consultants"
- "Shared intelligence, multiplied efficiency"
- "Connect once, access everywhere (CLI, IDE, browser)"
Automation Value
- "Build software from specifications"
- "Automate repetitive consulting tasks"
- "Generate docs automatically"
Intelligence
- "40+ specialized AI tools"
- "RAG-powered knowledge base"
- "Learns from every consultant's work"

Comparison Table

Old Identity	New Identity
idempiere-cli	idempiere-hub
CLI tool for developers	Central intelligence service
Local execution	Hub + spoke model
Single user	Multi-tenant, collaborative
Tool collection	Intelligence platform
100% CLI	CLI + MCP + API

Timeline

Phase	Duration	Target Date	Deliverable
Phase 1	1 week	2025-12-22	v2.0.0 with new name
Phase 2	2 weeks	2026-01-05	v3.0.0 with new packages
Phase 3	Ongoing	2026 Q1+	Service platform features

ADR-048: iDempiere AI Hub - Unified Architecture
ADR-049: Project Rebranding - From CLI to AI Hub
ADR-054: AI Tool Architecture - Purpose and Evolution
ADR-055: Tool Ecosystem Architectural Review

References

Industry Examples

Docker Hub - Central container registry
TensorFlow Hub - ML model repository
Azure IoT Hub - Central message broker

Internal Documents

Architecture diagrams (ADR-048)
Tool framework documentation (ADR-054)
Validation report (2025-12-15)

Approval

Decision Made By: Project Lead Date: 2025-12-15 Status: ACCEPTED

Next Actions:

Create GitHub issue for v2.0.0 rename
Assign implementation tasks
Set target date: 2025-12-22
Begin Phase 1 implementation

ADR-057 | Version 1.0 | 2025-12-15 Status: ACCEPTED Next: Phase 1 Implementation (v2.0.0 Rename)