KNOuXr
ACCESS

02 / ENGINEERING

Systems are
relationships.

A technical archive of what is implemented, what is constrained, and where the evidence lives. Interface claims stop where repository evidence stops.

Inspect the dossiers

A CONTINUOUS PRACTICE

From surface to system.

SW-01 / KNOUX ONEDECLARED ARCHITECTURE
01 / SURFACE
React 19 · TypeScriptDesktop shell

One interface over nineteen modules

Registry-driven navigationModule registry

Arabic / English search

02 / RUNTIME
Tauri 2Typed command bridge

Allowlisted renderer → Rust commands

RustNative workspaces

No arbitrary shell endpoint

03 / PROTECTION
Cross-volume quarantineCopy → flush → verify

BLAKE3 before source removal

Developer StudioBounded cache paths

Credential payloads refused

Repository-declared structure. Browser preview declines desktop operations.

01 / THE POINT OF CONTACT

Interface

How someone understands and uses a system.

IMPLEMENTATION RECORD

Registry-driven desktop shell covering nineteen modules with grouped navigation and Arabic/English search

CHECKABLE SOURCEREADME · implementation & limits Repository audit / 2026-09-28
Read the complete dossier

Implementation evidence and runtime verification are separate. Explore every system’s capabilities, constraints and sources below.

ENGINEERING DOSSIERS

Persistent context follows the selected system while the implementation record scrolls independently. Each dossier exposes declared capabilities and limitations side by side instead of turning documentation into a wall of text.

SW-01 / WINDOWS INTELLIGENCE

KNOUX ONE

A Windows desktop workspace that keeps one shell over nineteen modules and refuses to claim a service it cannot prove. Its own evidence baseline separates statically verified native paths from planned ones, and browser preview returns desktop_runtime_unavailable rather than inventing a host reading.

Implementation evidence

  • Registry-driven desktop shell covering nineteen modules with grouped navigation and Arabic/English search
  • Typed Rust-to-renderer command allowlist with no arbitrary shell endpoint
  • Native workspaces for setup, cleanup, duplicates, storage, startup, performance, repair, network and a developer studio
  • Cross-volume quarantine that copies, flushes, verifies a BLAKE3 digest, and only then removes a source
  • Developer Studio restricted to recognised cache paths and refusing credential payloads

Constraints & declared limits

  • Its own baseline reports 74 statically verified native paths, 6 partial, 110 planned, and 0 runtime-verified on Windows in repository evidence
  • Modules M09 to M14 and M16 to M19 are planned and expose no handler
  • Permanent purge does not claim guaranteed SSD secure erasure
TECHNOLOGY

Tauri 2 · Rust · React 19 · TypeScript · Vite

CHECKABLE SOURCES
  • README.mdProduct title, stack, module and service evidence matrix, safety boundaries
  • REAL_IMPLEMENTATION_MATRIX.mdReferenced as the service evidence authority
  • docs/services/service-reality-baseline.mdGenerated evidence baseline referenced by the README
  • .github/workflows/m03-native-validation.ymlWindows Rust formatting, Clippy and native test workflow
  • repository homepage fieldhttps://knoux-one.vercel.app
SW-02 / ENGINEERING TOOLING

KNOuX Forge

A React workspace over an Express API for discovering repositories, reading code evidence and running trusted project workflows. It reports unconfigured capabilities explicitly instead of fabricating remote, CI, registry, AI or release state, and it refuses to promote missing external-provider evidence to success.

Implementation evidence

  • Local project discovery with collections, trust, health, problems and bounded scans
  • Language-aware analysis of files, imports, symbols, routes, APIs, dependencies, cycles and architecture evidence
  • Release and Distribution Center keeping local artifacts, package identity, CI provenance and remote state independent
  • Marketplace that exposes provenance, permissions, compatibility and truthful unavailable states
  • Global search across real local product entities with visible coverage and safety limits
  • Preview Experience topology orchestration with owned process lifecycle, port evidence and service-scoped logs

Constraints & declared limits

  • Starts in Offline Mode; remote, CI, registry, preview and cloud AI surfaces stay unconfigured until a real adapter and action supply evidence
  • No trustworthy remote extension package adapter is configured, so remote install claims remain blocked rather than simulated
  • The Windows installer is an unsigned development and release artifact and makes no trusted-publisher claim
  • Its newest recorded green gate is run 271 on 2026-09-08, not a claim about current HEAD
TECHNOLOGY

React 18 · Express · TypeScript · Zod · Vite · Vitest · Playwright

CHECKABLE SOURCES
  • README.mdProduct description, reference verification baseline, architecture map, truthful limitations
  • docs/KFORGE-CAPABILITY-MATRIX.mdCapability-level status evidence
  • docs/DESKTOP_ARCHITECTURE_DECISION.mdArchitecture and trust boundaries
  • docs/SIGNING.mdRelease modes and the CI signing contract
  • repository metadataLicense MIT
SYSTEM RELATIONSHIPS
KNOUX ONE KNOuX Repair
SW-03 / SYSTEM MAINTENANCE

KNOuX Repair

A local-first Windows workstation exposing eighteen service categories through a web UI, an Electron shell, a Windows desktop build, a PowerShell console and a loopback execution bridge that runs only registered tools. Every registered tool carries risk metadata and destructive paths require explicit confirmation.

Implementation evidence

  • Eighteen service categories covering maintenance, cleanup, network, programs, duplicates, disk space, services, performance, security, diagnostics, backup, developer tools, privacy, drivers, monitoring, environment, post-install and project analysis
  • Risk classes of READ_ONLY, SAFE_CLEANUP, SYSTEM_REPAIR, DESTRUCTIVE and REBOOT_REQUIRED with confirmation before destructive execution
  • A loopback execution bridge that allowlists registered KNOuX tools and bounds scan and input ranges
  • An explicit UAC boundary: an unelevated bridge rejects admin-required tools with 403 ELEVATION_REQUIRED
  • Optional local authentication through GitHub OAuth or Microsoft Entra ID with loopback HttpOnly session cookies

Constraints & declared limits

  • Manual real-machine validation is still required for destructive end-to-end flows, reboot flows, rollback and hardware telemetry
  • The authoritative service map is Docs/SERVICE-INVENTORY.md; historical 100-tool documents describe an earlier console baseline
TECHNOLOGY

TypeScript · React 18 · Vite · Electron · PowerShell · .NET

CHECKABLE SOURCES
  • README-EN.mdProduct surfaces, service map, safety model, authentication, CI gate
  • VERSIONVersion 2.0.2
  • Docs/SERVICE-INVENTORY.mdAuthoritative current service and tool maturity matrix
  • Docs/SAFETY-MODEL.mdExecution, UAC, quarantine and protection boundaries
  • Docs/TOOLS-MANIFEST.jsonRegistered execution inventory
  • .github/workflows/ci.ymlWindows quality gate
SW-04 / FILE MANAGEMENT

KNOuX SmartOrganizer

A Windows desktop utility whose renderer cannot run commands or reach Node.js. Cleanup is a read-only preview by design, and the build explicitly refuses to claim deletion, registry changes or automation it has not implemented.

Implementation evidence

  • Storage and file tools covering disks, large files, SHA-256 duplicate detection, empty folders, Downloads inventory and file hashes
  • Smart Scan producing read-only disk, large-file and temporary-file review findings
  • System health for CPU, RAM, system drive, uptime and battery where Windows exposes it
  • Tool execution lifecycle from queued through preflight, running, progress, result, completed, cancelled and failed
  • Arabic and English with Arabic default and full document direction switching to RTL
  • Versioned local settings for language, appearance, scan, cleanup, privacy and performance defaults

Constraints & declared limits

  • Cleanup is a read-only temporary-file preview; the build performs no automatic cleanup
  • It claims no file deletion, registry changes, startup toggling, service manipulation, repair actions, scheduled automation, update downloads, usage statistics or AI assistance
  • Unsigned development build unless a signing certificate is configured in the build environment
TECHNOLOGY

Electron · React · TypeScript · Vite · NSIS

CHECKABLE SOURCES
  • README.mdImplemented-capability table, intentionally-unavailable list, privacy model, architecture
  • docs/FORENSIC_BASELINE_AUDIT.mdDetailed baseline findings referenced by the README
SYSTEM RELATIONSHIPS
KNOuX Repair KNOuX REC
SW-05 / CAPTURE & MEDIA

KNOuX REC

A Windows-first screen recorder that separates implemented from fully runtime-verified, and says so. Recordings are disk-backed incrementally so a crash does not destroy the take, and verification is carried by FFmpeg and FFprobe rather than by assertion.

Implementation evidence

  • Screen, window and constrained region capture with camera picture-in-picture composition
  • Incremental disk-backed recording with low-disk guards and local recording recovery
  • FFmpeg and FFprobe backed media verification and export, plus versioned .knouxrec projects and trimmed project export
  • Manual captions with SRT export, local thumbnails, library search and sorting, and timeline zoom controls
  • A native WASAPI helper and sandboxed renderer with a narrow typed preload bridge and validated IPC input

Constraints & declared limits

  • The product distinguishes implemented from fully runtime-verified; several capabilities remain partial pending real-device, long-session, multi-DPI, failure-recovery and installer acceptance gates
TECHNOLOGY

Electron · React · TypeScript · FFmpeg · FFprobe · WASAPI

CHECKABLE SOURCES
  • README.mdCurrent product reality, security boundaries, verification commands
  • docs/CURRENT_BASELINE.mdDeclared current authority for product behaviour
  • docs/PRODUCTION_STATUS.mdDetailed status matrix
  • docs/PROJECT_FORMAT.md.knouxrec project format
SW-06 / CAPTURE & MEDIA

KNOuX Player X

An Electron media player combining hardware-accelerated playback with static FFprobe and FFmpeg stream inspection, an equalizer and DSP chain, subtitle handling, and optional OpenRouter model integration for chat and playlist work.

Implementation evidence

  • Video and audio playback with hardware-accelerated decoding and 4K HDR rendering
  • Static FFprobe and FFmpeg stream analysis for metadata and container inspection
  • Neural DSP stage with a ten-band equalizer, presets and audio effects
  • Subtitle handling for SRT, VTT, ASS and SSA with custom styling
  • Optional OpenRouter integration for chat, model selection and playlist generation
  • Documented keyboard control surface including seek, volume, mute, fullscreen, loop, shuffle and subtitles

Constraints & declared limits

  • The AI features require a user-supplied OpenRouter API key and are not active without one
  • The repository README links to a knoux.dev documentation site that the repository itself does not evidence as KNOuX-operated, so it is not published as a KNOuX URL
TECHNOLOGY

Electron 28 · React 18 · TypeScript · FFmpeg Static · Zustand · Framer Motion

CHECKABLE SOURCES
  • README.mdFeature set, tech stack table, project structure, keyboard shortcuts, version badge
  • LICENSEMIT
  • repository homepage fieldhttps://knoux-x.vercel.app
SW-07 / DEVELOPER PRODUCTIVITY

KNOuX Clipboard AI

A local-first clipboard workspace whose release status is stated plainly in its own README as a release candidate under verification. Sensitive input is blocked before transport, the renderer never receives the provider credential, and services without a real runner are demoted to guarded automatically.

Implementation evidence

  • Local clipboard history with a renderer that never receives the OpenRouter credential
  • Local pre-transport scanning that blocks credential-like values, keys, tokens, JWTs, private keys, SSH keys, emails, phone numbers and card-like values
  • Vault IPC using AES-256-GCM with a random 16-byte salt, a 12-byte IV and a scrypt-derived key in knoux:v2 payloads
  • A service truth model that marks a service active only when it resolves through a verified executable runner
  • Developer Studio and barcode and QR utilities, with Arabic and English interface support

Constraints & declared limits

  • The repository states its own status as release candidate under verification and asks that catalog metadata not be treated as production evidence
  • Local transformer inference is intentionally guarded because its former dependency chain was not verified for the release baseline
  • Live AI requires OpenRouter configuration; the offline fallback is labelled fallback and never ready
TECHNOLOGY

Electron 43.4.1 · React · TypeScript · Vite · Vitest · NSIS

CHECKABLE SOURCES
  • README.mdStatus, runtime baseline table, security boundaries, CI gates, service truth model
  • .nvmrcNode.js 22.x baseline
  • docs/audit/FINAL-RELEASE-GATE.mdNamed as the release evidence record
  • LICENSEMIT
  • repository homepage fieldhttps://knoux-ai-clipboard-pro.vercel.app
Next archiveWork