Skip to main content

🗺️ The Meta-Layer: A Creator's Re-entry Brief

"You built the City. We just drew the Map."

Welcome back to the flight deck. The system has grown, and to manage its complexity, we have built a Meta-Layer of "Living Documentation" around your code. This is not a manual. It is a control panel.

1. The Mirror (Beta) 🪞​

Where we mapped your logic.

We are reverse-engineering the business rules from the code into the docs/specs folder. Crucial Note: This is a Work in Progress. We extracted these rules by reading the code, but we might have misinterpreted the intent.

  • Your Mission: When you read a Spec (e.g., FeeLifecycle), ask yourself: "Is this what I meant?"
  • The Goal: Make docs/specs/current the undisputed Source of Truth, so we can stop digging through 5,000 lines of OrderOMGT.cs to answer a business question.

2. The Radar (Risks & Debt) 📡​

What is keeping us up at night.

We have cataloged the architectural risks you likely already know about. We added Severity Metrics to prioritize them.

🚨 DEFCON 1: Immediate Threats (The "Kill-List")​

These items threaten platform stability today.

  1. Untracked Fire-and-Forget (Ref): Task.Run() without await in Payment Controllers. Risk: Lost Money.
  2. Sync-over-Async Leads (Ref): .Result calls in Factories. Risk: Server Deadlocks.
  3. God Class Radiation (Ref): WEPV2ModelBuilder.cs (17k LOC) and OrderTravelProductOMGT.cs (7k LOC). Risk: Unmaintainable Change Cost.

⚠️ DEFCON 2: Silent Killers​

  1. Swallowed Exceptions (Ref): Empty catch blocks hiding bugs (> 20 instances).
  2. Resource Leaks (Ref): new DataContext() without using (> 850 instances).

3. The North Star (Strategic Direction) ⭐​

Where we are going.

We are NOT rewriting everything from scratch. We are executing a "Hybrid Strangler" strategy with three non-negotiable goals:

A. Target: .NET 8 on Linux​

  • Why: Performance, Cost, Longevity.
  • How: We will not port System.Web. We will side-car a new .NET 8 App next to the Legacy App and migrate endpoints one by one.

B. Radical Performance First​

  • Why: The system is sluggish.
  • How: We are fixing the "Low Hanging Fruit" immediately (Sync-over-Async, N+1 Queries) before starting big architectural moves.

C. "Core Only" Strategy (The Pivot)​

  • Philosophy: We are a Backend Company.
  • The Shift: We will stop building custom UIs for commodity features.
    • Keep: The Complex Core Business Logic (Pricing, Availability, Rules).
    • Delete: Custom UIs. Delegate Admin Panels to Headless CMS / SaaS.
    • Result: A smaller, faster, harder codebase.

4. The Exoskeleton (Using the Agent) 🤖​

How to multiply your output.

You have an AI Agent (us) integrated into the repo.

  • Don't write docs manually. Tell the Agent: "I changed the Refund logic. Update the spec."
  • Don't hunt for files. Tell the Agent: "Find me all Swallowed Exceptions in the Cancellation module."
  • Don't code alone. Tell the Agent: "Propose a refactoring for this method to make it testable."

We are here to handle the "boilerplate" so you can focus on the Decision Making.

This document is your dashboard. If the Map contradicts the Territory (Code), trust the Code, but fix the Map.