Alien Corridor Support System

Select a module from the corridor manifest on the left,
then LOAD it to expose its clocks, matrices and enumerations.

Select a module to view its unmodified Clojure source.

Full Clojure REPL against the live engine.
Evaluate anything — exactly as the author did in Counterclockwise.

CTRL+ENTER · EVALUATES IN PERSISTENT NAMESPACE acss.console

Author's original REPL history (recovered)

loading…

Engine clock · z-tnldy-clock3 (sfo22 agent)

not engaged

Load sfo22 to engage the engine's own clock agent.

Live TNLDY · Nsukka/Yg clock (GUI-side, read-only)

—

Z = (yG − 1969)·Yg − 340 + days since 1 December 00:00 Nsukka, Yg = 17640/48.3 days: the engine's own year (sfo10), laid on Nsukka's calendar and recalibrated at every Yg year.

Alien corridor · core completion matrix 1 (sfo23, ZTP 10800)

—

(Z − 10800) ÷ 240 · projection; use sfo23 module for the sealed engine value.

What this is

The Alien Corridor Support System is a GUI cockpit for the original 3PP-NOAH84 / MDQNM Clojure project (time machines, clocks, corridor matrices, data alphabets, gematria ciphers and clock enumerations across ~90 namespaces).

Preservation guarantee

Not one tittle of the original Clojure is altered. The complete original folder lives verbatim in engine/ (verified byte-identical to the source). This GUI is a separate process layer that loads those files unchanged with (require … :reload) — the same mechanism the author's Eclipse Counterclockwise REPL used — running on the project's own original stack: Clojure 1.7.0, clj-time 0.11.0, joda-time 2.8.2.

This edition: in your browser

This page runs the engine without a JVM or a server. The same unmodified .clj files are read by SCI, a Clojure interpreter in the page, which supplies only what the JVM supplied: java.util.Date, clj-time's from-long and local-now, and agents. The API this GUI calls is answered in the page itself. The JVM engine remains the reference; every module of both editions has been compared with it — see fidelity. What differs, and why: numbers print the JavaScript way (16800 for 16800.0; no exact ratios), a character literal such as \n is the one-letter string "n", clocks read this device's clock and re-seal whenever the page is reloaded, and each visitor's engine is their own.

Two editions

The source folder contains two distinct editions of the engine that differ in nearly every file: the primary mdqnm tree and the mdqnmshulammitebanksystem tree. Each runs in its own JVM so their same-named namespaces never contaminate each other. Launch with ./run.sh primary, ./run.sh bank, or ./run.sh both.

How to use

① Pick a module in the left manifest and LOAD it (top-level agents are created and sealed to the current instant, exactly as on a REPL load). ② Invoke its functions — enumerations print full reports; corridor matrices take a Y or Z argument. ③ DEREF agents to read sealed clock values. ④ Or drop to the Console for raw REPL access, with the author's recovered command history alongside.

Feeds at a TNLDY

Every agent, and every function once its arguments are supplied, has a ⧉ FEED button. It opens a window that reads the agent or the call at the TNLDY it names — the TNLDY a function's arguments send it to, past, present or future; for an agent, and any call that reads the engine's clock, the clock itself, which can be set to any TNLDY — and shows the knowledge-server feeds at that TNLDY in JOMO SFO-WAM's feed regime: its domains, Latest or By source. The present is JOMO SFO-WAM's live snapshot, refreshed every 15 minutes; the past is the archive of every item those feeds carried (REVOTT STAMPS), and before the feeds' first reading GDELT's day sources; the future is ahead, and goes live when its window opens. The window runs its own copy of the engine, so this page is untouched.