ArchitectureModule Registry

Module Registry

Module Registry — Documentation Entry Points (SSOT)

This registry answers a single question:

“Where do I look to understand what modules exist, what is activated, and what is planned?”

It intentionally avoids duplicating long per-module tables that become stale.

1) Activation Status (What Is Live)

If you only read one file, read this:

  • docs/architecture/MODULE_STATUS_SSOT.md
    • Note: HealthModule is ACTIVE

Evidence-level audits and decisions:

  • docs/agent_ops/OUTBOX/audit_hidden_modules_20260211.md (ACTIVE/NESTED/ORPHANED audit + methodology)
  • docs/agent_ops/OUTBOX/task_module_reachability_audit_20260215.md (refreshed audit, supersedes above for current counts)
  • docs/agent_ops/OUTBOX/task_orphaned_modules_decision_sweep_20260211.md (ACTIVATE/ARCHIVE/DELETE decision matrix)

2) Architecture Docs Index

Primary navigation:

  • docs/architecture/INDEX.md

3) Roadmaps And Planning

  • docs/handoff/ROADMAP_v0.8.0.md (current scope + epics)
  • docs/architecture/ROADMAP.md (historical phase roadmap; may contain legacy claims—prefer SSOT + handoff roadmap for current truth)

4) Production Operations (Runbooks)

  • docs/operations/ (deployment, monitoring, backups, DR)

5) Visuals (Interactive HTML)

  • docs/architecture/visuals/Jorvis_Architecture.html
  • docs/architecture/visuals/Agent_Ops_Architecture.html
  • docs/architecture/visuals/Documentation_RAG_Pipeline.html
  • docs/architecture/visuals/OpenClaw_Control_Plane.html

6) How To Keep This Accurate

When you change DI wiring (activate/deactivate a module):

  1. Update docs/architecture/MODULE_STATUS_SSOT.md
  2. If it changes planned work, update docs/handoff/ROADMAP_v0.8.0.md
  3. If it changes operations, update relevant files under docs/operations/