Skip to content

feat: DISHA v5.0.0 — Global Launch & Elite Modernization #66

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Tashima-Tarsh merged 1 commit into from
Apr 15, 2026
Merged

feat: DISHA v5.0.0 — Global Launch & Elite Modernization #66

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,35 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/)

---

## [v5.0.0] — 2026-04-16

### 🚀 Major Overhaul
- **Brand Identity Redesign** — Migrated from developer-centric aesthetic to a "Premium World-Class" Luxury Minimalist identity (Space Obsidian & Quantum Indigo).
- **Core Architecture Stabilization** — Unified project versioning to v5.0.0 across all 7 layers (Root, CLI, AI-Platform, Cognitive-MIND, Decision-Engine, Cyber-Defense, Quantum, Historical Strategy).
- **Dependency Upgrades** — Critical modernization of core runtimes and libraries.
- Upgraded **React 19** and **Next.js 16.3** for the elite dashboard.
- Upgraded **TypeScript 6.0** and **esbuild 0.28** for the core CLI engine.
- Upgraded **Anthropic SDK** to 0.89.0 for improved AGI tool-calling.
- Upgraded **@opentelemetry** to 2.6.1 for enterprise-grade observability.

### 🎨 UI/UX Improvements
- **New CSS Design System** — Implementation of high-end HSL design tokens and glass-premium components.
- **Elite Hero Experience** — Redesigned landing page with immersive animations and quantum atmospheric accents.
- **Professional Metadata** — Full OpenGraph and Twitter SEO tags for high discovery on GitHub and Social Media.

### 📖 Documentation & GitHub Optics
- **README.md Evolution** — Complete rewrite with professional infographics, Mermaid diagrams, and clear value-proposition mapping.
- **Project Wiki Refresh** — Modernized the knowledge-base structure for v5.0.0 clarity.
- **Professional Repositories Files** — Created `SECURITY.md`, `CODE_OF_CONDUCT.md`, and modernized `CONTRIBUTING.md`.
- **Health Reporting** — Added `REPORT.md` with system architecture diagrams and repo health scores.

### 🔧 Stability & Bug Fixes
- Fixed `GCNEncoder` handling for missing `edge_index` in inference.
- Resolved CI/CD blocking linting errors across 10 modules.
- Implemented robust test-skipping for missing large model artifacts.

---

## [v3.2.0] — 2026-04-12

### 🐛 Bug Fixes
Expand Down
45 changes: 45 additions & 0 deletions CODE_OF_CONDUCT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
# Contributor Covenant Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a professional setting

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at `conduct@disha.agi`. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

[homepage]: https://www.contributor-covenant.org
Comment on lines +43 to +45

@coderabbitai coderabbitai Bot Apr 15, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Consider upgrading the template to Contributor Covenant v2.1.

Using the newer version improves clarity around enforcement guidelines and reporting expectations.

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@CODE_OF_CONDUCT.md` around lines 43 - 45, The Code of Conduct currently
references Contributor Covenant "version 1.4" and the old URL; update the
document to reference Contributor Covenant v2.1 by replacing the version string
"version 1.4" with "version 2.1", update the linked URL to the v2.1 page (and
the [homepage] reference) so both the inline citation and the [homepage] link
point to the official v2.1 location, and ensure any wording that explicitly
mentions v1.4 is adjusted to reflect v2.1.

82 changes: 42 additions & 40 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,59 +1,61 @@
### Prerequisites
# Contributing to DISHA v5.0.0

- **Bun** 1.1+ (CLI runtime)
- **Node.js** 18+ (MCP server)
- **Python** 3.11+ (AI platform, decision engine, cyber defense)
- **Git**
First off, thank you for considering contributing to DISHA! It's people like you that make DISHA an elite tool for the AGI community.

### Setup
## 🌟 Code of Conduct

```bash
git clone https://github.com/Tashima-Tarsh/Disha.git
cd Disha
```
By participating in this project, you agree to abide by our [Code of Conduct](./CODE_OF_CONDUCT.md).

### MCP Server Development
## 🚀 Getting Started

```bash
cd mcp-server
npm install
npm run dev # Run with tsx (no build step)
npm run build # Compile to dist/
```
### Prerequisites
- **Bun** ≥ 1.1.0 (Primary runtime)
- **Python** ≥ 3.13 (AI & ML modules)
- **Node.js** ≥ 20 (Compatibility)
- **Docker** (For full ecosystem testing)
Comment on lines +11 to +15

@coderabbitai coderabbitai Bot Apr 15, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

**Python version mismatch between documentation and CI.**The documentation claims Python ≥ 3.13 as a prerequisite, but Python 3.14.0 was released on October 7, 2025, and Python 3.13.13 was released on April 7, 2026 — so Python 3.13 does exist. However, there's a mismatch: the CI workflow (.github/workflows/modules-ci.yml) uses Python 3.11, not 3.13.

Either update the CI to use Python 3.13+ or adjust this documentation to reflect the actual minimum version used in CI (Python 3.11).

✏️ Option A: Lower documented requirement to match CI 
 ### Prerequisites
 - **Bun** ≥ 1.1.0 (Primary runtime)
-- **Python** ≥ 3.13 (AI & ML modules)
+- **Python** ≥ 3.11 (AI & ML modules)
 - **Node.js** ≥ 20 (Compatibility)
✏️ Option B: Update CI to match documentation

Update .github/workflows/modules-ci.yml:

       - name: Set up Python
         uses: actions/setup-python@v5
         with:
-          python-version: "3.11"
+          python-version: "3.13"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### Prerequisites
- **Bun** ≥ 1.1.0 (Primary runtime)
- **Python** ≥ 3.13 (AI & ML modules)
- **Node.js** ≥ 20 (Compatibility)
- **Docker** (For full ecosystem testing)
### Prerequisites
- **Bun** ≥ 1.1.0 (Primary runtime)
- **Python** ≥ 3.11 (AI & ML modules)
- **Node.js** ≥ 20 (Compatibility)
- **Docker** (For full ecosystem testing)
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)

[warning] 11-11: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@CONTRIBUTING.md` around lines 11 - 15, Align the documented Python
requirement with the CI: either update the "Prerequisites" entry under the "###
Prerequisites" section in CONTRIBUTING.md (change "Python ≥ 3.13" to "Python ≥
3.11") or update the GitHub Actions workflow `.github/workflows/modules-ci.yml`
to use Python 3.13+ by changing the action's python-version/setup value (the
`python-version` key in the workflow) so the CI and the "Python ≥ 3.13" line in
CONTRIBUTING.md match.


### Setup
1. Fork the repository
2. Clone your fork: `git clone https://github.com/Tashima-Tarsh/Disha.git`
3. Install dependencies: `bun install`
4. Create a new branch: `git checkout -b feature/your-feature-name`

### Linting & Type Checking
## 🛠️ Development Workflow

### CLI Core (TypeScript)
The core engine is located in `src/`. We use **Biome** for linting and formatting.
```bash
# From the repo root — checks the src/
npm run lint # Biome lint
npm run typecheck # TypeScript type check
bun run lint # Check for issues
bun run format # Auto-format code
bun run build # Build the CLI bundle
```

### Python Modules

### AI Platforms (Python)
Each platform has its own `requirements.txt`.
```bash
# AI Platform
cd ai-platform/backend && pip install -r requirements.txt
# Example: AI Platform
cd ai-platform/backend
pip install -r requirements.txt
python -m pytest tests/
```

# Decision Engine (mock mode — no LLM needed)
cd decision-engine && pip install -r requirements.txt
DISHA_MODEL_PROVIDER=mock python -m pytest tests/ -v
## 📐 Coding Standards

# Cyber Defense
cd cyber-defense && pip install torch --index-url https://download.pytorch.org/whl/cpu
```
- **TypeScript:** Strict mode, ES Modules, descriptive naming.
- **Python:** PEP 8, 120 char line limit, docstrings for all public classes/methods.
- **CSS:** Tailwind CSS utility-first approach with semantic HSL tokens.

## Code Style
## 📬 Pull Request Process

For any new code (MCP server, tooling, scripts):
1. Ensure your code passes all linting and tests.
2. Update the README or documentation if you've added new features.
3. Submit the PR with a clear description of the "What" and the "Why".
4. One of the maintainers (Tashima Tarsh) will review your PR within 48 hours.

- TypeScript with strict mode
- ES modules
- 2-space indentation (tabs for `src/` to match Biome config)
- Descriptive variable names, minimal comments
- Python: PEP 8, max line length 120, flake8 for linting
## 💎 Reporting Bugs & Suggestions

Please use [GitHub Issues](https://github.com/Tashima-Tarsh/Disha/issues) to report bugs or suggest new features. For security-related reports, please see our [Security Policy](./SECURITY.md).

## Questions?
---

Open an issue at https://github.com/Tashima-Tarsh/Disha/issues
<sub>Dedicated to the evolution of digital thought.</sub>
Loading
Loading