01 · Title
Perslis is the AI operational runtime.
A runtime layer that lets AI understand, operate, verify, and improve real software systems, including legacy desktops and virtual machines.
Perslis
The body that lets any model operate.
02 · Problem
Models cannot reliably touch the systems companies still run on.
Legacy OSes, siloed apps, and brittle operator workflows sit outside the clean API world. Models can describe them, but they lose reliability when they must see, click, inject payloads, compile binaries, and prove the outcome.
Legacy execution targets
03 · Perception
Tinky Vision turns screens into stable spatial maps.
The runtime sees the desktop as coordinates, text, UI regions, and intent targets. Visual context is streamed into the loop so non-visual models can still operate software through grounded observations.
AX/T/V coordinate grid
x:24 y:36
Start
compile output
04 · Architecture
Voltron OS assembles proof from static traces and live state.
Kist records what the system knows, what changed, what ran, and what was verified. Perslis reassembles that evidence in real time so the model cannot simply claim completion.
Runtime architecture
inputGoal, system context, live screen
kist loopPlan, route, execute, verify, remember
perslis runtimeVMs, desktop, tools, IPC, compilers
proofTrace, artifact, test, audit event
05 · Multi-Substrate Proof
One operator loop across old desktops, emulators, and compilers.
Perslis proves the runtime by executing across different substrates: legacy Windows, modern Windows, emulator surfaces, COBOL, DOS, and direct binary tooling.
Hardware-free execution
06 · IPC Plumbing
Host and guest communicate through direct payload channels.
Perslis does not depend on fragile manual copy-paste. It can move payloads through QMP, guest bridges, window automation, and application-specific adapters.
Bridge trace
host slack.event.message │ ├─ normalize payload ├─ verify target session ├─ inject via guest channel │ win95 NOTEPAD.EXE receives text └─ capture evidence and checksum
07 · Safety
The Captain makes autonomy fail closed.
The runtime requires evidence before claiming work is done. If tools fail, model output drifts, or verification is missing, the loop blocks completion and records a repair target.
Captain terminal gate
research · light gate PASS execute · artifact changed verify · missing proof captain refused completion opened bounded repair mission status: fail closed
08 · Governance
Every action becomes ledgered operational evidence.
Kist normalizes tool events, decisions, verification records, and failures into an audit stream that can be exported into security and compliance systems.
Tamper-evident ledger
event.idtool.callhash:91afactormimo plannersignedtargetwin98 sessionscopedoutcomecompletion refusedauditedexportECS / SIEMready09 · Memory
Agents improve through retained operating memory.
The system keeps structured memories about failures, skills, tool behavior, user preferences, and environment facts. Progression turns repeated proof into better routing and safer defaults.
S.P.E.C.I.A.L. progression
10 · Business Model
Gated engine, open loop, enterprise control plane.
Kist grows adoption through an open operational loop. Perslis monetizes the hard runtime layer: legacy execution, guest control, audit exports, governance, and enterprise support.
Dual-layer licensing
Community adoption, local workflows, memory, routing, and verification patterns.
VM orchestration, IPC bridges, enterprise governance, audit export, and support.