VOIDSYSTEM
SIGN INENTER THE VOID
· PROMISE ·

Permanence Editorial. Six clauses, written as a contract.

VOID asks you to trust your record to the system. That trust is asymmetric and needs to be earned on paper, not in tone. The six clauses below describe what VOID will not do, regardless of growth pressure or pricing change. Each clause has a technical note that explains how it is held.

VERSION 1 · 2026-05-19

  1. CLAUSE01

    Export always.

    Your Constructs, Phases, Expeditions, Archive entries, and Conquest history are exportable at any time, in a documented open format. No paid tier gates this. No promo window removes it.

    ENFORCED

    An export endpoint exists in the public API. The format is documented and stable.

  2. CLAUSE02

    No silent deletes.

    VOID does not remove what you made on its own. Archiving is reversible. Destruction of an entity is explicit, requires confirmation in writing, and produces a record of what was removed.

    ENFORCED

    Archive is a flag, never a deletion. Destruction paths require nominal confirmation. No background cleanup, no inactive-account purge.

  3. CLAUSE03

    Progression is permanent.

    Depth, Void Essence, Conquests, and Presence are never reset by a pricing change, a tier migration, or a product change. Earned progression stays earned.

    ENFORCED

    XP and Conquests live in your record. Pricing touches capabilities, never history.

  4. CLAUSE04

    Lore is fixed.

    The glossary (Construct, Phase, Expedition, The Archive, The Oracle, Depth, Void Essence, Presence) is not renamed for marketing reasons. If a term ever has to change, the old term keeps redirecting and a public note explains why.

    ENFORCED

    The glossary is a single source of truth in code. Renames go through versioned migration, not silent edits.

  5. CLAUSE05

    Wind-down clause.

    If VOID is ever discontinued, the operator commits to ninety days of advance notice, a final export of every Exile's full record in open format, and at least thirty days of read-only access after the export window closes.

    ENFORCED

    Public commitment. No silent shutdowns. The clause is part of this page and is versioned.

  6. CLAUSE06

    No quiet feature removal.

    A feature that shipped into the product does not disappear without notice. Either it stays, or it is removed with a public changelog entry and a migration path for the data it touched.

    ENFORCED

    The changelog is a public surface. Removals require an entry before the removal date.

If any clause is ever broken, the failure is public and documented. The contract is the contract.

RETURN TO THE VOID