reference · v0.01

Glossary

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

private draft assigned qtm-os

Glossary

Purpose

Glossary is part of the Glossary section of wiki.x1.

Architectural role

This page anchors Glossary inside the QTM OS knowledge layer. It records the intended role, status, and boundaries without implying runtime behavior that has not been implemented.

What it governs

  • Canonical terminology for this area
  • Status framing across conceptual, assigned, partially implemented, and live work
  • Relationships to the execution spine and namespace model where relevant

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, service event, record, or settlement layers.

Relationships to other layers

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

Current status

Partially populated with canonical terms from the execution spine, signal, and listing layers.

Terms

⭐ Signal

A system-emitted, execution-derived trust attribution object. A ⭐ Signal is produced after a ServiceEvent completes and a Record is sealed. It cannot be manually created or self-declared. It traces back to a specific Job, ServiceEvent, and Record. Governed by the ⭐.x1 namespace. Not a review score or user feedback object.

MLS Listing

A structured, discoverable listing artifact that organizes a service or opportunity into a format capable of converting directly into QTM OS intake. Governed by the mls.x1 namespace. Sits upstream of intake. Does not create execution objects directly.

Execution Spine

The strict sequential path: Actor → Request → Task → Assignment → Job → ServiceEvent → Record → Settlement. No layer may be bypassed.

Record

Durable execution truth created from a completed ServiceEvent. The canonical source of truth for what happened in execution. Records may be linked to assets, rights, and ⭐ Signals downstream.

Intake

The governed entry point for service requests. Conversion from a listing, surface form, or API submission that produces a Task for review and assignment. Intake does not create Jobs directly.

ServiceEvent

The execution runtime container for governed operator work. Created from a Job. Contains evidence, stage transitions, and completion state. Produces Record on completion.

Operator Routing Rule

Requests originating from operator-owned surfaces must route to the originating operator’s governance surface first. Central admin (network-managed) review applies only when the funnel is explicitly network-governed.

Listing Trust

Trust indicators shown on a listing in mls.x1. Always read-only references derived from ⭐.x1 signal history. Cannot be self-asserted by an operator or publisher.

Future direction

Expand all terms as each layer reaches partial or live implementation state.

Guardrails

  • Preserve the distinction between planned, partial, and live.
  • Avoid marketing language.
  • Keep IDs, namespaces, and lifecycle terms precise.