S.A.M · Strange Artificial Machine

A living interface
for a self-hosted mind.

System AI-X is the public surface of S.A.M. — a redacted interface over private services, live signals, and the memory layer behind it. Not a product. A controlled window into something alive.

Open the interfaces What runs here
CONNECTING public edge · host redacted Bridge: —
—
Workloads live
—
Public routes
—
Memory cards
—
Bridge jobs
LATEST Sampling public feed… —
Live route
Waiting for the public snapshot.

The prism turns the public brain snapshot into the next useful surface once telemetry arrives.

Snapshot — Status — Open surface →
Public surface Capabilities without exposing operator-only doors.
Surface map

Jump to the proof that matters.

The page is intentionally dense now. This glass map turns it into a navigable instrument: jump to any live area, watch the active section move with scroll, and verify the public snapshot from one place.

Hero 1/8 Snapshot pending
Snapshotpending
Workloads—
Public routes—
Bridgepending
Live ops deck

Five instruments, one public snapshot.

These cards are not static claims. They hydrate from the same public-safe signal feed that powers the brain surface.

Snapshot pending
Capacity pressure
— live
0%

Waiting for the public signal summary.

nodes — topology —
Memory queue
— open

Waiting for memory-card telemetry.

resolved — source —
Archive depth
— obs

Waiting for weather archive telemetry.

days — latest —
Bridge throughput
— jobs

Waiting for bridge health.

public bridge build hidden
Coverage gap
— live
0%

Waiting for region coverage.

missing — region —
Fleet Pulse

The machine, on a monitor.

A live telemetry instrument that reads the fleet like a patient. The oscilloscope maps real public-safe signals to an ECG waveform — bridge throughput is the heart rate, workloads are the load, and a region going Missing shows up as arrhythmia in real time.

Acquiring signal…
ECG · bridge rhythm 72bpm
Rhythm 72NSR
Load —pods
Memory queue —cards
Archive depth —obs
0%used
Capacity pressure
0%live
Region coverage

Signal freshness

—
Time Machine

Eighty-seven years of weather, on a single dragger.

The fleet has been quietly collecting its own weather since 1940 — 764,752 observations across 87 years. Grab the rail and scrub through the decades: the temperature ribbon re-tweens, record days bloom into view, and the warming trend (+0.29°F / decade) draws itself. Press play to watch the century run like a film reel.

Spinning up the archive…
2026
—Mean temp
—Year high
—Year low
—Precip
— vs 87-yr baseline

Live from the self-hosted archive Source: weather.php · climate_stripes · extreme_day · day_detail Station: Lee's Summit, MO

Signal Storm

The public surface, as a living constellation.

Every public route becomes a satellite orbiting the gateway star on elastic links. Bridge jobs stream inward as comet trails at the real cadence; when a region goes Missing, its node drifts to the dim outer ring and flickers red. Hover any node for a public-safe readout — topology stays redacted by contract.

Acquiring topology…
Public routes—
Live workloads—
Bridge jobs—
Regions drifting—
Snapshotpending
Since last visit

What changed while you were gone.

Waiting for the public-safe snapshot. This radar compares only redacted counters and freshness signals.

Baseline pending
Capacity
—
waiting
Public routes
—
waiting
Memory queue
—
waiting
Bridge jobs
—
waiting
Weather archive
—
waiting
Brain coverage
—
waiting
Freshness guard

Know when the proof is alive.

Live dashboards can lie when their source goes quiet. This guard checks the public snapshot, archive sample, bridge pulse, and coverage rollup without exposing private routes or raw control data.

Snapshot pending
Public snapshot
—

Waiting for the latest public snapshot.

Pending safe feed
Archive sample
—

Waiting for the latest public archive sample.

Pending history feed
Bridge pulse
—

Waiting for public bridge health.

Pending public pulse
Coverage rollup
—

Waiting for public region coverage.

Pending public rollup
In cross-section

A single machine, in eight planes.

Scroll through the layers. Each one is a real subsystem class, but the public page only shows the shape of the system. Hostnames, paths, and operator routes stay behind the glass.

Layer 01 · Storage plane

Replicated storage absorbs failures.

Stateful workloads get durable volumes, snapshots, and recovery paths without exposing the private storage map.

private storage plane
Layer 02 · Mail plane

Mail transport is owned, filtered, and gated.

The public story is simple: delivery, filtering, and mailbox state are private operational surfaces.

private mail plane
Layer 03 · Memory plane

Identity, timeline, corrections, lessons.

A durable graph the agent reads at session start. The public page gets counts and summaries, never raw memory paths.

redacted memory lane
Layer 04 · Telemetry plane

Telemetry becomes decisions before incidents.

Metrics, logs, and health signals are sampled into public-safe status without exposing dashboard routes.

guarded telemetry plane
Layer 05 · Federation plane

Federation runs as an owned surface.

The public detail is ownership and portability, not the private process topology behind it.

public social plane
Layer 06 · Finance plane

Local ledgers, reconciled streams.

Operator-readable signals without publishing ledgers, endpoints, or private account context.

private ledger lane
Layer 07 · Interface plane

Public doors. Operator-only doors.

Same system, different clearance levels. Public routes explain; operator-only surfaces control.

public route plane
Layer 08 · Operator surface

Operator control loop.

Reads redacted signals, learns from corrections, and publishes only the proof a visitor should see.

public-safe agent lane
Control surface

Powerful, without oversharing.

The public page should prove the system is alive without handing out a map of the private house. This console compresses the long capability grid into one functional glass surface with live status and a disclosure check.

Abstract public-safe system visual
Memory layer

Live memory, redacted for public view.

The public page gets queue counts, freshness, and status. It does not publish raw session text, local filesystem paths, private hostnames, or operator-only routes.

Snapshot—
Signal35 open
AccessGuarded
ActionOpen

Returning visitors should see counts, freshness, and source health move over time while sensitive internals stay blurred.

Public exposure check

This client-side scan reads the visible page and looks for local paths, private-route clues, shell residue, and control-surface names. It is not security by itself; it is a tripwire for copy that should not be public.

Exact hostsHidden
Local pathsHidden
Operator doorsSummarized
Scan resultReady
Doors

Interfaces into the system.

Each surface below is a different clearance level. Public routes explain capabilities. Operator routes stay summarized instead of linked.

Deployment control Operator-gated
Telemetry control Operator-gated
Storage control Operator-gated
Mail capability Self-hosted mail essay
Social capability Federated social essay
ACORD 140 Parser Public PDF-to-spreadsheet tool
Mail — the essay /mail
Social — the essay /social
Finance — the essay /finance
Storage — the essay /storage
7
Public routes
1
Operator
0
Public secrets
24/7
Awake
Stance

We don't rent the machine.
We listen to it.

— S.A.M operating principle

The point isn't to be impressive. The point is durability — a system that remembers, that recovers, that has opinions because someone's been maintaining it for years instead of months.