Light · Precision · Data
The display technology SPEKTX was founded on: software that lets separate screens, projectors and passive aerial surfaces act as one picture. Patent pending.
SPEKTX LLC is a New Jersey company founded by Kevin Bramble. Spektx is where it started: a body of patent-pending display technology for screens that do not touch, projectors that share a curved surface, and aerial surfaces lit from the ground. The same way of working produced the security and governance engines that Krytix and Chorix are built on.
It is not a slide deck. Each idea has been reduced to an engine that runs, and each engine carries its own check. This page lists every engine and every demonstrator, and says plainly where each one stands: complete, mostly complete, or under construction.
Each track stands alone: its engines do not depend on another track's. Beside the three display tracks sit two sister technologies with engines of their own: the security core behind Krytix, and the governance engines behind Chorix. All twelve are listed below.
Billboards, glass, storefronts and trailers treated as nodes of one canvas. One creative runs across all of them with the gaps cancelled, each panel keeps its own calibration, and a ledger counts what was shown.
5 engines · 5 completeProjection onto domes, cylinders and irregular surfaces from a scan of the surface itself. The engine works out the correction for every projector, handles the places where there is nothing to hit, and blends the overlaps.
3 engines · 2 completeAerial surfaces that carry no lights of their own. A projector on the ground lights them; the engine finds each one from its infrared returns and predicts where it will be when the light arrives.
1 engine · 1 completeTwo technologies that grew up beside the display work. The security core behind Krytix holds a transaction reversible with no network. The governance engines behind Chorix decide who must rule, and when software may act by itself.
3 engines · 3 complete11 complete, 1 mostly complete. Complete means the engine passes its own built-in check; mostly complete means it runs end to end and still lacks a full check of its own. The advertising ledger has no built-in check: it is counted complete because it runs inside the Display Engine and its accounts reconcile.
| Engine | What it does | Track | Standing |
|---|---|---|---|
| Dead-space cancellation and predictive coherence | One picture across screens that do not touch: the gaps between them are cancelled, not stretched over, and each screen can carry on by itself when it loses contact. | Display network | Complete |
| Billboard cascade | A stored calibration map for every panel, so a picture is cut into its pieces the same way every time and lines up across the joins. | Display network | Complete |
| Trailer registration | Keeps a picture registered across a trailer surface that flexes as it moves. | Display network | Complete |
| Advertising ledger and impression model | Counts impressions from a traffic model and keeps the accounts that share the revenue, reconciled exactly. | Display network | Complete |
| Color manipulator | Tone, colour, selective hue, curves and lookup tables for the creative that goes on the screens. | Display network | Complete |
| Warp and void driver | The core projection math: how far each ray travels, how much to pre-distort it, what to do where there is nothing to hit, and how neighbouring projectors blend. | Projection | Complete |
| Predistortion engine for the browser | The same math running live in a browser, drawing the corrected feed for each projector. | Projection | Complete |
| Warp pipeline | The deployment form: takes a scanned surface, solves every projector over it, and writes the meshes a venue would load. | Projection | Mostly complete |
| Aerial mapping | Finds where each passive aerial surface is from its infrared returns, and predicts where it will be at the instant of projection. | Aerial | Complete |
| Reversible-state core | A transaction that can be held, reversed or committed with no network at all: staged, timed, and proof against replay. The secure hardware it is written for is not part of the software. | Security (Krytix) | Complete |
| Escalation chains | Who must rule at each gate, and where a decision goes next when that person does not answer. | Governance (Chorix) | Complete |
| Judgment governor | Decides when software may act by itself and when it must go back to the person, from that person's own record of rulings. | Governance (Chorix) | Complete |
Interactive scenes built on the engines. 1 complete, 2 mostly complete, 3 under construction.
| Demonstrator | What it shows | Standing |
|---|---|---|
| Spektx Display Engine | A three-dimensional array of separate screens you can drive: one creative across all of them, a live camera, mirror and projection modes, a colour grade, creative libraries, and the advertising ledger running live. | Mostly complete |
| Dead-space demonstrator | A single offline page: drag a picture across separated screens and watch the gaps cancel. | Complete |
| Dealership facade command | A dealership frontage treated as a display surface, with its zones, controls and readouts. | Mostly complete |
| Aerial lake | The aerial track as a scene: lit surfaces over water at night. | Under construction |
| Dealership lot | A lot of vehicles as a field of display nodes. | Under construction |
| Viewer | A stand-alone viewer for the display scenes. | Under construction |
Every engine is self-contained and gives the same answer every time. None of them needs a network to run.
An engine is called complete here only when it passes the check built into it.
The projection math exists as a reference engine and again as a live engine in the browser, written to the same contract.
Where the screens are and what they show are handled separately, so a surface can change without the creative changing.
The display network, projection and aerial engines do not depend on one another.
The technology on this page is the subject of pending patent applications.
For the display technology, its engines or a demonstration, write to us.
kevin@spektx.comThe family of IP behind these engines · Back to SPEKTX and the rest of the family