standard ยท v0.01

Overview

Standards overview within wiki.x1, the private-first knowledge layer for QTM OS.

private active assigned qtm-os

Standards

Purpose

Standards define the rules that keep wiki.x1 precise, private-first, and aligned to QTM OS architecture.

This section governs naming, event classes, economic object language, record-linked asset rules, visibility/status policy, publication workflow, docs governance, and domain-governance rules.

Architectural role

Standards are not execution surfaces. They are documentation and governance constraints that keep architecture, implementation reality, and publication posture legible.

What it governs

  • Naming rules and namespace language
  • Event class terminology
  • Canonical economic object language
  • Record-linked asset expectations
  • Visibility, status, and implementation-state discipline
  • Publication workflow for future public docs
  • Contributor guidance for wiki.x1 pages
  • Domain governance rules

What it does not govern

  • It does not create execution authority.
  • It does not replace runtime source-of-truth records.
  • It does not collapse task, job, ServiceEvent, record, or settlement layers.
  • It does not publish private docs automatically.

Relationships to other layers

Standards should be read against the execution spine, canonical namespace spine, and domain architecture strategy.

Standards protect the wiki from drifting away from saved architecture and current implementation reality.

Current status

Active standards index. Some standards pages are canonical or active; others may remain draft until their source material stabilizes.

Future direction

Expand standards as new source-of-truth documents stabilize. New standards should preserve QTM OS terminology and implementation-state discipline.

Guardrails

  • Preserve the distinction between planned, partial, and live.
  • Avoid marketing language.
  • Keep IDs, namespaces, and lifecycle terms precise.
  • Do not imply publication automation before it exists.