ARIS OS · evolution log

It started as a shell.

Every entry in this log is real — pulled from the project's commit history. The machine did not arrive self-aware; it grew, one improvement at a time.

Current · v0.1.0-rc.7

MilestoneWhat arrived
rc.7README with install instructions — the shell becomes distributable
rc.6Custom theme color — one accent in, a full CRT family out; settings row in General
rc.5Stability pass — harness crash fixes, mono-font removal, theme render fixes
rc.4Dir-panel color harmonization; dev workflow documented (3083 local instance)
rc.3Project structure refactor — bundle / client / host packages split cleanly
rc.2World view — the encom-globe sphere with endpoint markers and spline links
rc.1System telemetry — left bar with CPU, memory, processes; right bar with network and traffic
0.0.1First breath — the shell frame around the harness GUI

Each milestone is a small act of self-improvement: a panel added, a color fixed, a crash hunted down, a readme written. That is the whole philosophy in miniature — observe, reason, act, learn — applied by humans first, and increasingly by the system itself.

Planned · the roadmap (vision — not shipped)

PLANNED

ARIS on Android

The shell tuned for touch and small screens — telemetry, world view, and agent workspaces in your pocket, with the same local-first privacy.

PLANNED

Persistent memory

A learning layer that keeps improvement history across sessions — so the OS remembers what worked and why, and gets faster at fixing itself.

PLANNED

Agent workspace sync

The same workspace on every device — start an agent on your laptop, continue on your phone, no cloud required.

PLANNED

Tool & panel registry

An open registry of agent tools and shell panels, so the OS — and its operators — can extend the machine without forking it.

Roadmap items are marked planned on purpose. ARIS does not promise futures it has not built — it ships what runs, and improves from there.

History source: the dsh-edex-ui repository ↗ · MIT