INDUS v1.4.0 Release Notes | Platform Release

Registry-Backed Architecture (New in v1.4.0)

From hardcoded switches to dynamic JSON-backed command routing

graph TB User[User Input] -->|ind command| Parser[Command Parser] Parser --> Registry[Command Registry
registry.json v1.4.0] Registry -->|Lookup & Cache| Core[Core Module
6 commands] Registry -->|Lookup & Cache| System[System Module
8 commands] Registry -->|Lookup & Cache| Project[Project Module
7 commands] Registry -->|Lookup & Cache| Environment[Environment Module
9 commands] Registry -->|Lookup & Cache| Filesystem[Filesystem Module
5 commands] Registry -->|Lookup & Cache| Network[Network Module
6 commands] Registry -->|Lookup & Cache| Developer[Developer Module
4 commands] Registry -->|Lookup & Cache| Package[Package Module
7 commands] Registry -->|Lookup & Cache| Terminal[Terminal Module
3 commands] Registry -->|Lookup & Cache| Workspace[Workspace Module
3 commands] Core --> Output[Terminal Output] System --> Output Project --> Output Environment --> Output Filesystem --> Output Network --> Output Developer --> Output Package --> Output Terminal --> Output Workspace --> Output Legacy[Pre-Registry
v1.3.0] -.->|Migrated from| Parser Legacy -.->|Hardcoded switches| Output style User fill:#FF9933,stroke:#FF9933,color:#0a0a0a style Parser fill:#1a1a1a,stroke:#FF9933 style Registry fill:#1a1a1a,stroke:#9C27B0 style Legacy fill:#1a1a1a,stroke:#666,stroke-dasharray: 5 5 style Output fill:#FF9933,stroke:#FF9933,color:#0a0a0a

What's New in v1.4.0

Registry system introduction and command expansion

Command Registry System

Introduced registry.json as the single source of truth for all commands. Dynamic loading, metadata-driven execution, and extensibility.

✓ JSON-backed command definitions
✓ Dynamic command loading
✓ Metadata-rich command info
✓ Cache-optimized execution

10 Command Modules

Commands organized into logical modules: Core, System, Project, Environment, Filesystem, Network, Developer, Package, Terminal, Workspace.

→ ind list
58 commands across 10 modules
✓ Core, System, Project, Environment...

Performance Optimizations

Command caching, lazy module loading, and optimized registry lookups reduce startup time and execution overhead.

✓ In-memory command cache
✓ Lazy module initialization
✓ Fast registry lookups

Enhanced Command Help

Rich help system with command categories, usage examples, and module-level documentation powered by registry metadata.

→ ind help project
Project Module: 7 commands
project create, project init, ...

Registry Version 1.4.0

The registry tracks its own version, allowing future backward compatibility checks and migration paths.

{
  "registryVersion": "1.4.0",
  "commands": { /* 58 commands */ }
}

Backward Compatibility

All v1.3.0 commands remain functional. Old hardcoded paths migrated seamlessly to registry-backed execution.

✓ Zero breaking changes
✓ Command aliases preserved
✓ Drop-in upgrade

Command Module Breakdown

58 commands organized into 10 logical modules

registry.json Structure

        
              Module
              Commands
              Examples
            
              Core
              6
              help, version, list
            
              System
              8
              sysinfo, cpu, memory
            
              Project
              7
              project create, project init
            
              Environment
              9
              env list, env get, env set
            
              Filesystem
              5
              tree, size, search
            
              Network
              6
              ping, ports, ipinfo
            
              Developer
              4
              git status, lint
            
              Package
              7
              pkg list, pkg install
            
              Terminal
              3
              clear, theme
            
              Workspace
              3
              workspace init, workspace status

Module	Commands	Examples
Core	6	`help`, `version`, `list`
System	8	`sysinfo`, `cpu`, `memory`
Project	7	`project create`, `project init`
Environment	9	`env list`, `env get`, `env set`
Filesystem	5	`tree`, `size`, `search`
Network	6	`ping`, `ports`, `ipinfo`
Developer	4	`git status`, `lint`
Package	7	`pkg list`, `pkg install`
Terminal	3	`clear`, `theme`
Workspace	3	`workspace init`, `workspace status`

Migration from v1.3.0

Seamless upgrade path with zero breaking changes

✅ No Breaking Changes

All v1.3.0 commands work identically. The registry system is transparent to end users — same commands, same behavior, enhanced internals.

🎯 Performance Wins

Faster command lookup (registry cache), reduced startup time (lazy loading), cleaner codebase (JSON-driven instead of switch statements).

📈 Extensibility Foundation

The registry enables future plugin systems, custom commands, and third-party modules without core changes.

Upgrade Instructions

# Download v1.4.0 installer
https://github.com/hari7261/INDUS/releases/tag/v1.4.0

# Run installer (automatically upgrades from v1.3.0)
.\indus-setup-v1.4.0.exe

# Verify registry system
→ ind version
INDUS v1.4.0 • Registry v1.4.0 • 58 commands

# Test command lookup
→ ind list
58 commands across 10 modules (registry-backed)