name: overview-repository-structure description: Repository structure overview - Solution organization (Src, Test, Docker, Docs), project dependencies, folder conventions, and codebase navigation. Start here for understanding the repository layout. Keywords: repository-structure, solution-organization, project-organization, codebase-navigation, folder-structure, project-dependencies last-updated: 2026-02-15 difficulty: basic tokens: ~1.5K

DRN-Project Repository Structure

Complete reference for repository organization, solution structure, and project dependencies.

When to Apply

• Navigating the codebase for the first time
• Understanding project relationships and dependencies
• Locating specific functionality across the repository
• Setting up development environment

Repository Layout (Physical)

The physical directory structure separates source code, documentation, and agent resources.

DRN-Project/
├── .agent/                    # Agent skills and workflows
│   ├── rules/                 # DiSCOS rules
│   └── skills/                # Expert skills (this directory)
├── .github/workflows/         # CI/CD workflows
├── DiSCOS/                    # Distinguished Secure Cognitive OS documentation
├── Docker/                    # Container definitions (Postgre, Graylog, RabbitMQ)
│
├── DRN.Framework.*/           # Framework packages (Physical folders in root)
├── DRN.Nexus.*/               # Nexus microservice hub (Physical folders in root)
├── Sample.*/                  # Sample DDD application (Physical folders in root)
├── DRN.Test.*/                # Test projects (Physical folders in root)
│
├── DRN.slnx                   # Solution file (defines logical structure)
├── docker-compose.yml         # Global compose for all services
└── README.md                  # Project documentation

Solution Structure (Logical)

The .slnx solution file organizes the flat physical project list into logical Solution Folders for better navigation in IDEs.

Framework Package Hierarchy

graph TD
    SK[DRN.Framework.SharedKernel] --> U[DRN.Framework.Utils]
    U --> H[DRN.Framework.Hosting]
    U --> EF[DRN.Framework.EntityFramework]
    H --> T[DRN.Framework.Testing]
    EF --> T
    U --> J[DRN.Framework.Jobs]
    U --> MT[DRN.Framework.MassTransit]
    
    style SK fill:#e1f5fe
    style U fill:#b3e5fc
    style H fill:#4fc3f7
    style EF fill:#4fc3f7
    style T fill:#0288d1

Dependency Order (bottom to top):

1. SharedKernel - No external DRN dependencies (lightweight)
2. Utils - Depends on SharedKernel
3. Hosting / EntityFramework - Depend on Utils
4. Testing - Depends on Hosting + EntityFramework

Sample Application Tiers

See: overview-ddd-architecture.md

Project Dependencies (Sample)

Sample.Hosted
├── Sample.Application
├── Sample.Infra
│   ├── Sample.Domain (entities, aggregates)
│   └── Sample.Contract (DTOs, events)
└── DRN.Framework.Hosting
    └── DRN.Framework.Utils
        └── DRN.Framework.SharedKernel

Key Configuration Files

CI/CD Workflows

Common Development Commands

# Build solution
dotnet build DRN.slnx

# Run tests
dotnet test DRN.slnx

# Run Sample.Hosted
dotnet run --project Sample.Hosted

# Start dependencies
docker compose -f Docker/Postgre/docker-compose.yml up -d

# Frontend build (Sample.Hosted)
cd Sample.Hosted && npm run build

Related Skills

• overview-drn-framework.md - Framework architecture
• overview-drn-testing.md - Testing philosophy
• overview-ddd-architecture.md - Sample application architecture