Skip to main content

Changelog

All notable changes to the Kai project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Unreleased

Added

  • MoodBoard feature with public/private settings and dedicated pages
  • Comprehensive subscription management with Stripe integration
  • Tile property categorization with inheritance systems
  • Intelligent recommendation engines for material suggestions
  • Material Comparison and Analytics engines with similarity scores
  • Property Relationship Graph for enhanced AI model training
  • Credit system for factories to promote materials in 3D model generation
  • Admin panel for managing prompts with versioning and success tracking

Changed

  • Enhanced documentation system with Docusaurus 3.7
  • Improved deployment process with GitHub Actions
  • Updated ML models for better material recognition

Fixed

  • Resolved issues with PDF processing pipeline
  • Fixed authentication flow for multiple user types
  • Improved error handling in the API server

0.1.0 - 2023-12-15

Added

  • Initial release of Kai platform
  • Material Recognition System with multi-strategy recognition
  • Knowledge Base System for material information storage
  • 3D Visualization System with ThreeJS integration
  • Machine Learning Infrastructure with Model Context Protocol (MCP) Server
  • PDF Processing capabilities for catalog extraction
  • Neural OCR Integration for advanced document understanding
  • Queue System for asynchronous processing
  • CrewAI Integration for intelligent agent capabilities
  • Basic authentication system with multiple user roles
  • Initial API endpoints for material management
  • Frontend client application with Gatsby
  • Admin panel with Next.js
  • Documentation system in the /readme/ folder

Changed

  • N/A (Initial release)

Fixed

  • N/A (Initial release)

Removed

  • N/A (Initial release)

Types of changes

  • Added for new features.
  • Changed for changes in existing functionality.
  • Deprecated for soon-to-be removed features.
  • Removed for now removed features.
  • Fixed for any bug fixes.
  • Security in case of vulnerabilities.

How to update this changelog

  1. Add a new version section at the top under Unreleased when releasing a new version
  2. Document all notable changes since the previous release under appropriate categories
  3. Move items from Unreleased to the new version section
  4. Add the release date in YYYY-MM-DD format