Minotaur Project Structure Analysis and Renaming Recommendations

Current Issues Identified

1. Pipeline Naming ✅ FIXED

• Issue: Pipeline was named “CI/CD Pipeline with Release Management” (containing “enhanced”)
• Solution: Renamed to “CI/CD Pipeline”
• Status: Fixed in current commit

2. Project Naming Misalignment

• Issue: Project is named “Minotaur” but main namespace and folder is “GolemCognitiveGraph”
• Impact: Confusing and inconsistent branding
• NuGet Package: Correctly named “DevelApp.Minotaur” but code structure doesn’t match

3. Non-Descriptive Folder Names

• Issue: “Advanced” folder name provides no context about its contents
• Current Contents: ContextAwareEditor.cs (context-aware editing capabilities)
• Better Name: Should reflect its actual purpose

Detailed Structure Analysis

Current Structure:

src/
├── GolemCognitiveGraph/           # ❌ Wrong project name
│   ├── Advanced/                  # ❌ Non-descriptive
│   │   └── ContextAwareEditor.cs  # Context-aware editing capabilities
│   ├── Core/                      # ✅ Good
│   │   ├── CognitiveGraphNode.cs
│   │   └── ConcreteNodes.cs
│   ├── Editor/                    # ✅ Good
│   │   ├── EditOperation.cs
│   │   └── GraphEditor.cs
│   ├── Parser/                    # ✅ Good
│   │   └── StepParserIntegration.cs
│   ├── Plugins/                   # ✅ Good
│   │   ├── BuiltInLanguagePlugins.cs
│   │   ├── ILanguagePlugin.cs
│   │   ├── LanguagePluginManager.cs
│   │   └── LanguageUnparseVisitors.cs
│   ├── Projects/                  # ✅ Good
│   │   ├── IProjectLoader.cs
│   │   ├── ProjectLoader.cs
│   │   └── ProjectModels.cs
│   ├── Unparser/                  # ✅ Good
│   │   ├── GraphUnparser.cs
│   │   └── IUnparseStrategy.cs
│   ├── Visitors/                  # ✅ Good (assumed based on structure)
│   └── GolemCognitiveGraph.csproj # ❌ Wrong project name
├── GolemCognitiveGraph.Demo/      # ❌ Wrong project name
├── GolemCognitiveGraph.Tests/     # ❌ Wrong project name
└── Minotaur.sln                   # ✅ Correct name

Recommended Changes

1. High Priority: Project and Namespace Renaming

A. Main Project Directory

CURRENT:  src/GolemCognitiveGraph/
PROPOSED: src/Minotaur/
REASON:   Aligns with project name - GolemCognitiveGraph should simply be Minotaur

B. Support Projects

CURRENT:  src/GolemCognitiveGraph.Demo/
PROPOSED: src/Minotaur.Demo/

CURRENT:  src/GolemCognitiveGraph.Tests/
PROPOSED: src/Minotaur.Tests/

C. Main Project File

CURRENT:  GolemCognitiveGraph.csproj
PROPOSED: Minotaur.csproj

2. Medium Priority: Folder Structure Improvements

A. Context-Aware Features

CURRENT:  Advanced/
PROPOSED: ContextAware/
REASON:   Clearly indicates context-aware editing functionality
CONTENTS: ContextAwareEditor.cs and related context-aware features

3. Namespace Updates Required

All C# files would need namespace updates:

// CURRENT
namespace GolemCognitiveGraph.Advanced;
namespace GolemCognitiveGraph.Core;
namespace GolemCognitiveGraph.Editor;
// etc.

// PROPOSED  
namespace Minotaur.ContextAware;
namespace Minotaur.Core;
namespace Minotaur.Editor;
// etc.

Functionality Analysis vs NuGet Dependencies

Current NuGet Dependencies:

• DevelApp.CognitiveGraph (1.0.0) - Core cognitive graph functionality
• DevelApp.StepParser (1.0.1) - Parsing functionality
• DevelApp.StepLexer (1.0.1) - Lexical analysis
• DevelApp.RuntimePluggableClassFactory (2.0.1) - Plugin system

Functionality That Could Be External:

1. Core Graph Functionality ⚠️ ALREADY EXTERNAL

• Current: Local implementation in Core/
• External: DevelApp.CognitiveGraph package already available
• Recommendation: Consider consolidating with external package or clearly separate concerns

2. Parsing Integration ✅ APPROPRIATE HERE

• Current: Parser/StepParserIntegration.cs
• Analysis: This is integration code specific to Minotaur’s needs
• Recommendation: Keep local - this is the glue code between external parser and Minotaur

3. Plugin System Management ✅ APPROPRIATE HERE

• Current: Plugins/ folder with language plugins
• Analysis: Minotaur-specific plugin implementations
• External: Uses DevelApp.RuntimePluggableClassFactory appropriately
• Recommendation: Keep local - these are Minotaur-specific plugins

4. Project Loading ❓ COULD BE EXTERNAL

• Current: Projects/ folder with project loading functionality
• Analysis: Generic project loading could be a separate package
• Recommendation: Consider if this is Minotaur-specific or reusable

Implementation Impact Assessment

Breaking Changes: HIGH

• All import statements in dependent code would break
• NuGet package consumers would need updates
• Documentation updates required

Migration Effort: MEDIUM-HIGH

• File moves and renames can be automated
• Namespace updates can be scripted with regex
• Build scripts and CI/CD need updates
• Solution file needs updates

Risk Level: MEDIUM

• Well-tested codebase reduces refactoring risk
• Clear folder structure makes automation safer
• Good test coverage provides safety net

Recommendations Summary

Immediate Actions (This PR):

1. ✅ Fix pipeline name (completed)
2. ✅ Rename Advanced/ to ContextAware/ (completed)
3. ✅ Update documentation to reflect correct naming (completed)
4. ✅ Rename GolemCognitiveGraph to Minotaur (IMPLEMENTING NOW)
5. ✅ Update all namespaces (IMPLEMENTING NOW)
6. ✅ Update project files and solution (IMPLEMENTING NOW)
7. ✅ Update CI/CD paths and references (IMPLEMENTING NOW)

Future Major Refactoring (Separate PR):

1. 🏗️ Rename GolemCognitiveGraph to Minotaur
2. 🔧 Update all namespaces
3. 📦 Update project files and solution
4. 🔄 Update CI/CD paths and references

Analysis Recommendations:

1. 🔍 Review overlap with DevelApp.CognitiveGraph package
2. 📊 Assess if Projects/ functionality should be external
3. 📝 Document clear separation between core functionality and Minotaur-specific features

Conclusion

The current structure has significant naming inconsistencies that create confusion. The “GolemCognitiveGraph” naming appears to be legacy from a previous project iteration, while “Minotaur” is the current project identity. A phased approach is recommended:

1. Phase 1 (Current): Complete project renaming and namespace restructuring - IMPLEMENTING NOW
2. Phase 2 (Future): Evaluate external package consolidation opportunities
3. Phase 3 (Analysis): Document clear separation between core functionality and Minotaur-specific features