Skip to main content

Executive Summary

The WepNG_MVC platform is a critical legacy monolith currently undergoing a strategic modernization process. This documentation aggregates the analysis of its current state, highlighting key architectural bottlenecks and the roadmap for its evolution.

🧠 Living Documentation Strategy​

This documentation is not a static archive but a Living System, integrated directly into the development workflow ("Quality First" Methodology). It is structured to serve both human engineers and AI agents efficiently.

Core Principles​

  1. Truth vs. Proposal: We strictly separate what is (Specs/Current) from what will be (Specs/Proposals) to avoid ambiguity.
  2. Organic Learning: The structure guides the reader from high-level concepts (Overview) to deep implementation details (Modules, Code), filtered by strategic importance.
  3. Risk Awareness: Anti-patterns and legacy risks are highlighted early to prevent regression.

📂 Document Structure​

The knowledge base is organized into logical layers:

  1. 🏛️ High-Level Overview:
    Understanding the domain, the system landscape, and how to deploy. Start here.

  2. ✅ Specifications (Current):
    The "Gold Standard" of current functionality. Business rules and logic currently in production.

  3. 🧪 Specifications (Draft):
    Work-in-Progress specs including Business Rule candidates and reverse-engineered logic awaiting verification.

  4. 🔍 Module Analysis:
    Deep dives into the monolithic modules (OMGT, BO, MNT, etc.), analyzing their dependencies and refactoring potential.

  5. ⚖️ Architectural Decisions (ADR):
    The record of why specific architectural choices were made (e.g., .NET 8 Migration, Modular Monolith).

  6. ⚠️ Anti-Patterns & Risks:
    A catalog of technical debt ("God Objects", "Leaky Abstractions") to avoid and refactor.

  7. 📏 Guidelines:
    Operational standards for the team: Async Strategy, Gherkin Best Practices, and Use Case definitions.

  8. 🏗️ Strategic Patterns:
    Aspirational architectural patterns (e.g., Strangler Fig, Logic Side-car) guiding the modernization.

  9. 🚧 Roadmap:
    Consolidated timelines for stabilization, refactoring, and migration.

  10. 📝 Backlog: Tracking of granular maintenance tasks and agent configuration debt.

  11. 🎭 Platonic Dialogues: Simulated debates between different Agent Personas (Architect, Critic, Veteran) to explore architectural trade-offs (e.g., Microservices vs Modular Monolith) before making decisions.

Note: A detailed Security Audit is tracked separately in Metrics & Analysis.