๐ฅ Black Trigram โ End-of-Life Strategy
๐ก๏ธ Proactive Technology Lifecycle Management for Frontend Gaming Platform
๐ฆ Current Stack Maintenance โข ๐ Node.js Lifecycle Evolution โข โก Future-Ready Architecture
**๐ Document Owner:** CEO | **๐ Version:** 1.2 | **๐
Last Updated:** 2026-04-21 (UTC)
**๐ Review Cycle:** Annual | **โฐ Next Review:** 2027-04-21
**๐ท๏ธ Classification:** Public (Frontend-Only Educational Gaming Platform)
---
## ๐ฏ EOL Strategy Overview
### **๐ Strategic Objective**
**Black Trigram** will maintain its current frontend-only technology stack, utilizing modern web technologies and React 19 ecosystem, without requiring backend infrastructure migration. The project will reach EOL when compatibility with the latest browser runtimes or critical dependency security support requires architectural migration beyond cost-effective maintenance.
This strategy aligns with [Hack23 AB's Vulnerability Management Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Vulnerability_Management.md) **"Living on the Edge"** philosophy - maintaining latest stable releases with comprehensive automated testing and security validation.
### **๐ท๏ธ Business Impact Classification**
Based on [Hack23 AB Classification Framework](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md):
| Security Dimension | Level | EOL Impact | Business Rationale |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | ---------------------------------------------------------------------- |
| **๐ Confidentiality** | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#confidentiality-levels) | Low | Open source educational content, no sensitive data |
| **๐ Integrity** | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#integrity-levels) | Medium | Educational content accuracy critical for Korean cultural authenticity |
| **โก Availability** | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#availability-levels) | Medium | Educational gaming platform; tolerates maintenance windows |
**๐ฏ RTO/RPO Alignment:** Medium RTO (4-24hrs), Daily RPO acceptable for educational content platform
---
## ๐ฆ Current Technology Stack Analysis
### **๐๏ธ Core Technology Matrix**
```mermaid
%%{
init: {
'theme': 'base',
'themeVariables': {
'primaryColor': '#e8f5e9',
'primaryTextColor': '#2e7d32',
'lineColor': '#4caf50',
'secondaryColor': '#fff3e0',
'tertiaryColor': '#e3f2fd'
}
}
}%%
mindmap
root)๐ฅ Black Trigram Stack(
(๐ฅ๏ธ Runtime)
โ Node.js 25.x
๐
CI Runtime Baseline - transitioning to 26.x LTS
โฐ Lifecycle source - Node.js release schedule
๐ LTS migration track - 24.x and 26.x
๐ข New schedule from 27.x
๐ Prepared for Node 26 LTS upgrade
๐ Browser Runtime
๐
Evergreen Updates
โฐ EOL N/A - Auto-update
๐ WebGL/WebAssembly Support
(โ๏ธ Frontend Framework)
๐ฆ React 19.2.x
๐
Current Latest
โฐ EOL ~2027-2028
๐ Concurrent Features
๐ฎ Three.js 0.184.x / R3F 9.6.x
๐
Current Latest
โฐ EOL Active development
๐ WebGL 2.0 + WebGPU Support
๐ฑ Internal ErrorBoundary Component
๐
Current In-repo component
โฐ EOL React-dependent
๐ Error Handling
(๐ ๏ธ Build and Tooling)
โก Vite 8.x
๐
Current Latest
โฐ EOL Active yearly
๐ ESBuild Integration
๐ TypeScript 6.x
๐
Current Latest
โฐ EOL ~6-month cycles
๐ Strict Mode Enabled
๐ ESLint 9.x
๐
Current Latest
โฐ EOL Active
๐ Flat Config System
(๐ต Audio and Assets)
๐ต Internal Web Audio System
๐
Current In-repo implementation
โฐ EOL Browser Web Audio API dependent
๐ Web Audio API
๐จ @react-three/drei 10.7.x
๐
Current Latest
โฐ EOL R3F-dependent
๐ 3D Helpers and Audio
(๐งช Testing and Quality)
๐งช Vitest 4.x
๐
Current Latest
โฐ EOL Active
๐ Native ESM Support
๐ง Cypress 15.x
๐
Current Latest
โฐ EOL Active
๐ E2E Testing
```
### **๐ Technology Lifecycle Overview**
| **Technology Category** | **Current Version** | **Release Model** | **EOL Timeline** | **Migration Complexity** |
| ----------------------- | ------------------------- | ------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **โ๏ธ React Framework** | 19.2.5 (Latest) | Major annually, Minor quarterly | ~2027-2028 | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
| **๐ฎ Three.js / R3F** | 0.184.0 / 9.6.0 (Latest) | Major annually, Patch monthly | Active development | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
| **โก Vite Build Tool** | 8.0.9 (Latest) | Major annually | Active development | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
| **๐ TypeScript** | 6.0.3 (Latest) | Major every ~12 months | Active development | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
| **โ Node.js Runtime** | 25.x (CI); 26.x LTS (target) | Major every 6 months; even-numbered majors LTS | LTS 24.x: **Apr 2027**; LTS 26.x: **Apr 2028** | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
| **๐งช Testing Stack** | Vitest 4.1.4 + Cypress 15.14.0 | Major annually | Active development | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
---
## โ Node.js Release Schedule Evolution & Transition Strategy
### **๐ข Node.js Release Schedule Change โ Alpha From Oct 2026, Annual Major From Apr 2027**
Starting with **Node.js 27.x**, the Node.js project is [evolving its release schedule](https://nodejs.org/en/blog/announcements/evolving-the-nodejs-release-schedule) from **two major releases per year** to **one major release per year**. The new model introduces a **6โmonth alpha phase beginning in October 2026** and moves to **a single stable major release each April starting in April 2027**. This change, discussed in [nodejs/Release#1113](https://github.com/nodejs/Release/issues/1113), has significant implications for Black Trigram's lifecycle planning.
#### **๐ Key Changes Summary**
| Aspect | Old Model (โค26.x) | New Model (27.x+) |
| ------ | ------------------ | ------------------ |
| **Major releases/year** | 2 (April + October) | 1 stable major/year (April; first in Apr 2027) |
| **LTS eligibility** | Even-numbered only | Every release |
| **Odd/even distinction** | Yes (odd = Current only) | No โ all releases become LTS |
| **Alpha channel** | None | 6-month alpha (OctโMar, starting Oct 2026) with semver-major changes |
| **Alpha versioning** | N/A | Semver prerelease (e.g., `27.0.0-alpha.1`); alpha for year N+1's major starts Oct of year N |
| **Version numbering** | Sequential | Calendar-aligned stable release (27 ships Apr 2027, 28 ships Apr 2028); alpha prereleases begin the prior October |
| **LTS support window (from LTS start to EOL)** | 30 months | 30 months (unchanged; still ~36 months total including 6 months Current + 30 months LTS) |
#### **๐ New Node.js Release Lifecycle Phases**
| Phase | Duration | Description |
| ----- | -------- | ----------- |
| **Alpha** | 6 months (OctโMar) | Early testing, semver-major changes allowed |
| **Current** | 6 months (AprโOct) | Stabilization period |
| **LTS** | 30 months | Long-term support with security fixes |
| **EOL** | โ | No further support provided |
#### **๐ฏ Impact on Black Trigram**
- **โ
Simplified planning:** Every release becomes LTS โ no need to skip odd-numbered versions
- **โ
Predictable upgrades:** One major version per year, calendar-aligned
- **โ
Earlier testing:** Alpha channel enables integration testing 6 months before release
- **๐ Action required:** Integrate Node.js Alpha releases into CI as early as possible to report bugs before they affect users
- **๐ Library authors note:** Testing only on LTS releases means bugs cannot be reported before they affect users
### **๐ฏ Strategic Node.js Lifecycle Management**
Following [Hack23 AB's Proactive Runtime Management](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Vulnerability_Management.md#proactive-runtime--operations-management), Black Trigram implements a **current-version-first** approach for optimal security and performance.
```mermaid
%%{init: {'theme':'base', 'themeVariables': {'primaryColor':'#2979FF','primaryTextColor':'#fff','primaryBorderColor':'#0D47A1','lineColor':'#455A64','secondaryColor':'#4CAF50','tertiaryColor':'#FF9800','taskBkgColor':'#2979FF','taskTextColor':'#fff','taskTextDarkColor':'#fff','taskTextOutsideColor':'#000','activeTaskBkgColor':'#00C853','activeTaskBorderColor':'#00796B','doneTaskBkgColor':'#4CAF50','doneTaskBorderColor':'#2E7D32','critBkgColor':'#D32F2F','critBorderColor':'#B71C1C'}}}%%
gantt
title Node.js Lifecycle & Black Trigram Transition Timeline (Updated Schedule)
dateFormat YYYY-MM-DD
axisFormat %Y-%m
section Node.js Old Schedule (โค26.x)
Node.js 24.x LTS :active, node24lts, 2024-10-29, 2027-04-30
Node.js 25.x Current :done, node25c, 2025-04-22, 2025-10-21
Node.js 26.x Current :active, node26c, 2025-10-21, 2026-04-01
Node.js 26.x LTS :node26lts, 2026-04-01, 2028-04-30
Node.js 24.x EOL :crit, node24eol, 2027-04-30, 0d
Node.js 25.x EOL :crit, node25eol, 2025-10-21, 0d
Node.js 26.x EOL :crit, node26eol, 2028-04-30, 0d
section Node.js New Schedule (27.x+, approximate)
Node.js 27.x Alpha :node27a, 2026-10-01, 2027-03-31
Node.js 27.x Current :node27c, 2027-04-01, 2027-09-30
Node.js 27.x LTS :node27lts, 2027-10-01, 2030-04-30
Node.js 28.x Alpha :node28a, 2027-10-01, 2028-03-31
Node.js 28.x Current :node28c, 2028-04-01, 2028-09-30
Node.js 28.x LTS :node28lts, 2028-10-01, 2031-04-30
section Black Trigram Strategy
Node 25.x CI Runtime (active baseline) :active, bt25prod, 2025-04-22, 2026-03-18
25.x โ 26.x LTS Migration :active, bt25mig, 2026-03-01, 2026-06-30
Node.js 26.x LTS Production :bt26prod, 2026-06-30, 2028-04-30
Node.js 27.x Alpha CI Testing :bt27alpha, 2026-10-01, 2027-03-31
Node.js 27.x Migration :bt27mig, 2027-04-01, 2027-09-30
Node.js 27.x Production :bt27prod, 2027-10-01, 2030-04-30
section Risk Management
26.x LTS Migration (Active) :active, upgrade26, 2026-03-01, 2026-06-30
26.x Compatibility Testing :compat26, 2026-03-01, 2026-06-30
27.x Alpha CI Integration :alphaci, 2026-10-01, 2027-04-01
27.x Migration Risk Assessment :milestone, riskassess27, 2027-03-01, 0d
```
### **๐ Node.js Transition Trigger Conditions**
#### **๐ข Proactive Migration Triggers (Preferred)**
1. **๐
Node.js Major Release Available:** Upgrade planned within 4 weeks of each stable release (see [official release schedule](https://github.com/nodejs/release#release-schedule))
2. **๐
Node.js LTS Promotion:** Transition to LTS for production stability once the release enters LTS phase
3. **๐
Node.js 27.x Alpha Release:** October 2026 - Begin CI integration testing (new schedule, first calendar-aligned release)
4. **๐ก๏ธ Security Feature Advantages:** Enhanced security features in newer Node.js releases
5. **โก Performance Improvements:** Significant V8 or runtime optimizations
6. **๐ฆ Ecosystem Compatibility:** Major dependencies requiring newer Node.js
#### **๐ก Risk-Based Migration Triggers (Monitored)**
1. **โฐ Node.js 25.x upstream EOL:** October 2025 (passed) โ Odd-numbered release, short upstream support window; migration to 26.x LTS is underway
2. **๐จ Security Support Concerns:** Security patch availability degradation
3. **๐ง Tooling Incompatibility:** Build/development tools requiring newer Node.js
4. **โ๏ธ Hosting Platform Changes:** Deployment platform Node.js requirements
#### **๐ด Critical Migration Triggers (Mandatory)**
1. **โ Node.js 25.x upstream EOL:** October 2025 (passed) โ Upstream support ended; 25.xโ26.x LTS migration actively in progress
2. **โ Node.js 24.x EOL:** April 2027 - End of security support for previous LTS
3. **๐จ Critical Vulnerability:** Unpatched security issues in current Node.js version
4. **๐ง Build System Incompatibility:** Essential tools no longer supporting current Node.js
5. **๐ Browser API Requirements:** New web standards requiring newer Node.js features
### **๐งช Node.js Migration Testing & Validation Strategy**
#### **๐ฌ Alpha Channel CI Integration (New Schedule 27.x+)**
With the new Node.js release schedule introducing a 6-month alpha phase, Black Trigram will integrate alpha releases into CI early to detect compatibility issues before they reach production:
1. **๐ค Automated Alpha Testing:** Add Node.js alpha to CI matrix (non-blocking) during alpha phase
2. **๐ Bug Reporting:** Report any issues discovered during alpha testing upstream to Node.js
3. **๐ Dependency Compatibility:** Validate all major dependencies against alpha releases
4. **๐ Performance Baselines:** Establish performance baselines during alpha for comparison
#### **๐ Migration Validation Flow**
```mermaid
%%{
init: {
'theme': 'base',
'themeVariables': {
'primaryColor': '#e3f2fd',
'primaryTextColor': '#01579b',
'lineColor': '#2196f3',
'secondaryColor': '#f1f8e9',
'tertiaryColor': '#fff8e1'
}
}
}%%
flowchart TB
subgraph PREPARATION["๐ฌ Pre-Migration Testing (Jun-Jul 2026)"]
COMPAT_TEST["๐งช Compatibility Testing
โข Vite 8+ compatibility
โข React 19 compatibility
โข Three.js / R3F compatibility
โข TypeScript 6+ compatibility"]
DEP_AUDIT["๐ฆ Dependency Audit
โข NPM package compatibility
โข Native module rebuilds
โข Security vulnerability scan
โข License compliance check"]
PERF_BASELINE["๐ Performance Baseline
โข Build time comparison
โข Runtime performance
โข Memory usage analysis
โข Bundle size impact"]
end
subgraph VALIDATION["โ
Migration Validation (Aug-Sep 2026)"]
FEATURE_TEST["๐ฎ Feature Testing
โข Combat system validation
โข Audio engine testing
โข Korean text rendering
โข Three.js 3D graphics performance"]
E2E_VALIDATION["๐ E2E Validation
โข Complete user journeys
โข Cross-browser testing
โข Mobile compatibility
โข Performance regression"]
SECURITY_SCAN["๐ Security Validation
โข Vulnerability scanning
โข Dependency security
โข Secret scanning
โข SLSA attestation"]
end
subgraph DEPLOYMENT["๐ Controlled Deployment (Oct 2026)"]
STAGING_DEPLOY["๐งช Staging Deployment
โข Node.js 26.x environment
โข Full test suite execution
โข Performance monitoring
โข Error tracking"]
CANARY_RELEASE["๐ฆ Canary Release
โข 10% traffic allocation
โข Performance monitoring
โข Error rate analysis
โข User feedback collection"]
FULL_MIGRATION["๐ฏ Full Migration
โข 100% Node.js 26.x
โข Legacy cleanup
โข Documentation update
โข Team notification"]
end
COMPAT_TEST --> DEP_AUDIT
DEP_AUDIT --> PERF_BASELINE
PERF_BASELINE --> FEATURE_TEST
FEATURE_TEST --> E2E_VALIDATION
E2E_VALIDATION --> SECURITY_SCAN
SECURITY_SCAN --> STAGING_DEPLOY
STAGING_DEPLOY --> CANARY_RELEASE
CANARY_RELEASE --> FULL_MIGRATION
style PREPARATION fill:#bbdefb
style VALIDATION fill:#c8e6c9
style DEPLOYMENT fill:#ffecb3
```
### **๐ Node.js Migration Risk Assessment**
| Risk Category | Probability | Impact | Mitigation Strategy | Success Criteria |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | --------------------------- |
| **๐ฆ Dependency Incompatibility** | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) | Early testing + dependency audit | All dependencies compatible |
| **โก Performance Regression** | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) | Performance benchmarking | <5% performance degradation |
| **๐ง Build System Changes** | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) | Vite + ESBuild compatibility testing | Build process unchanged |
| **๐ Runtime API Changes** | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) | API compatibility validation | All APIs function correctly |
| **๐ Security Control Impact** | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) | Security scanning + attestation | Security posture maintained |
---
## ๐ Ongoing Maintenance Strategy
### **๐ฆ Dependency Management Philosophy**
Aligned with [Hack23 AB's "Living on the Edge" Strategy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Vulnerability_Management.md#proactive-dependency-management-strategy):
#### **๐ Bleeding-Edge with Safety Controls**
- **๐ฆ Always Latest:** Accept Dependabot PRs for latest stable releases immediately
- **๐ก๏ธ Security Gates:** Automated testing and security validation before merge
- **๐ Dependency Review:** GitHub's Dependency Review Action with OpenSSF Scorecard integration
- **โ
Test-Driven Confidence:** Trust comprehensive test suites over manual review
- **๐จ Rapid Response:** <4 hours for critical security vulnerabilities
- **โฐ EOL Tracking:** Proactive monitoring of runtime and dependency lifecycles
### **๐ Automated Dependency Updates**
```mermaid
%%{
init: {
'theme': 'base',
'themeVariables': {
'primaryColor': '#f3e5f5',
'primaryTextColor': '#6a1b9a',
'lineColor': '#ba68c8',
'secondaryColor': '#e8f5e9',
'tertiaryColor': '#fff3e0'
}
}
}%%
flowchart LR
subgraph MONITORING["๐ Daily Monitoring (09:00 CET)"]
DEPENDABOT["๐ค Dependabot Scanning
โข NPM security advisories
โข Version compatibility
โข License compliance
โข OpenSSF Scorecard"]
SECURITY_SCAN["๐ Security Scanning
โข GitHub Security Advisories
โข CVE database updates
โข Supply chain analysis
โข Vulnerability assessment"]
end
subgraph VALIDATION["โ
Automated Validation"]
QUALITY_GATES["๐ก๏ธ Quality Gates
โข Unit tests (>80% coverage)
โข E2E tests (critical paths)
โข Security scans (SAST/SCA)
โข Performance budgets"]
REVIEW_ACTION["๐ Dependency Review
โข License compatibility
โข Vulnerability check
โข Supply chain security
โข Breaking change analysis"]
end
subgraph DEPLOYMENT["๐ Auto-Deployment"]
AUTO_MERGE["๐ Auto-Merge Logic
โข Security patches: <2 hours
โข Minor updates: <8 hours
โข Major updates: <24 hours
โข Manual review if needed"]
ROLLBACK["โฉ๏ธ Automated Rollback
โข Test failure detection
โข Performance regression
โข Security scan failure
โข Build errors"]
end
DEPENDABOT --> QUALITY_GATES
SECURITY_SCAN --> REVIEW_ACTION
QUALITY_GATES --> AUTO_MERGE
REVIEW_ACTION --> AUTO_MERGE
AUTO_MERGE --> ROLLBACK
style MONITORING fill:#e1bee7
style VALIDATION fill:#c8e6c9
style DEPLOYMENT fill:#ffecb3
```
### **๐ Update Classification & Response Times**
| Update Type | Response Time | Security Gate | Merge Strategy | EOL Consideration |
| ----------------------- | ------------- | ------------------------- | -------------------- | ---------------------------------- |
| **๐ด Security Patches** | <4 hours | Dependency Review + Tests | Auto-merge on green | Immediate regardless of EOL |
| **๐ Major Releases** | <24 hours | Full test suite + review | Auto-merge on green | Check EOL timeline alignment |
| **๐ก Minor Releases** | <8 hours | Standard testing | Auto-merge on green | Prefer LTS versions |
| **๐ข Patch Releases** | <2 hours | Basic validation | Immediate auto-merge | Always apply within support window |
---
## โฐ End-of-Life Tracking & Monitoring
### **๐ Technology EOL Dashboard**
Real-time monitoring using [endoflife.date](https://endoflife.date/) references and automated tracking:
```mermaid
%%{init: {'theme':'base', 'themeVariables': {'primaryColor':'#2979FF','primaryTextColor':'#fff','primaryBorderColor':'#0D47A1','lineColor':'#455A64','secondaryColor':'#4CAF50','tertiaryColor':'#FF9800','taskBkgColor':'#2979FF','taskTextColor':'#fff','taskTextDarkColor':'#fff','taskTextOutsideColor':'#000','activeTaskBkgColor':'#00C853','activeTaskBorderColor':'#00796B','doneTaskBkgColor':'#4CAF50','doneTaskBorderColor':'#2E7D32','critBkgColor':'#D32F2F','critBorderColor':'#B71C1C'}}}%%
gantt
title Black Trigram Technology End-of-Life Timeline (2025-2031)
dateFormat YYYY-MM-DD
axisFormat %Y
section Runtime and Core
Node.js 24.x LTS :active, node24, 2024-10-29, 2027-04-30
Node.js 25.x Current (historical track) :done, node25, 2025-04-22, 2025-10-21
Node.js 26.x LTS (Target) :node26, 2025-10-28, 2028-04-30
Node.js 27.x LTS (New Schedule) :node27, 2027-10-01, 2030-04-30
Node.js 28.x LTS (New Schedule) :node28, 2028-10-01, 2031-04-30
section Frontend Framework
React 19.x :active, react19, 2024-12-05, 2027-12-31
React 20.x (Future) :react20, 2025-12-01, 2028-12-31
React 21.x (Future) :react21, 2026-12-01, 2029-12-31
section Build and Tooling
Vite 8.x :active, vite8, 2025-06-01, 2026-12-31
Vite 9.x (Future) :vite9, 2026-06-01, 2027-12-31
TypeScript 5.x :done, ts5, 2024-03-16, 2025-09-30
TypeScript 6.x :active, ts6, 2026-03-01, 2027-03-31
section Graphics and Audio
Three.js 0.183.x :active, three, 2024-01-01, 2026-12-31
@react-three/fiber 9.x :active, r3f9, 2024-06-01, 2027-06-01
section Critical Milestones
Node.js 25 โ 26 Upgrade :milestone, node25upgrade, 2026-04-01, 0d
Node.js 24 Migration Alert :milestone, node24alert, 2026-04-30, 0d
React 19 Assessment :milestone, react19assess, 2026-12-01, 0d
Major Stack Review :milestone, stackreview, 2027-01-01, 0d
```
### **๐จ EOL Warning System**
#### **๐ Automated EOL Monitoring**
- **โฐ 24-Month Early Warning:** Initial migration planning phase
- **โ ๏ธ 18-Month Alert:** Active migration preparation required
- **๐จ 12-Month Critical:** Migration implementation must begin
- **โ 6-Month Emergency:** Final migration deadline approach
- **๐ด EOL Reached:** Immediate security risk assessment required
#### **๐ EOL Response Procedures**
| Warning Level | Timeline | Actions Required | Escalation |
| --------------------- | ---------- | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **๐ข Early Warning** | 24+ months | Technology assessment, alternative evaluation | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
| **๐ก Planning Phase** | 18+ months | Migration strategy development, testing plan | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
| **๐ Implementation** | 12+ months | Active migration, compatibility testing | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
| **๐ด Critical Phase** | 6+ months | Final testing, production migration | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
| **โ Emergency** | <6 months | Security assessment, risk acceptance | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
---
## ๐ฏ Final EOL Conditions
### **๐ Project Retirement Triggers**
Black Trigram will be designated as EOL and archived in read-only state when ANY of these conditions occur:
#### **๐ด Critical EOL Triggers (Immediate Retirement)**
1. **๐จ Security Support Failure:** No security patches available for critical vulnerabilities in core dependencies
2. **๐ Browser Compatibility Loss:** Modern browsers no longer support required WebGL/Canvas APIs
3. **โก Performance Degradation:** Framework limitations causing <30fps on target hardware
4. **๐ฆ Dependency Chain Collapse:** Critical dependencies (React, Three.js/R3F, Vite) all reach EOL simultaneously
#### **๐ Business EOL Triggers (Planned Retirement)**
1. **๐ฐ Maintenance Cost Exceeds Value:** Security maintenance costs exceed educational value delivery
2. **๐ Technology Replacement:** Superior educational gaming platform technology becomes available
3. **๐ Compliance Requirements:** New regulations incompatible with frontend-only architecture
4. **๐ฏ Mission Completion:** Educational objectives fully achieved through other means
#### **๐ก Technical EOL Triggers (Migration Required)**
1. **โ Node.js Ecosystem End:** Node.js 27+ unsupported and current LTS EOL reached
2. **โ๏ธ React Major Breaking Change:** React 20+ incompatible with current Three.js/R3F integration
3. **๐ฎ Three.js Architecture Change:** WebGPU transition requiring significant refactoring
4. **๐ง Build System Evolution:** ES Modules/Import Maps requiring Vite replacement
### **๐ EOL Decision Matrix**
```mermaid
%%{
init: {
'theme': 'base',
'themeVariables': {
'primaryColor': '#ffcdd2',
'primaryTextColor': '#c62828',
'lineColor': '#f44336',
'secondaryColor': '#fff3e0',
'tertiaryColor': '#e8f5e9'
}
}
}%%
flowchart TD
START[๐ฏ EOL Assessment Trigger] --> SECURITY{๐ Security Support Available?}
SECURITY -->|โ No| CRITICAL[๐จ Critical EOL
Immediate Retirement]
SECURITY -->|โ
Yes| BROWSER{๐ Browser Compatibility OK?}
BROWSER -->|โ No| CRITICAL
BROWSER -->|โ
Yes| PERFORMANCE{โก Performance Acceptable?}
PERFORMANCE -->|โ No| CRITICAL
PERFORMANCE -->|โ
Yes| MAINTENANCE{๐ฐ Maintenance Cost Reasonable?}
MAINTENANCE -->|โ No| BUSINESS[๐ Business EOL
Planned Retirement]
MAINTENANCE -->|โ
Yes| COMPLIANCE{๐ Compliant with Regulations?}
COMPLIANCE -->|โ No| BUSINESS
COMPLIANCE -->|โ
Yes| MIGRATION{๐ Migration Required?}
MIGRATION -->|๐ด Critical| TECHNICAL[๐ก Technical EOL
Migration Required]
MIGRATION -->|๐ข Manageable| CONTINUE[โ
Continue Maintenance
Monitor EOL Triggers]
CRITICAL --> ARCHIVE[๐ฆ Archive Repository
Read-Only State]
BUSINESS --> MIGRATE_OR_ARCHIVE{๐ค Migration Feasible?}
TECHNICAL --> PLAN_MIGRATION[๐ Plan Migration
To Modern Stack]
MIGRATE_OR_ARCHIVE -->|โ No| ARCHIVE
MIGRATE_OR_ARCHIVE -->|โ
Yes| PLAN_MIGRATION
PLAN_MIGRATION --> NEW_PLATFORM[๐ New Platform Development
Modern Technology Stack]
style CRITICAL fill:#ffcdd2,stroke:#d32f2f
style BUSINESS fill:#fff3e0,stroke:#f57c00
style TECHNICAL fill:#fff9c4,stroke:#fbc02d
style CONTINUE fill:#c8e6c9,stroke:#388e3c
style ARCHIVE fill:#f3e5f5,stroke:#7b1fa2
```
---
## ๐ Technology Succession Planning
### **๐ Future Platform Vision**
Should EOL conditions trigger migration, the successor platform will maintain **Korean martial arts educational integrity** while leveraging modern technology:
#### **๐ Next-Generation Technology Candidates**
| Component | Current (Black Trigram) | Future Candidate | Migration Complexity |
| ------------------------- | ----------------------- | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **โ๏ธ Frontend Framework** | React 19 + Three.js/R3F | React 22+ or Svelte 5+ with WebGPU | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
| **๐ฎ Graphics Engine** | Three.js WebGL 2.0 | Three.js WebGPU or native WebGPU | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
| **๐ ๏ธ Build System** | Vite 8 + ESBuild | Rolldown, Turbopack, or Vite Next | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
| **๐ฑ Platform Target** | Web-only | Progressive Web App + WebAssembly | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
| **โ Runtime** | Node.js (build only) | Node.js 27+, Deno, Bun, or Next-gen | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) |
#### **๐ฏ Migration Success Criteria**
- **๐ฐ๐ท Cultural Authenticity Preserved:** Korean martial arts content maintained exactly
- **๐ฎ Educational Value Enhanced:** Improved learning effectiveness and engagement
- **๐ก๏ธ Security Posture Improved:** Better security controls and vulnerability management
- **โก Performance Gains:** >60fps on target hardware with better accessibility
- **๐ฆ Maintenance Simplified:** Reduced complexity and better long-term support
### **๐ Technology Investment Strategy**
```mermaid
%%{init: {
"theme": "neutral",
"themeVariables": {
"quadrant1Fill": "#2E7D32",
"quadrant2Fill": "#D32F2F",
"quadrant3Fill": "#1565C0",
"quadrant4Fill": "#FF9800",
"quadrantTitleFill": "#ffffff",
"quadrantPointFill": "#ffffff",
"quadrantPointTextFill": "#ffffff",
"quadrantXAxisTextFill": "#ffffff",
"quadrantYAxisTextFill": "#ffffff"
}
}}%%
quadrantChart
title ๐ฏ Technology Investment vs Migration Complexity
x-axis Low Migration Complexity --> High Migration Complexity
y-axis Low Strategic Value --> High Strategic Value
quadrant-1 Research & Prototype
quadrant-2 Priority Investment
quadrant-3 Maintain Current
quadrant-4 Evaluate Alternatives
Node.js Runtime Upgrade: [0.3, 0.8]
React Framework Upgrade: [0.4, 0.9]
Three.js WebGPU Migration: [0.9, 0.9]
Build System Modernization: [0.5, 0.6]
TypeScript Latest: [0.2, 0.7]
Testing Framework Update: [0.4, 0.5]
Audio Engine Upgrade: [0.3, 0.4]
PWA Implementation: [0.7, 0.8]
```
---
## ๐ Compliance & Documentation
### **๐ Required Documentation Maintenance**
Per [Hack23 AB Secure Development Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Secure_Development_Policy.md), all EOL planning must maintain:
#### **๐ Architecture Documentation**
- **๐๏ธ [ARCHITECTURE.md](ARCHITECTURE.md)** โ Current system design with EOL considerations
- **๐ [FUTURE_ARCHITECTURE.md](FUTURE_ARCHITECTURE.md)** โ Migration path and next-generation vision
- **๐ก๏ธ [SECURITY_ARCHITECTURE.md](SECURITY_ARCHITECTURE.md)** โ Security controls aligned with EOL timeline
- **๐ [WORKFLOWS.md](WORKFLOWS.md)** โ CI/CD processes adapted for EOL management
#### **๐ Testing & Quality Assurance**
- **๐งช [UnitTestPlan.md](UnitTestPlan.md)** โ Test coverage for legacy compatibility
- **๐ [E2ETestPlan.md](E2ETestPlan.md)** โ End-to-end validation through EOL transitions
- **โก [performance-testing.md](performance-testing.md)** โ Performance benchmarks for EOL decisions
#### **๐ Business & Strategic Documentation**
- **๐ง [MINDMAP.md](MINDMAP.md)** โ System relationships and EOL impact analysis
- **๐ผ [SWOT.md](SWOT.md)** โ Strategic assessment including EOL risks and opportunities
- **๐ [FLOWCHART.md](FLOWCHART.md)** โ Process flows adapted for EOL scenarios
### **๐๏ธ Security & Compliance Badges**
EOL strategy compliance demonstrated through continuous monitoring:
[](https://scorecard.dev/viewer/?uri=github.com/Hack23/blacktrigram)
[](https://github.com/Hack23/blacktrigram/attestations)
[](https://sonarcloud.io/summary/new_code?id=Hack23_blacktrigram)
[](https://bestpractices.coreinfrastructure.org/projects/10777)
---
## ๐ Monitoring & Alerting Framework
### **๐ Continuous EOL Monitoring**
Integration with [Hack23 AB Security Metrics](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Security_Metrics.md) for proactive EOL management:
#### **๐ Key EOL Metrics**
- **โฐ Days Until EOL:** Automated countdown for all critical dependencies
- **๐ก๏ธ Security Patch Availability:** Response time and availability tracking
- **๐ฆ Dependency Health Score:** OpenSSF Scorecard and vulnerability status
- **โก Performance Regression Tracking:** Automated benchmark comparison
- **๐ฐ Maintenance Cost Trending:** Development effort and resource allocation
#### **๐จ Alerting Thresholds**
- **๐ด Critical (0-6 months to EOL):** Daily alerts to CEO and development team
- **๐ High (6-12 months to EOL):** Weekly status reports and planning meetings
- **๐ก Medium (12-18 months to EOL):** Monthly reviews and migration assessment
- **๐ข Low (18+ months to EOL):** Quarterly strategic planning inclusion
### **๐ Automated Reporting**
```mermaid
%%{
init: {
'theme': 'base',
'themeVariables': {
'primaryColor': '#fff8e1',
'primaryTextColor': '#e65100',
'lineColor': '#ff9800',
'secondaryColor': '#e8f5e9',
'tertiaryColor': '#e3f2fd'
}
}
}%%
flowchart LR
subgraph COLLECTION["๐ Data Collection"]
EOL_API["๐ endoflife.date API
โข Version EOL dates
โข Support timelines
โข Release schedules"]
PACKAGE_JSON["๐ฆ package.json Analysis
โข Current versions
โข Dependency tree
โข Security advisories"]
GITHUB_API["๐ GitHub API
โข Dependabot alerts
โข Security advisories
โข Release notes"]
end
subgraph ANALYSIS["๐งฎ Risk Analysis"]
TIMELINE_CALC["โฐ Timeline Calculation
โข Days until EOL
โข Migration lead time
โข Risk scoring"]
IMPACT_ASSESS["๐ Impact Assessment
โข Component criticality
โข Migration complexity
โข Business continuity"]
COST_ANALYSIS["๐ฐ Cost Analysis
โข Migration effort
โข Risk vs. investment
โข Resource allocation"]
end
subgraph REPORTING["๐ Automated Reporting"]
DASHBOARD["๐ EOL Dashboard
โข Real-time status
โข Risk heat map
โข Trend analysis"]
ALERTS["๐จ Alert System
โข Threshold breaches
โข Escalation workflow
โข Notification routing"]
MONTHLY_REPORT["๐
Monthly Report
โข Executive summary
โข Action items
โข Strategic recommendations"]
end
EOL_API --> TIMELINE_CALC
PACKAGE_JSON --> IMPACT_ASSESS
GITHUB_API --> COST_ANALYSIS
TIMELINE_CALC --> DASHBOARD
IMPACT_ASSESS --> ALERTS
COST_ANALYSIS --> MONTHLY_REPORT
style COLLECTION fill:#fff9c4
style ANALYSIS fill:#e1f5fe
style REPORTING fill:#f3e5f5
```
---
## ๐ Related Documentation
### **๐ Core ISMS Integration**
- **[๐ Vulnerability Management Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Vulnerability_Management.md)** โ "Living on the Edge" dependency strategy and EOL management
- **[๐ ๏ธ Secure Development Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Secure_Development_Policy.md)** โ Architecture documentation requirements and security controls
- **[๐ท๏ธ Classification Framework](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md)** โ Business impact analysis and risk prioritization methodology
### **๐๏ธ Black Trigram Architecture**
- **[๐ ARCHITECTURE.md](ARCHITECTURE.md)** โ Current system design and technology stack overview
- **[๐ FUTURE_ARCHITECTURE.md](FUTURE_ARCHITECTURE.md)** โ Evolution roadmap and planned architectural enhancements
- **[๐ก๏ธ SECURITY_ARCHITECTURE.md](SECURITY_ARCHITECTURE.md)** โ Security controls and EOL impact analysis
- **[๐ก๏ธ THREAT_MODEL.md](THREAT_MODEL.md)** โ EOL-aware threat modeling and risk assessment
### **๐ Project Management & Strategy**
- **[๐ง MINDMAP.md](MINDMAP.md)** โ System component relationships and EOL dependencies
- **[๐ผ SWOT.md](SWOT.md)** โ Strategic assessment including EOL risks and opportunities
- **[๐ฐ FinancialSecurityPlan.md](FinancialSecurityPlan.md)** โ Infrastructure cost analysis and security investment planning
- **[๐ WORKFLOWS.md](WORKFLOWS.md)** โ CI/CD automation adapted for EOL management
- **[๐ฎ game-status.md](game-status.md)** โ Current development status and EOL timeline integration
### **๐งช Testing & Quality**
- **[๐งช UnitTestPlan.md](UnitTestPlan.md)** โ Test coverage ensuring legacy compatibility validation
- **[๐ E2ETestPlan.md](E2ETestPlan.md)** โ End-to-end validation through technology transitions
- **[โก performance-testing.md](performance-testing.md)** โ Performance benchmarks for EOL decision making
### **๐ External References**
- **[โ Node.js EOL](https://endoflife.date/nodejs)** โ Node.js runtime lifecycle and support timeline
- **[๐ข Node.js Release Schedule Evolution](https://nodejs.org/en/blog/announcements/evolving-the-nodejs-release-schedule)** โ New release model starting with 27.x (one major/year, every release LTS)
- **[๐ nodejs/Release#1113](https://github.com/nodejs/Release/issues/1113)** โ Background discussion on the release schedule change
- **[โ๏ธ React EOL](https://endoflife.date/react)** โ React framework lifecycle and major version support
- **[๐ฆ NPM Package EOL](https://endoflife.date/)** โ General package and library end-of-life tracking
- **[๐ Browser Support](https://caniuse.com/)** โ Web standard compatibility and browser support lifecycle
---
**๐ Document Control:**
**โ
Approved by:** James Pether Sรถrling, CEO
**๐ค Distribution:** Public
**๐ท๏ธ Classification:** [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md)
**๐
Effective Date:** 2026-04-21
**โฐ Next Review:** 2027-04-21
**๐ฏ Framework Compliance:** [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md)