🚀 Launch QTMoS VisPy
QTMoS.com Lab

QTMoS Experimental AI Nebula

A home-grown Ai operating space for symbolic logic, rails, and CognitiveSystems_V3 — running on Windows + WSL + QTMoS interlaces both!, LIke the name states, AI states "Are Birthed Here!"

About QTMoS

A personal AI Os-style'd shell wrapped around your own experiments.

QTMoS Status: Active · Lab build

QTMoS (Quantum Tier Multi-operational System) is a self-hosted environment where you prototype logic transforms, symbolic engines, and ideas that don’t fit normal software boxes. (◣◢)™

It started as a local lab on Windows + WSL; this page is the public front door: no frameworks, no heavy stack — just your own HTML being served off your own machine.

Discord server is live — come hang out and talk: https://discord.gg/9Q6RBkV26k

Core ideas:

  • Everything important runs under your control (home box + quick tunnel).
  • Layered design: shell, rails, WSL envs, web UI, not one giant blob.
  • Room for non-textbook logic.
  • Lab, not product — it can be rough around the edges by design.

CognitiveSystems_V3

Your personal AI-style assistant and memory system, wired into the stack.

CognitiveSystems_V3 is your local “audible mind” — a scripted assistant and reflection engine that:

  • Tracks core vs episodic memories and synthesis logs.
  • Hooks into QTMoS for commands, state checks, and experiments.
  • Emotional custom binary systems catalogs based on internal logic.
  • Keeps state in files / JSON that you can inspect and move around.

Sample lab prompt flow:

learn "anything" - Add new episodic memory
recall - View memories
promote "anything" - Promote episodic to core mem
ingest-api - Ingest Wikipedia summary into mem
ingest-url - Ingest page text into memory
duel p1 p2 q? - persona1&2 respond about it

The goal isn’t to be “officially correct” — it’s to notice patterns, reactions, and how your own thinking loops around the outputs.

Architecture Snapshot

How the layers you built actually stack together.

Home-lab path:

  • Hardware: your physical PC + GPU.
  • Windows host: browser, X launch, tools.
  • WSL2 (Ubuntu 24.04): Linux envs, QTMoS shell, CognitiveSystems_V3.
  • Rails: QUADOS / QFS, ±rail, tiers and modes.
  • Web entry: qtmos_control.py serving CogSystems terminal bridge on ws cloudflared tunnel run qtmos = Domain QTMoS.com.
  • Cloudflare Tunnel: Launch a secure reverse-proxy path into your local QTMoS box using:
    cloudflared tunnel --url www.qtmos.com
  • Cloudflare generates a temporary, session-based *.trycloudflare.com URL that points directly to your WSL-hosted QTMoS backend.
  • Any device — phone, laptop, guest — can open that URL. Requests flow through Cloudflare’s edge network → into your tunnel → straight into QTMoS.
  • No static IPs, no port-forwarding, no VPS, no AWS. Just a Zero-Trust encrypted pipe from the internet to your personal lab machine.
  • All sensitive operations remain local: CognitiveSystems_V3, GPU workloads, filesystem tools, constructor engine, shell rails, memory models — none of it leaves your hardware.
  • This setup gives you “public” access to QTMoS without exposing your machine or granting anyone raw network access — Cloudflare becomes the armored entry hatch.