PUBLIC INFORMATIONCURRENT PHASE P0
LUMORAP0 · PUBLIC INSTITUTIONAL SURFACEResearch · Technology · Institutional Development
Menu

Platform status

One operational namespace. Distinct operating-system owners.

lumora-ingo.org is the institutional, research, governance and evidence-facing public surface. lumoraplatform.xyz is assigned as the Lumora OS root operational surface and the shared namespace under which other Domain Operating Systems may receive governed subdomains.

Hold / not activated

Owner and namespace bindings now exist, but this page does not represent a launched public service-runtime, paid service, account system, wallet, KYC flow or Production Lumora OS. Namespace assignment is not Production activation.

Current institutional status

00 — Commercial service architecture

Digital-first development without invented launch claims.

LumoraOS, VoxelVerse and Lumora VoxelVerse Studio are being developed for interactive learning, virtual goods, creator services and AI-assisted experiences. Planned paid services and internal LUM entitlements have distinct product, contract, settlement and consumer-rights conditions. The current PH-P0 Founder/operator may prepare and lawfully provide qualifying services independently of a future Swiss institutional formation; this page does not claim that a public wallet or checkout is active.

Explore digital services and commercial readiness

01 — Surface separation

Institutional information and operational runtime remain separate.

INSTITUTION

lumora-ingo.org

Who Lumora is, what it researches, how responsibility is structured, and what governance and evidence can be published.

OPERATIONAL ROOT

lumoraplatform.xyz

The root operational surface assigned to Lumora OS and the root of the shared delegated operational namespace.

TECHNOLOGY

Web∞

Generic technology, conformance and cross-OS federation contracts. Web∞ does not allocate concrete Lumora ecosystem hostnames or own OS-specific business truth.

02 — Operating-system namespace

The shared hostname hierarchy does not merge the operating systems.

The topology below is a public projection of records held in the governance and operating-system owner repositories. This website does not own namespace allocation or runtime truth.

  1. Lumora OS

    lumoraplatform.xyz

    ROOT ASSIGNED · owner binding materialized

    HOLD NOT ACTIVATED

  2. GBOS

    gbos.lumoraplatform.xyz

    DELEGATED · owner binding materialized

    HOLD NOT ACTIVATED

  3. STAVA OS

    stava.lumoraplatform.xyz

    RESERVED · owner repository not yet materialized

    NOT AUTHORIZED

  4. SoloFlow OS

    soloflow.lumoraplatform.xyz

    RESERVED · owner repository not yet materialized

    NOT AUTHORIZED

  5. NOB! OS

    nob.lumoraplatform.xyz

    RESERVED · owner repository not yet materialized

    NOT AUTHORIZED

Federation principle

Shared namespace.
Scoped interoperability.
Independent truth.

Authority

OS-specific

A shared hostname hierarchy does not transfer roles, governance authority or reserved matters between operating systems.

Data & consent

OS-specific

Federated identity or interoperability does not silently create shared consent, data ownership or access rights.

Economy & evidence

OS-specific

Service exchange does not itself merge treasury, revenue, tax treatment, wallet ledgers or canonical evidence ownership.

03 — Activation principle

A namespace can exist before its service is allowed to exist publicly.

A domain or subdomain becomes a live service destination only after the applicable owner repository, authority, implementation, security, policy, evidence, deployment and recovery gates support that state.

  1. Allocated / reserved

    Governance can assign or reserve a namespace without creating a runtime.

  2. Owner binding

    The operating-system owner repository records what that namespace means for its own domain truth.

  3. Controlled implementation

    Software can exist without being advertised as publicly available.

  4. Verification and admission

    Security, quality, authority, policy, evidence and recovery gates determine whether activation is supportable.

  5. Public activation

    Only then may an operational entry point become clickable and be represented as available.

Technology context

04 — Source boundary

This page is a projection, not the authority root.

Current projection is pinned to owner evidence in Lumora Governance, Lumora OS, GBOS and Web∞. If those owner records change, this public projection must be reconciled before a new public status is asserted.

GOVERNANCE

Namespace allocation

Owned by Lumora Governance. Current evidence: ab1faf935679…

DOMAIN OS

Runtime truth

Owned by each operating-system repository. Lumora OS and GBOS owner bindings are materialized; STAVA, SoloFlow and NOB! owner repositories remain on hold.

WEB∞

Federation technology

Generic cross-OS contract only. Current evidence: 742f1ed034ea…