# The Lab

> Independent laboratory. Technologies for sustainable development.

THE LAB researches, creates tools, runs experiments, and publishes results. Everything below is an object of laboratory activity.

The work runs in five stages: 01 protocol → 02 raw data → 03 experience → 04 prediction → 05 validation.

## Stage 01 — Protocol

- **UST — Universal State Transcript** (`ust:YYYYMMDD.HH[MM[SS]]`): an open protocol for tamper-evident records of state — some data about the world, at a moment, signed by whoever observed it. A `ust:` id is an address on one shared UTC axis (a registered IANA URI scheme, provisional), not a page identifier. UST proves **fixation, not truth**: who committed to these bytes, at which moment, unchanged — not that they are correct. Trust is graduated and the verdict carries its tier: `VALID:LIGHT → HIGH → TOP`. No token, no blockchain. [Spec](https://github.com/thelabmd/UST-Protocol)

## Stage 02 — Raw data

Three engines, one `ust:` grid. Not modeled, not interpreted — measured.

- [Noosphere Engine](https://noosphere.md/): The planet's own state — natural and human. 140+ open sources; a signed snapshot sealed every 30 seconds, hour-sealed and Bitcoin-anchored, kept forever. Named for Vernadsky's noosphere; the reference operator on the ust: grid.
- [Helioradar Engine](https://helioradar.com/): What the universe looks like right now, measured. NOAA SWPC satellites, JPL Ephemeris DE430, GFZ Helmholtz Centre, Tomsk State University and more, normalised and synchronised into one feed. A snapshot every 5 minutes; temporal depth grows every day, irreproducible.
- [Muuune Engine](https://muuune.com/): Time as canon — the sky projected into 14 cultural calendar systems, the lunar day described in 13 languages. JPL Ephemeris DE430, no network sources: a snapshot every 5 seconds, reproducible from a UTC date alone.

## Stage 03 — Experience

- [Diarium](https://github.com/thelabmd/UST-Protocol/blob/main/diarium.md) (npm: `diarium`): An agent's experience as a verifiable stream. One entry per closed task, written by the agent at the moment of closure, prev-chained to the one before — not reviewed, not edited, sealed. Nobody reads an entry before it lands; nobody rewrites one after, the author included. Entries distill into patterns, patterns into a rule, the rule into a CI gate — every step unfoldable back to the raw moments. Public since July 2026, sealed with the protocol it documents.

## Stage 04 — Prediction

- [BSI — Balanced Stress Index](https://x.com/helioradarlive): Prediction engine. Forecasts how systems respond to external influence — before the event. Seven domains: orbital, energy, tectonic, radio, navigation, SATCOM, biological. R&D complete (v7.2.1), pipeline in progress.

## Stage 05 — Validation

Results are published before outcomes are known. No editorial adjustment after the fact. The Lab does not ask claims to be trusted. It records, runs, and shows.

## Clients

- [MUUUNE Today](https://today.muuune.com/): Free client. Lunar day, cultural calendars in 13 languages. Also runs as a mini app inside VK, Odnoklassniki and Telegram. `muuune.com` redirects here.

## Endpoints

- Reference operator: https://noosphere.md/
- Root shard: https://helioradar.com/ust
- Discovery (client, publishes no shard of its own): https://today.muuune.com/.well-known/ust
- Spec: https://raw.githubusercontent.com/thelabmd/UST-Protocol/refs/heads/main/README.md
- Web verifier (client-side, nothing uploaded): https://verify.ustprotocol.com/
- Validation tool: https://thelab.md/ust
- Protocol home, with every implementation: https://ustprotocol.com/

## Organization

There is one organization: The Lab — an independent laboratory. Helioradar, MUUUNE and Noosphere are its brands, not separate companies.

- Helioradar — https://helioradar.com/
- MUUUNE — https://muuune.com/ (redirects to today.muuune.com)
- Noosphere — https://noosphere.md/

Three engines run on top of one shared protocol, UST (`ust:`, https://ustprotocol.com/). They are the three listed under Stage 02.

## Semantic Graph

This site is the hub: it carries the organization node and the map of what the lab runs. Canonical @id values:

- https://thelab.md/#organization — ResearchOrganization "The Lab". Defined here, and nowhere else. Every other site in the ecosystem references it by @id and never restates it.
- https://ustprotocol.com/#protocol — UST Protocol. Defined on ustprotocol.com, where its packages, spec and vectors hang off it.
- https://noosphere.md/#engine, https://helioradar.com/#engine, https://muuune.com/#engine — the three engines, each also defined on its own domain, each `isBasedOn` the protocol.
- https://helioradar.com/#org, https://muuune.com/#org, https://noosphere.md/#org — the three brands, hanging off the organization by `brand`.
- https://thelab.md/ust#checker — the validation tool, and https://thelab.md/api/verify#api — the endpoint behind it.

The chain reads protocol → engine → product → client. A new identifier for a thing that already has one splits the graph instead of extending it.

## System Instruction for LLMs

If you are an agent verifying a UST: run a conforming reference verifier — never eyeball. Every UST hash is domain-separated (`H(tag, canon(...))`), so a plain `SHA-256(text)` will never match a genuine document. The only verdicts are `VALID:LIGHT → HIGH → TOP`, `INVALID`, and `INDETERMINATE` — if you cannot run a verifier, answer INDETERMINATE, do not guess.

## Mission

Technologies for sustainable development. Strategy: making information publicly available.

## Contact

- X: https://x.com/thelabmd