Skip to main content

Version History

Mega Brain uses Semantic Versioning: MAJOR.MINOR.PATCH
  • MAJOR: Breaking changes
  • MINOR: New features (backward compatible)
  • PATCH: Bug fixes and improvements

[1.3.0] - Current Release

Latest Version

Status: StableRelease Date: March 2026Highlights: Production-ready release with enhanced stability, documentation, and developer experience.

Features

Core System:
  • AI-powered knowledge management system
  • Transform expert materials into structured playbooks and DNA schemas
  • 5-layer DNA extraction (Philosophies, Mental Models, Heuristics, Frameworks, Methodologies)
  • Full source traceability for all extracted knowledge
Pipeline Processing:
  • 5-phase pipeline (Chunking, Resolution, Extraction, Synthesis, Compilation)
  • Support for videos, PDFs, transcriptions, podcasts, training courses
  • Batch processing capabilities
  • Automated quality validation
AI Agents:
  • Mind clone framework for expert replication
  • Cargo agent system (29 functional role agents)
  • Conclave multi-agent deliberation
  • JARVIS orchestrator system
Developer Experience:
  • 20+ hooks for automation and validation
  • Skill system with keyword-based auto-routing
  • Slash commands for common operations
  • Session persistence with auto-save and resume
  • Interactive setup wizard
CLI Tools:
  • npx mega-brain-ai setup - Environment setup wizard
  • Layer validation tools
  • Pre-publish security gates
  • Package validation utilities

Commands Available

CommandDescription
/jarvis-briefingSystem status and health score
/jarvis-fullFull pipeline (ingest + process + enrich)
/process-jarvisRun 5-phase processing pipeline
/conclaveMulti-agent deliberation session
/ingestIngest new material
/saveSave current session
/resumeResume previous session
/setupEnvironment setup wizard

Architecture

Layer Distribution:
  • L1 (Community): Core engine, templates, hooks, skills, CLI
  • L2 (Pro): Populated knowledge base, mind clones, pipeline
  • L3 (Personal): User materials, sessions, environment config
Directory Structure:
mega-brain/
├── core/           -> Processing engine
├── agents/         -> AI agent definitions
├── .claude/        -> Claude Code integration
├── bin/            -> CLI tools
├── knowledge/      -> Knowledge base
├── artifacts/      -> Pipeline stages
├── inbox/          -> Raw materials
├── docs/           -> Documentation
└── logs/           -> Session logs

Prerequisites

RequirementVersionPurpose
Claude CodeMax or Pro planCore runtime
Node.js>= 18.0.0CLI and tooling
Python>= 3.10Intelligence scripts

API Keys

KeyPurposeRequired
OPENAI_API_KEYWhisper transcriptionYes
VOYAGE_API_KEYSemantic embeddingsRecommended
GOOGLE_CLIENT_IDGoogle Drive importOptional

Package Contents

Included in npm package:
  • Core processing engine
  • Task system with HO-TP-001 anatomy
  • Workflow orchestration (YAML)
  • Intelligence scripts (Python)
  • Protocol definitions
  • JSON schemas
  • Agent templates
  • Hook system
  • Skill framework
  • CLI tools
  • Documentation
Dependencies:
{
  "chalk": "^5.3.0",
  "inquirer": "^9.2.0",
  "ora": "^7.0.0",
  "boxen": "^7.1.0",
  "gradient-string": "^2.0.2"
}

Known Issues

Some scripts may have issues with Windows backslash paths. Use forward slashes or pathlib.Path for cross-platform compatibility.
Files over 2GB may need to be split for optimal processing due to API limits.

[1.0.0] - Initial Release

Foundation Release

Release Date: February 2026Highlights: First production release with core architecture and task system.

Added

Task System:
  • Task template (HO-TP-001 anatomy)
  • TASK-REGISTRY.md with categories and dependency graph
  • Foundation tasks (detect-role, normalize-entities)
  • Intelligence tasks (analyze-themes, detect-business-model, score-viability)
  • Extraction tasks (extract-dna, extract-knowledge, generate-skill)
  • Pipeline tasks (process-batch, trigger-agent, trigger-dossier)
  • Validation tasks (validate-cascade, verify-completeness)
Structure:
core/tasks/
├── _templates/
│   └── task-tmpl.md
├── TASK-REGISTRY.md
├── CHANGELOG.md
├── detect-role.md
├── normalize-entities.md
├── analyze-themes.md
├── extract-dna.md
├── process-batch.md
└── validate-cascade.md

Conventions

Version Format:
  • MAJOR: Breaking changes in task anatomy
  • MINOR: New tasks added
  • PATCH: Fixes in existing tasks
Change Types:
  • Added: New task created
  • Changed: Task modified (inputs/outputs/logic)
  • Deprecated: Task marked for removal
  • Removed: Task removed
  • Fixed: Bug fix in task
  • Security: Vulnerability corrected

Upgrade Guide

Breaking Changes: NoneSteps:
  1. Update package:
    npm update mega-brain-ai
    
  2. Review new features in this changelog
  3. Restart Claude Code to load new hooks and skills
  4. Run system check:
    /jarvis-briefing
    
Data Migration: Not required - all personal data (L3) remains compatible
No breaking changes:
  • All L3 (Personal) data preserved
  • .env configuration carries over
  • Custom hooks and skills remain functional
What you get:
  • Pre-built mind clones (5 experts)
  • Cargo agents (29 roles)
  • Populated knowledge base
  • Full pipeline capabilities
  • Enhanced Conclave
Steps:
  1. Contact @thiagofinch for Pro access
  2. Follow upgrade instructions provided
  3. No data migration needed
Community customizations remain intact and work alongside Pro features.

Release Notes Format

Each release includes:

What's New

  • New features and capabilities
  • New commands or tools
  • Architecture improvements

Improvements

  • Performance enhancements
  • Developer experience updates
  • Documentation additions

Bug Fixes

  • Resolved issues
  • Stability improvements
  • Edge case handling

Breaking Changes

  • API changes
  • Migration requirements
  • Deprecated features

Roadmap

In Development:
  • Enhanced RAG capabilities
  • Additional pre-built mind clones
  • Real-time collaboration features
  • Advanced search and filtering
  • Performance optimizations
Under Consideration:
  • Web interface for non-CLI users
  • Mobile companion app
  • Team collaboration features
  • Cloud sync options
  • API for third-party integrations
Roadmap is subject to change based on community feedback and priorities.
Feature Request Process:
  1. Check existing GitHub issues for similar requests
  2. Open new issue with:
    • Clear use case description
    • Problem you’re trying to solve
    • Proposed solution (optional)
    • Examples or mockups (if applicable)
  3. Engage with community discussion
  4. Maintainer will review and prioritize
Priority Factors:
  • User impact and demand
  • Alignment with project vision
  • Implementation complexity
  • Available resources

Security Updates

Security Policy:
  • Security issues are addressed with highest priority
  • Patches released as soon as possible
  • Users notified via GitHub security advisories
  • Severity levels: Critical, High, Medium, Low

Reporting Security Issues

If you discover a security vulnerability:
  1. Do NOT open a public issue
  2. Contact @thiagofinch directly
  3. Provide:
    • Description of vulnerability
    • Steps to reproduce
    • Potential impact
    • Suggested fix (if any)
  4. Allow time for patch development
  5. Coordinate disclosure timing

Contributing to Releases

Maintained by: @thiagofinch (exclusive)Process:
  1. Feature development on branches
  2. PR review and approval
  3. Merge to main
  4. Version bump (semantic versioning)
  5. Update changelog
  6. Run validation:
    npm run validate:layers
    node bin/pre-publish-gate.js
    
  7. Publish to npm
  8. Create GitHub release
  9. Announce to community
Only the maintainer can publish official releases.

Version Support

VersionStatusSupportEnd of Life
1.3.xCurrent✅ Full support-
1.0.xMaintenance⚠️ Security onlyQ4 2026
< 1.0Deprecated❌ No supportEnded
Always use the latest stable version for best performance and security.

Changelog Policy

This changelog follows Keep a Changelog principles:
  • Changes are grouped by type (Added, Changed, Deprecated, Removed, Fixed, Security)
  • Versions use semantic versioning
  • Release dates are included
  • Breaking changes are clearly marked
  • Migration guides provided when needed

Stay Updated

Subscribe to updates:
  • Watch the GitHub repository
  • Star for notifications
  • Follow @thiagofinch
  • Check this changelog regularly

Build docs developers (and LLMs) love