01 // TECHNICAL CASE STUDYFLAGSHIP INTERNAL ENGINE

blox-aether-core
Discord Engine & Three.js Architecture

A comprehensive architectural breakdown of Bloxaether Labs' internal operations and client consultation engine. Built with Node.js 22 LTS, strict TypeScript ESM, discord.js v14, Prisma ORM with SQLite, and an interactive Three.js 3D topology visualizer.

01 // System Philosophy & Mission

In high-stakes software engineering, communication latency and lost requirement records often compromise sprint delivery. Rather than relying on generic SaaS ticketing forms or manual chat channels, blox-aether-core delivers a unified Discord platform operating across two distinct tiers: an automated public client consultation intake and a role-guarded internal operations hub.

Designed and built specifically by our Lead Software Engineer and QA Specialist, every interaction—from the 4-field modal submission to atomic database writes and encrypted channel teardowns—strictly adheres to our studio's Dual-Gate QA framework and zero-spam notification principles.

02 // Interactive 3D System Topology

Interactive Three.js WebGL visualization of the core subsystems, dispatch pipelines, and data stores.

[INITIALIZING THREE.JS WEBGL TOPOLOGY ENGINE...]

03 // Core Functional Subsystems

MODULE 01 // CLIENT INTAKE

Dynamic 4-Field Intake & Isolated Channels

Executing /ticket-panel deploys a persistent client consultation showcase. Clicking the action button opens a 4-field modal collecting Project Name, Estimated Budget, Target Deadline, and Technical Scope.

  • Isolated private #ticket-{username} channels
  • Anti-spam 3-second interaction deferral guards
  • 3 quick-action buttons (Close, Add Note, Request Call)
MODULE 02 // ARCHIVAL ENGINE

Dual-Delivered Dark HTML Transcripts

Closing a client ticket executes an automated channel history sweep. Messages, code snippets, attachments, and timestamps are compiled into an encrypted, standalone dark HTML document without external CSS dependencies.

  • Direct DM dispatch to client upon closure
  • Mirrored immutable copy in `#ticket-logs`
  • 100% offline-viewable with syntax-highlighted code blocks
MODULE 03 // INTERNAL QA RIGOR

Role-Guarded QA Bug State Machine

Our QA Specialist tracks defect lifecycles via /bug add. A custom state machine transitions tickets across Open, Triaged, In Progress, and Resolved states.

  • In-place embed mutations prevent notification fatigue
  • Role-based access guard: only Lead & QA roles can edit
  • Automated SQLite persistence & severity tags
MODULE 04 // RUNTIME OBSERVABILITY

Native HTTP Health Server & Diagnostics

A lightweight Node.js HTTP server listens on port 7890 without bulky frameworks. Exposes real-time RSS memory consumption, heap usage, and Discord WebSocket ping latency.

  • Two-column `/server-status` Discord command
  • Native Docker healthcheck container probe
  • Sub-millisecond JSON latency metrics

04 // Engineering Tradeoffs & Architectural Decisions

Decision 1: SQLite on Local NVMe vs. Remote Distributed Database

For a single-instance Discord bot, network hops to external database servers introduce unnecessary latency and potential connection timeouts during gateway spikes. We chose Prisma ORM with SQLite stored directly on the host's NVMe drive. This delivers sub-millisecond query execution, zero external network dependency, atomic ACID transactions, and painless backup automation via standard snapshot scripts.

Decision 2: In-Place Embed Mutations vs. Successive Channel Messages

Standard Discord bots spam channels with new messages every time a state changes, triggering notification storms for engineers. blox-aether-core executes atomic message edits on existing embed payloads, keeping the defect queue pristine, readable, and noise-free.

Decision 3: Standalone Dark HTML Transcripts vs. Plain Text Logs

Plain text logs lose formatting, user avatars, and code syntax. We engineered a custom HTML builder that packages the full thread with Discord dark mode styling into a single offline-readable file. This serves as an immutable legal record of sprint requirements and technical handoffs for our clients.

05 // Technical Specification Matrix

← Swipe horizontally to view full matrix →
LayerTechnologySpecification / VersionEngineering Purpose
RuntimeNode.jsv22+ (LTS)Native ESM execution and high-performance I/O
LanguageTypeScript5.8+ Strict, NodeNextEnd-to-end type safety and compile-time validation
Gateway APIdiscord.jsv14.18+WebSocket connection, REST endpoints, and button handlers
PersistencePrisma ORMv6.x with SQLiteType-safe schema modeling with local NVMe persistence
ValidationZodv3.xRuntime environment variable and input validation
TestingVitestv3.x SuiteDual-Gate QA unit and integration test coverage
VisualizationThree.js / WebGLv0.174.0Interactive web architecture showcase with DOM mirror
EXPERIENCE BOUTIQUE SOFTWARE CRAFTSMANSHIP

Need Precision Discord & Web Engineering?

Consult directly with our Lead Software Engineer and QA Specialist. Zero agency fluff, zero sales intermediaries.