🕉️ Dhurandhar v2.0.0 - Dharma-Centric System Design Framework

Where Ancient Wisdom Meets Modern Design

The world's first dharma-centric system design framework that combines Hindu mythology with software engineering best practices.

🎯 What is Dhurandhar v2.0.0?

Dhurandhar is a dharma-first, phase-based system design framework featuring:

• 8 Mythological Master Agents - Each Pandava brother leads a design phase
• Dharmic Evaluation - Every feature judged by 5 dharmic principles
• Decision Registry - Ask-once persistence pattern for all standards
• Cascading Review - Each phase reviewed by the previous agent
• Constraint Propagation - Auto-flows constraints across phases
• Party Mode - Multi-stakeholder democratic voting
• Quality Metrics - Elegance, Precision, Drift, Quality scoring
• Imperial Blessing - Final approval from Emperor Yudhishthira

The 8-Phase Journey

Yudhishthira → Bhishma → Sahadeva → Nakula → Bheema → Arjuna → Bheema → Draupadi
  Features   Requirements  Entities    APIs      HLD      LLD    Implementation  Audit

Unlike traditional frameworks, Dhurandhar enforces righteousness, quality, and accountability at every step.

🏗️ The 8 Master Agents (Pandavas)

Phase 1: Yudhishthira - The Emperor (Features Discovery)

Role: Dharmaraja, Truth Seeker Evaluates: Every feature through 5 dharmic questions Modes: Brainstorming (solo) + Party Mode (multi-stakeholder voting) Manages: Decision Registry (Ask-Once Persistence Pattern)

dhurandhar yudhishthira
dhurandhar decisions  # View/edit Decision Registry

Output: Dharma-aligned features with council votes

Phase 2: Bhishma - The Grand Sire (Requirements Engineering)

Role: Ancient Strategist, Constraint Master Defines: Functional Requirements, NFRs, Constraints, Trade-offs Auto-populates: NFRs from Decision Registry (security, performance standards)

dhurandhar bhishma

Output: Complete requirements with constraints Review: Yudhishthira validates features → requirements mapping

Phase 3: Sahadeva - The Astrologer (Entities & Domain)

Role: Divine Seer, Domain Modeler Models: Entities, Relationships, Aggregates Applies: Cosmic Patterns (Duality, Lifecycle Orbit, Invariants) Enforces: Entity naming from Decision Registry Receives: Technical/Legacy constraints from Bhishma

dhurandhar sahadeva

Output: Domain model with cosmic patterns Review: Bhishma validates requirements → entities coverage

Phase 4: Nakula - Master of Beauty (API Design)

Role: Elegance Enforcer, API Architect Designs: REST, GraphQL, gRPC APIs Scores: Elegance (naming, hierarchy, verbs, errors) Enforces: API naming from Decision Registry Receives: Security/Technical constraints from Bhishma

dhurandhar nakula

Output: API specifications with elegance scores Review: Sahadeva validates entities → APIs (CRUD coverage)

Phase 5: Bheema - The Mighty (High-Level Design)

Role: Powerful Architect, Strategy Decider Defines: The 7 Strategic Decisions Validates: Against Decision Registry Receives: ALL constraints from Bhishma

dhurandhar bheema

Output: Service architecture + 7 strategic decisions Review: Nakula validates APIs → Services

Phase 6: Arjuna - Master of Precision (Low-Level Design)

Role: Perfect Warrior, Class Designer Designs: Classes, Methods, DB Schemas Scores: Precision (0-100%)

dhurandhar arjuna

Output: Detailed class designs with precision scores Review: Bheema validates services → classes

Phase 7: Bheema Returns (Implementation)

Role: Implementation Commander Plans: Code generation, tests, infrastructure

dhurandhar bheema  # Auto-detects Phase 7

Output: Implementation roadmap Review: Arjuna validates classes → implementation

Phase 8: Draupadi - The Purifier (Review & Audit)

Role: Quality Enforcer Audits: Drift, Compliance, Quality, Dharma Grants: Imperial Blessing

dhurandhar draupadi

Output: Audit report + Imperial Blessing (if worthy) Review: Bheema validates implementation → deployment readiness

✨ Unique Features

1. Dharmic Evaluation (5 Sacred Questions)

Every feature is judged through dharmic principles:

• Satya (Truth): Does it solve a real problem?
• Ahimsa (Non-harm): Does it avoid dark patterns?
• Artha (Value): Does it provide economic value?
• Karma (Action): Can it be implemented?
• Moksha (Liberation): Does it free users?

Result: Features automatically categorized as dharmic, neutral, or adharmic

2. Decision Registry (Ask-Once Persistence)

• Define naming conventions, error standards, security policies ONCE
• Automatically enforced across ALL 8 phases
• No repetitive decisions
• Perfect consistency

Managed by: Yudhishthira Used by: All agents

3. Party Mode (Multi-Stakeholder Voting)

Democratic feature approval with 6 stakeholder personas:

• Drupada (Business Sponsor) - ROI focused
• Virat (Product Owner) - User empathy
• Dhritarashtra (Customer) - Accessibility champion
• Jarasandha (Competitor) - Market pressure
• Vidura (Technical Advisor) - Feasibility
• Sanjaya (Observer) - Documentation

Each votes: -2 to +2 Result: Democratic feature prioritization

4. Cascading Review (7 Review Types)

Every phase reviewed by the previous agent:

1. Yudhishthira reviews Bhishma (Features → Requirements)
2. Bhishma reviews Sahadeva (Requirements → Entities)
3. Sahadeva reviews Nakula (Entities → APIs)
4. Nakula reviews Bheema (APIs → Services)
5. Bheema reviews Arjuna (Services → Classes)
6. Arjuna reviews Bheema (Classes → Implementation)
7. Bheema reviews Draupadi (Implementation → Audit)

Result: Automated drift detection, accountability at every phase

5. Constraint Propagation

Constraints from Phase 2 auto-flow to affected phases:

• Technical constraints → Sahadeva, Nakula, Arjuna, Bheema
• Security constraints → Nakula, Bheema, Arjuna
• Performance constraints → Bheema, Arjuna
• Regulatory constraints → ALL phases

Real-time validation with user confirmation for violations

6. Quality Metrics Throughout

• Elegance Score (Nakula) - API design beauty (0-100%)
• Precision Score (Arjuna) - Class design accuracy (0-100%)
• Drift Score (Draupadi) - Design vs implementation alignment
• Quality Score (Draupadi) - Overall system quality (0-100%)
• Constraint Satisfaction (Draupadi) - Compliance percentage

7. Imperial Blessing (Final Approval)

Emperor Yudhishthira grants final approval based on:

• Drift < 25%
• Quality >= 70%
• No dark patterns
• No privacy violations
• Decision Registry compliant
• Constraint satisfaction >= 80%

If unworthy: Specific guidance on what to fix If worthy: Majestic blessing speech + Phase 8 complete!

🚀 Quick Start

Installation

npm install -g [email protected]

Initialize Project

dhurandhar init

Run Phase by Phase

dhurandhar phase 1    # Features Discovery
dhurandhar next       # Auto-advance to next phase
dhurandhar status     # Check current phase status

🎯 Key Differentiators

1. Phase-Based Design Process

Unlike other frameworks, Dhurandhar enforces the proper sequence:

• ✅ Features BEFORE Requirements
• ✅ Requirements BEFORE Entities
• ✅ Entities BEFORE API
• ✅ API BEFORE Implementation

2. Multi-Agent System

Each phase has a Master Agent + Sub-Agents

3. Decision Registry (from v1.0.2)

Stock decisions ONCE, enforce EVERYWHERE

4. Ask-Once Persistence

Framework remembers decisions forever

5. Architectural Drift Detection

Auto-detect gaps between design and implementation

📊 v2.0.0 vs v1.0.2

| Feature | v1.0.2 | v2.0.0 | |---------|--------|--------| | Structure | Feature-based | Phase-based process | | Requirements Engineering | ❌ No | ✅ Phase 2 | | Domain Modeling | Basic | ✅ Complete | | LLD | ❌ No | ✅ Phase 6 |

📦 Status

Current Version: v2.0.0-alpha.1
Status: Foundation + Phase 1 skeleton
Stable Version: v1.0.2 (available on npm)

📝 License

MIT © Dhurandhar Framework

Dhurandhar v2.0.0: The proper way to design systems 🎯