wiki.x1

Architectural meaning

wiki.x1 is the canonical knowledge and documentation namespace for QTM OS. It gives the system a durable reference layer for architecture, domains, surfaces, modules, standards, definitions, maps, and operational understanding.

It complements execution and coordination namespaces. It does not replace them.

What wiki.x1 is

wiki.x1 is a documentation surface and knowledge-governance layer. It records how QTM OS should be understood, how its namespaces relate, and how implementation status should be read.

The namespace is private-first in this repo. Public-facing documentation may be derived from reviewed wiki.x1 pages through the publication workflow, but publication is a deliberate act, not a side effect of writing a page.

Primary functions

  • Maintain canonical terminology and architectural definitions
  • Organize domain, namespace, module, surface, workforce, and standards pages
  • Preserve distinctions between conceptual, assigned, partially implemented, and live work
  • Provide source-aligned maps for QTM OS architecture and namespace strategy
  • Support future public documentation without weakening internal system truth

What it governs

  • Documentation structure and knowledge organization
  • Canonical and reference pages for QTM OS
  • Visibility, status, and implementation-state framing
  • Publication readiness for future public docs
  • Contributor expectations for precise, non-promotional system language

What it does not govern

  • It does not execute jobs or coordinate work.
  • It does not mutate Planck runtime state.
  • It does not replace planck.x1, omni.x1, desk.x1, operator.x1, workflow.x1, or jobs.xen.
  • It does not make draft or planned systems live.
  • It does not authorize public release by itself.

Relationship to other namespaces

NamespaceRelationship
index.x1Resolves location; wiki.x1 defines meaning — the two layers do not overlap
planck.x1Runtime execution and storage layer that wiki.x1 documents but does not operate
omni.x1Advisory intelligence layer that may read documented context but does not receive authority from docs
desk.x1Governance and command surface documented by wiki.x1
operator.x1Executable actor namespace documented by wiki.x1
workflow.x1State and process namespace documented by wiki.x1
jobs.xenGoverned work availability and assignment namespace documented by wiki.x1

Example uses

  • Reading the execution spine before changing runtime behavior
  • Checking namespace boundaries before introducing a new domain page
  • Confirming whether a surface is conceptual, assigned, partially implemented, or live
  • Preparing a public-facing summary from reviewed source material
  • Auditing terminology across QTM OS docs

Current status

Active namespace page in the Domains sidebar at /domains/wiki-x1. The documentation system exists in this repo; public filtering and publication tooling remain governed future work.

Future direction

wiki.x1 may later support intentionally published public documentation, source-sync checks, review roles, and stronger publication gates. Those should be added only when the repo and workflow support them.

Guardrails

  • Preserve the distinction between planned, partial, and live.
  • Avoid marketing language and speculative implementation claims.
  • Keep IDs, namespaces, and lifecycle terms precise.
  • Do not treat documentation as runtime authority.
  • Do not weaken private-first source posture while preparing public-facing material.