Skip to content

Module Ecosystem

UnDaoDu edited this page Apr 8, 2026 · 5 revisions

Module Ecosystem

The Foundups-Agent repository contains 120+ modules organized across 7 enterprise domains plus the WRE Core Engine (which has special architectural status). All modules follow the WSP 3 Enterprise Domain Organization protocol — functionality is distributed by function, not consolidated by platform.


Enterprise Domains

AI Intelligence (modules/ai_intelligence/)

AI and LLM systems that provide cognitive capabilities across the ecosystem.

Key modules: banter_engine (AI response generation), multi_agent_system (agent coordination), rESP_o1o2 (quantum state detector framework), ai_overseer (security and compliance oversight including OpenClaw Security Sentinel).

Communication (modules/communication/)

Real-time messaging, chat processing, and dialogue management.

Key modules: livechat (YouTube/Twitch/Discord chat protocols), moltbot_bridge (OpenClaw DAE "The Frontal Lobe", capability audit, action ledger, conversation engine, execution routes), live_chat_poller, live_chat_processor.

Platform Integration (modules/platform_integration/)

External API adapters and platform connectors.

Key modules: linkedin_agent (professional network automation), youtube_proxy (unified YouTube API gateway following WSP 42), x_twitter (first DAE communication node, WSP 26-29 compliant), remote_builder (webhook-based remote build orchestration).

Infrastructure (modules/infrastructure/)

Core system services, CLI, agent management, and daemon processes.

Key modules: cli (main command-line interface with OpenClaw menu), agent_management (multi-agent coordination), dae_daemon (DAE launch broker), compliance_agent (WSP compliance enforcement), documentation_agent, module_scaffolding_agent, llm_client.

Gamification (modules/gamification/)

Engagement mechanics, reward systems, and token loops.

Key modules: core (reward mechanics and token circulation).

Blockchain (modules/blockchain/)

Decentralized infrastructure, DAE architecture, and tokenomics.

Key modules: src (DAE and tokenomics implementation).

FoundUps (modules/foundups/)

Individual FoundUp instances and the platform infrastructure. This is where compute-native ventures live.

Instances: gotjunk (proto-ready), move2japan (incubating), pqn_swarm_hub (active), pqn_portal (incubating), social_twin (incubating), simulator (active), agent_market (FAM daemon), agent (base framework), ecosystem_animation (supporting).

Platform: foundup_spawner.py (creates new instances), platform_manager.py (manages multiple FoundUps), runtime_engine.py (execution environment).

See the dedicated FoundUps Portfolio page for full details on each instance.

WRE Core (modules/wre_core/)

The Windsurf Recursive Engine — the autonomous build system with special architectural status. WRE orchestrates module creation, coordinates agents, manages the CABR loop, and drives recursive self-improvement across the entire ecosystem.


Module Organization Rule: Function Over Platform

The cardinal rule of WSP 3: distribute by function, not by platform.

Correct (Function-Based) Wrong (Platform-Based)
YouTube API → platform_integration/youtube_proxy/ Everything YouTube → modules/youtube/
YouTube chat → communication/livechat/ Everything LinkedIn → modules/linkedin/
YouTube analytics → ai_intelligence/
LinkedIn API → platform_integration/linkedin_agent/
LinkedIn messaging → communication/

This ensures that communication logic, AI logic, and API logic remain reusable across all platforms rather than being siloed.


Module Structure (WSP 22)

Every module follows a standardized structure:

modules/<domain>/<module_name>/
├── src/                  # Implementation
│   └── module.py
├── tests/                # Test suite (≥90% coverage per WSP 5)
│   └── test_module.py
├── README.md             # Module overview and usage
├── ROADMAP.md            # Development phases (POC → Prototype → MVP)
├── ModLog.md             # Change tracking
├── INTERFACE.md          # API documentation (WSP 11)
├── module.json           # Module metadata
└── requirements.txt      # Dependencies

Module Lifecycle

Modules progress through development phases tracked in their ROADMAP.md:

  1. POC (Proof of Concept) — Core functionality demonstrated
  2. Prototype — Feature-complete with basic test coverage
  3. MVP (Minimum Viable Product) — Production-ready with ≥90% test coverage, full documentation

Each phase transition is validated by FMAS audit (WSP 4) and WRE orchestration (WSP 30).


Key Statistics (March 2026)

Metric Value
Total modules 120+
Enterprise domains 7 + WRE Core
FoundUp instances 9 active
WSP protocols governing modules 116+
Priority P0 modules 4 (remote_builder, linkedin_agent, youtube_proxy, x_twitter)
Test coverage target ≥90% per WSP 5

Related Pages


Back to Wiki Home

Clone this wiki locally