Skip to main content
sooth — the Truemark

The sooth family

sooth — truth you can check

sooth explores how more of a system's behavior, provenance, and refusal can become explicit enough to examine. Its hosted kernel milestone is real, private, and narrower than a downloadable operating system.

sooth is the family. Soothfast is the kernel. Active development

sooth is the Magogi Foundation's flagship systems-software family. At its heart is the Soothfast kernel; around it sit a build forge, a trust-first mesh, a provenance-bearing debugger, a trust-first systems language, and a GUI toolkit whose entire interface is one readable text file. Alongside that core, the family carries an applied verifiable-AI member and a flagship consumer hardware project that take the same discipline to new ground. They are designed as one coherent family that shares the kernel's laws and provenance model rather than each reinventing its own.

The long-term strategy has two parts: bring checkable properties to existing software stacks without requiring kernel adoption, and build complete systems for bounded hardware uses. These are directions at different stages, not a ready integration for every platform. Current examples include reproducible build evidence on an existing substrate and the hosted kernel's recorded behavior.

Soothfast's private v0.9.0 hosted release tag is dated 2026-08-28. The kernel-side time-source gate crossed on 2026-08-20 inside a host environment. That establishes neither a public OS download nor device hardware, trusted physical time, or real mesh transport.

How to read this page

sooth is in active development — and currently private.

This is Magogi's long-term systems work. Roster rows and pinned counts come from dated family records. The milestone paragraph is a source reading reviewed 2026-09-13. The source reading is not a fresh kernel-suite execution, an independent signature verification, a public OS download, hardware execution, or real mesh transport.

sooth and Soothfast are in active development and developed privately. A private hosted release exists; no public operating-system download, hardware crossing, or real mesh transport is claimed.

The family

Each member is described by what it does and by where it sits. The family is in active development and currently private; we do not publish dates we cannot keep.

  • Member
    sooth-standard
    Ring
    0
    Level
    L3
    What it is
    The family's engineering standard: its rules, its philosophy, and the tooling that enforces them. The family's own standard, adapted with attribution from the Magogi standard. Its shipped code boundary remains independent; selected MGF Python development tooling may be used outside that boundary.
    State
    Active development Private
  • Member
    soothfast
    Ring
    1
    Level
    L3
    What it is
    The kernel: deterministic and compliance-first, designed around explicit states, refusal, and provenance. Active development and private. A hosted v0.9.0 release tag exists, but no public operating-system download or hardware crossing is claimed.
    State
    Active development Private
  • Member
    soothglass
    Ring
    2
    Level
    L2
    What it is
    The GUI toolkit: a user interface as one readable text file with a mandatory semantic twin — no pixel is painted whose meaning has not been published. Pre-alpha, by its own README: the language, the oracles and the parser are real and verified; nothing renders yet.
    State
    Active development Private
  • Member
    soothsmith
    Ring
    2
    Level
    L2
    What it is
    The forge: it turns a kernel build into a provenance-bearing artifact for a board — provenance you re-derive rather than trust. Active development · private.
    State
    Active development Private
  • Member
    soothtroth
    Ring
    2
    Level
    L1
    What it is
    The language: a trust-first systems language whose compiler lowers to a pinned toolchain. Active development · private.
    State
    Active development Private
  • Member
    soothwatch
    Ring
    2
    Level
    L2
    What it is
    The provenance-bearing debugger: a separately built instrument for recording, replaying, and examining kernel decisions. Active development and private. Its evidence describes recorded debugger behavior rather than an independent audit of the full family.
    State
    Active development Private
  • Member
    soothweave
    Ring
    2
    Level
    L2
    What it is
    The trust-first mesh: networking work with explicit routing, trust, and provenance decisions. Active development and private. Real mesh transport remains a kernel crossing, with production cryptography included in that crossing.
    State
    Active development Private
  • Member
    soothrede
    Ring
    2A
    Level
    L1
    What it is
    Applied verifiable AI: a self-hosted, local-first, all-integer inference core that runs byte-identically twice. Active development · private. The registry records a conformance level below the one its README declares, and the registry wins by the family's own rule.
    State
    Active development Private
  • Member
    first-light
    Ring
    3
    Level
    L2
    What it is
    The family's flagship consumer project: a verifiable weather node whose firmware provenance is re-derived rather than trusted. A sooth-family project, never a Magogi product listing. Hosted evidence does not establish device hardware; real hardware remains a separate crossing.
    State
    Active development Private
  • Member
    sooth-brand
    Ring
    brand
    Level
    n/a
    What it is
    The family's identity layer: the canonical reference for what sooth is, and its visual system. Describes and mirrors; defines nothing.
    State
    Active Private
The 10 members of the sooth family, read at build from the family's own registry. Ring is a structural position — 0 the standard, 1 the kernel, 2 the siblings, 2A an applied member that does not depend on the kernel, 3 a consumer built on family surfaces — and level is the conformance level the registry records, which is the one that binds even where a repository's own README declares a higher one. Source: sooth-standard/SOOTH_LIBRARIES.json at 49b27c7, synced 2026-09-13.

One chain, four instruments

Four of those members are not a feature list — they are one provenance path. The kernel decides, the forge turns a build into a provenance-bearing artifact, the mesh is intended to transport it without abandoning the kernel's laws, and the debugger records and replays observations. Real mesh transport remains a crossing, so this diagram describes the family design rather than a deployed path. The chain reads: kernel, forge, mesh, debugger.

  1. soothfast deterministic core
  2. soothsmith verified artifact
  3. soothweave transport design
  4. soothwatch replay + attest

The numbers the family pins

The family's own voice canon says the strongest sentence it can write is one with a hash or a gate name in it. These are the values its brand repository pins and mechanically re-checks, mirrored here with their provenance rather than retyped.

Members
10 repositories in the family, counted from its registry and cross-checked against the brand pin
Rules
222 in the family's engineering standard, of which 194 are binding
Laws
20 in the kernel's constitution, inherited by reference across the sibling ring
Kernel bundle digest
58ea59fa…9f52 the short form the brand pins — a record, not a download

Recorded at build from sooth-brand/identity/facts.pins.json at c026351, synced 2026-09-13, sha256 7166d51031941bbf…. Upstream, a gate asserts each pin against the live sources; here, the snapshot is re-hashed on every build. Neither check makes any of it reachable by you today.

Gated, not faked

A stack that claims determinism has to be exact about the parts of the world it has not touched yet. Two kernel crossings remain, and where something stands in for one, the substitution is marked rather than quietly passed off as the real thing. This list is the family's own, and it is here in full — it is not a roadmap, and it carries no dates.

  • Real hardware

    first-light — the family's Ring-3 consumer, a verifiable weather-mesh node — is the project this gate opens onto.

  • Real mesh transport and production cryptography

    soothweave's hosted work does not establish real network transport; production cryptography belongs to this same crossing.

How sooth relates to Magogi

sooth is a project of the Magogi Foundation and its first endorsed sub-brand: it has its own name, voice, and mark, but it is visibly part of Magogi and inherits the Foundation's legal, governance, and infrastructure umbrella. It follows its own engineering standard — parallel to, and adapted with attribution from, the standard behind the mgf-* library federation.

The shipped boundary is a rule: sooth product code depends on no mgf-* library, and no mgf-* library depends on sooth. The family may use selected MGF Python development and operations tooling outside its shipped trust and provenance boundary. Shared tooling and attributed lessons do not make the two families' standards interchangeable.

Boundary source: sooth-standard@49b27c7, reviewed 2026-09-13. The written boundary and dependency register do not establish that every specified gate currently runs or that every repository is conformant.

Status

sooth is in active development and developed privately. A private hosted kernel release exists; it runs under a host environment and is not a public, bootable operating-system download. Real hardware and real mesh transport remain deferred, with production cryptography included in the mesh crossing. Public distribution is a separate milestone.

Verify it yourself
No public release yet. Every repository in the roster is private today, so this page links none of them and invites you to clone nothing. The records behind it are named where they are used and re-hashed at build.