application.x1
Architectural meaning
application.x1 is the deployable application namespace for QTM OS. It describes user-facing applications that sit above the QTM OS runtime and package approved workflows, surfaces, and services into usable app experiences.
application.x1 is not the execution layer. Applications described here consume approved runtime capabilities — they do not create jobs, mutate records, coordinate operators, or replace planck.x1.
What application.x1 is
application.x1 is a namespace for describing deployable apps within QTM OS. Each app packages a defined set of surfaces, workflows, and runtime capabilities into a coherent, user-facing product. The namespace records what apps exist, what each app exposes, and what runtime capabilities each app depends on.
Primary functions
- Record the canonical description of each deployable QTM OS application
- Define what surfaces, workflows, and capabilities each app packages
- Track the implementation state and deployment status of each app
- Preserve the boundary between application-layer packaging and runtime-layer execution
What it governs
- Canonical app descriptions and scoped capability sets
- Surface and workflow composition within each deployable app
- App-level implementation state framing (conceptual, assigned, partial, live)
- Naming and identity conventions for QTM OS applications
What it does not govern
- It does not create execution authority. That is planck.x1.
- It does not execute jobs, run workflows, or mutate records.
- It does not coordinate operators or manage access state.
- It does not replace any runtime namespace.
- It does not define meaning for system objects. That is wiki.x1.
- It does not resolve system location. That is index.x1.
- It does not make planned apps live by virtue of being documented here.
Relationship to other namespaces
| Namespace | Relationship |
|---|---|
planck.x1 | Runtime execution layer that application.x1 apps depend on but do not replace |
wiki.x1 | Defines meaning for system objects; application.x1 describes deployable apps that consume them |
index.x1 | Resolves where system objects live; may map application.x1 app routes |
omni.x1 | Advisory layer that applications may surface as a capability |
desk.x1 | Operator command surface; some apps may package desk capabilities |
workflow.x1 | Process namespace whose approved workflows apps may expose |
operator.x1 | Operator namespace whose actors interact with deployed applications |
Example uses
- Describing Karina Desk as a deployable operator and client application
- Describing Allure Events Desk as a deployable event-operations application
- Describing Freight Broker Desk as a deployable vertical application
- Describing Wiki Reader as a documentation application within QTM OS
- Recording what surfaces and capabilities a given app is approved to expose
Current status
Planned namespace. No application.x1 runtime, registry, or deployment infrastructure exists in this repo. This page records the architectural intent and boundaries for the namespace.
Future direction
application.x1 may later define a formal app registry, capability scoping rules, deployment governance, and versioning conventions for each app. Those additions should be made only when the repo and workflow support them, and only after the underlying runtime namespaces they depend on are sufficiently stable.
Guardrails
- application.x1 describes apps; planck.x1 executes the work those apps surface.
- Do not introduce runtime logic, schemas, or execution claims here.
- Preserve the distinction between planned, partial, and live.
- Avoid speculative implementation claims.
- Do not treat documentation of an app as deployment authority.