Software architecture for streaming data

DECIMA-8 Detects rare events in a continuous stream

DECIMA-8 is a software core for monitoring and decision systems. It continuously reads data, retains how a process develops, and emits a signal when a specified meaningful situation appears.

Start with documentation Open WebGL demo
runs on a standard server built for continuous data reproducible state signals only on events

What a system receives

A complete event detection contour

Decima connects to a data source, follows how the process changes over time, and passes an event to an existing application. A deployed project has four clear parts.

01 / connection

Data adapter

Turns a market, telemetry, sound, or another stream into eight normalized channels.

02 / detector

Personality

A compact executable configuration built for a specific class of meaningful events.

03 / execution

Runtime

Runs on a standard server, retains process state, and makes exact historical replay possible.

04 / action

Integration

The event enters a trading system, monitoring stack, automation, or another application contour.

Operating contour

A personality is created by an Architect

The runtime does not learn in production or silently change its rules. The Architect defines the meaning of input lanes and the shape of the reaction; the Baker translates that intent into an executable personality object. 

ENVIRONMENT
  ↓
PRESS → VSB[8]
  ↓
PERSONALITY .d8p
  ↓
FIRE events
  ↓
DIRECTOR → action
Environment

A continuous source

A market, telemetry, sound, network, or another process where dynamics matter more than an isolated snapshot.

Press

Eight physical meanings

The Press normalizes the environment into a VSB frame. The semantics of each lane belong to the system being built.

Architect

The intent of a personality

The Architect defines weights, corridors, decay, priorities, domains, resets, and the permission graph. This is where domain engineering lives.

Baker

Building an executable brain

The Baker verifies the structure and emits a .d8p personality. The same personality moves across compatible runtimes without retraining.

Runtime

Deterministic execution

The complete ordered tape, the same personality, initial state, and reset schedule produce the same event trace.

Director

Meaning and action

The Director owns application context: risk, system state, permissible action, and the decision to do nothing.

A personality is not a list of text rules.

It is a baked dynamic medium. Its memory emerges from distributed accumulator state, lock transitions, and permitted topology. The Architect defines the character of that memory before runtime.

FIRE / rare event

First useful system

Whaler listens to market microstructure

Whaler compresses a trade stream into eight lanes, passes them through a Decima personality, and waits for a rare event. A separate Director interprets the event and manages position state and risk.

This is not a pretty pattern demo or an attempt to trade every move. It is a long-running test of the architecture in a noisy, non-stationary environment with economically measurable outcomes.

Whaler documentation

Who it is for and why

DECIMA-8 application areas

Decima is not one universal detector. For each domain, an Architect defines the meaning of input channels, the significant event, and a separate personality. The status of every direction is stated explicitly.

Working system

Market microstructure

For trading and risk system developers. Whaler detects rare state changes in a continuous market trade stream.

Demonstration

OCR and visual symbols

A manually baked OCR personality showed that Decima can hold a deterministic recognizer. This validates the mechanism; it is not a finished OCR product.

Direction

ASR and acoustic events

For voice and acoustic systems: detecting stable sound structures, commands, and anomalies in a continuous audio stream.

Direction

Equipment monitoring

For industrial teams and integrators: observing telemetry, operating modes, and rare transitions that require a response.

Research demonstration

A manually baked OCR personality

This demonstration records an early engineering result: an Architect manually assembled a personality for typed-digit recognition and observed it in the IDE. It validates the principle on a visual stream, but is not presented as a standalone product.

Platform

Commodity CPUs are Decima's current platform

Now

Commodity hardware is enough

The reference runtime executes personalities on standard CPUs. That is sufficient for Press development, baking, long-running live observation, deterministic replay, and production applications.

We develop the architecture through tools, personalities, and working systems. They can be verified, moved, and applied on accessible computing platforms today.

Later

A native substrate can arrive naturally

When mature memristive technology becomes a practical engineering platform, it may provide a more direct physical execution substrate for Decima. That is a possible evolution, not a prerequisite for the architecture today.

Open ecosystem

The architecture grows through knowledge and applications

Public v3 physics, reference code, and documentation provide a shared language. Architects can create their own Press, personalities, and Directors while keeping application know-how inside their systems.

Specification Decima documentation v3 physics, personality format, runtime, and determinism boundaries. Reference Source code The reference implementation and engineering artifacts of the architecture. Method Philosophy The Architect, context, personality, and the discipline of event systems. Registry RuleROM A registry of ecosystem projects, documents, and working systems.

Build a system

Start with the flow and the event

Describe the environment, the available data, and the event that matters enough to distinguish from noise. We will determine whether Decima fits, what Press the task needs, and where the personality should end and the application Director should begin.