Foundational Overview

1. Purpose

The UTS Glossary is the shared terminology layer for the Universal Theory Stack.

It defines the recurring terms, variables, operators, diagnostics, gates, constructs, failure modes, restoration arcs, interfaces, and registry language used across UTS modules.

Its primary purpose is not only to explain words. It preserves the precision of the system.

A UTS term often carries several simultaneous functions:

• a human-readable definition
• a technical system meaning
• a symbolic or conceptual meaning
• a registry index role
• a machine-readable indexing role
• a cross-module linking role
• a guardrail against terminology drift

The glossary therefore functions as both a reader aid and a semantic infrastructure layer for the project.

1. Core Function

The glossary supports seven main functions.

1.1 Reader Orientation

It gives new readers compact definitions before they enter denser modules.

This is especially important because UTS uses many terms that have common-language meanings but more precise technical meanings inside the system.

Examples:

• Coherence is not vague harmony.
• Restoration is not symbolic closure.
• Consent is not a checkbox.
• Stability is not automatically coherence.
• Fitness Proxy is not the same as real success.
• Signal is not automatically truth.

1.2 Cross-Module Consistency

The glossary prevents the same word from drifting across modules.

For example, Hidden Debt appears in security, restoration, governance, economics, biology, scaling, AI, and failure modes. The local expression may change, but the core definition must remain stable.

1.3 Registry Alignment

The glossary provides the short definitions that connect the major registries:

• Operator Registry
• Diagnostics Registry
• Invariants Registry
• Laws & Scaling Rules Registry
• Failure Modes Registry
• Restoration Arcs Registry
• Constructs & Operating Systems Registry

Each registry entry can reference glossary terms instead of redefining them repeatedly.

1.4 Website Infrastructure

The glossary is designed to support the public archive site through:

• hover definitions
• term pages
• search indexing
• tag generation
• cross-links
• sidebar reference pages
• machine-readable exports
• reader pathway tools

1.5 AI-Readable Alignment

The glossary gives AI readers a stable semantic map so they can preserve UTS definitions during summarization, search, retrieval, translation, and tool generation.

This matters because many UTS terms are close to ordinary language but are not interchangeable with ordinary meanings.

1.6 Drift Prevention

The glossary acts as a calibration surface.

When a new module introduces a term, the glossary helps determine whether it is:

• a new canonical term
• a synonym of an existing term
• a subtype of an existing term
• a module-local phrase
• a registry candidate
• a deprecated or redundant formulation

1.7 Translation Layer

The glossary enables UTS to be translated between technical, public, symbolic, governance, AI, biological, economic, and system-design language without flattening the term.

2. Scope

The glossary covers recurring UTS language across the following term families:

1. Core variables

Example: O, H, ε, ι, Au, µᵢ, BΣ, K, R, Φ.

1. Operators

Example: ⊕, ⊗, Π, Γ, Δ, ℛ, Ξ, Μ, Τ, Θ, Λ, Σ, Ψ.

1. U-layer localization terms

Example: U0 through U8.

1. Diagnostics

Example: Slack, Bandwidth, Damping, Constraint Complexity, Effective Auditability, Memory Half-Life.

1. Gates and admissibility terms

Example: FI-Gate, HR-Gate, MS-Gate, Au-Actuation, Λ Compatibility Gate, BΣ Validity.

1. Core system patterns

Example: Pseudo-Coherence, Hidden Debt Export, Basin Lock, Ring-Down, Inversion.

1. Restoration terms

Example: Restoration Arc, Origin-Layer Repair, Conditional Reintegration, Controlled Decoupling.

1. Governance and justice terms

Example: Legitimacy, Rank Immunity, Responsibility Gradient, Coherence-Valid Contract.

1. AI governance terms

Example: Cognitive Infrastructure, Signed Decision Provenance, Recognition Gradient, Ontology Freeze.

1. Principles and interface terms

Example: Principle Constraint Field, Shadow Interface, Light Interface, Empathy Interface, Wisdom Interface.

1. Identity and archetype terms

Example: Identity Matrix, Soul, Archetype, Archetypal Drift, Translation Layer.

1. Applied system terms

Example: Coherent Economy, Biological Coherence, Membrane, Cancer as Pseudo-Coherent Growth Basin.

1. Construct and tool terms

Example: Coherence Support Evaluator, Failure Mode Mapper, Restoration Arc Selector, Operator Sequence Builder.

3. Canonical Glossary Architecture

The glossary should be organized as a structured reference layer rather than an essay.

Recommended structure:

0. Purpose
1. Usage Note
2. Core State Vector Terms
3. Core Operators
4. U-Layers
5. Diagnostics
6. Gates and Admissibility
7. Core System Patterns
8. Restoration Terms
9. Justice / Governance / Legitimacy Terms
10. AI Governance Terms
11. Principles and Interface Terms
12. Intention / Identity / Soul Terms
13. Archetype Terms
14. Economy Terms
15. Biology / Medicine Terms
16. Constructs and Operating Systems
17. Registry Terms
18. Compact A–Z Index
19. Machine-Readable Summary
20. Citation
21. Status

This hybrid structure is useful because pure alphabetical ordering is easy to search but weak for learning. The project benefits from both:

• conceptual grouping for comprehension
• A–Z index for lookup
• machine-readable summary for indexing and retrieval

4. Term Entry Anatomy

A full glossary term can eventually contain the following fields.

term: "Hidden Debt"
term_id: "gloss-hidden-debt"
status: "canon"
type: "core-variable"
symbol: "H"
short_definition: "Deferred incoherence, unresolved burden, unpaid repair, exported cost, or suppressed contradiction."
long_definition: "..."
related_terms:
  - "Restoration"
  - "Inversion"
  - "Pseudo-Coherence"
  - "Hidden Debt Return"
source_modules:
  - "Coherence"
  - "Restoration"
  - "Security"
  - "Scaling"
registry_links:
  - "/archive/failure-modes"
  - "/archive/restoration-arcs"
aliases:
  - "deferred incoherence"
  - "unpaid repair"
disambiguation:
  - "Not the same as visible error."
  - "Not always immediately observable."

The public glossary page does not need every field at first, but the structure should guide future machine-readable expansion.

5. Definition Standards

Glossary entries should follow these standards.

5.1 Compact but Not Flattened

Definitions should be short enough for reference use but not so short that they lose the UTS meaning.

Weak definition:

Coherence means things work together.

Stronger UTS definition:

Coherence is the preservation of identity, meaning, and functional integrity across time under transformation.

5.2 Preserve Technical Distinctions

Definitions should protect key UTS distinctions:

• Coherence ≠ fitness proxy
• Stability ≠ coherence
• Signal ≠ truth
• Diagnostics ≠ adjudication
• Consent ≠ checkbox
• Restoration ≠ apology
• Growth ≠ expansion
• Legibility ≠ legitimacy
• Force ≠ restoration
• AI fluency ≠ AI coherence

5.3 Define by Function, Not Ideology

UTS terms should be defined by system function.

Example:

Justice is restoration of auditability, agency, and legitimacy under symmetry.

This avoids reducing terms to morality, preference, or rhetoric.

5.4 Include Failure Boundaries Where Needed

Some terms require a paired warning because the common-language word can drift.

Example:

Stability is a system’s tendency to return to an attractor after perturbation. Stability is not coherence.

5.5 Preserve Layered Meaning

Many UTS terms operate across several layers at once.

Example: Boundary may apply to biology, governance, contracts, AI permissions, identity, consent, institutional roles, or technical interfaces.

The glossary should retain enough abstraction to allow cross-domain use.

6. Term Classes

The glossary should distinguish between term classes so the archive can later support structured navigation.

6.1 Core Variable

A term that belongs to the canonical state vector.

Examples:

• O — Coherence
• H — Hidden Debt
• Au — Auditability
• BΣ — Boundary Integrity
• R — Restoration Capacity
• Φ — Fitness Proxy

6.2 Operator

A named state transformation.

Examples:

• Γ — Select
• Π — Constrain
• ℛ — Restore
• Ξ — Inversion Detection
• Λ — Compatibility

6.3 Diagnostic

A measurable or observable signal used to read system condition.

Examples:

• Slack
• Bandwidth
• Damping
• Effective Auditability
• Constraint Complexity
• Memory Half-Life

Diagnostics inform action but do not automatically authorize action.

6.4 Gate

An admissibility mechanism that determines whether an action, coupling, authority claim, contract, enforcement path, or restoration sequence may proceed.

Examples:

• FI-Gate
• HR-Gate
• MS-Gate
• Au-Actuation
• Λ Compatibility Gate

6.5 Pattern

A recurring system behavior.

Examples:

• Pseudo-Coherence
• Basin Lock
• Hidden Debt Export
• Inversion
• Ring-Down

6.6 Failure Mode

A recurring structural pathway through which coherence degrades.

Examples:

• Consent Theater
• Security Theater
• Metric Substitution
• Boundary Collapse
• Restoration Bypass

6.7 Restoration Arc

A sequenced repair pathway.

Examples:

• Truth Reconstruction
• Boundary Reconstitution
• Legibility Restoration
• Justice-Aligned Repair
• Controlled Decoupling

6.8 Construct

A reusable UTS framework, evaluator, interface, or operating system.

Examples:

• Coherence Support Evaluator
• Coherence Admissibility Ladder
• Institutional Coherence Trajectory Evaluator
• Coherence Loss Surface Map

6.9 Applied Domain Term

A term adapted to a specific domain while preserving UTS logic.

Examples:

• Coherent Economy
• Biological Coherence
• Cognitive Infrastructure
• AI-Mediated Archetype

7. Relationship to the Core Model

The glossary is anchored in the UTS state vector:

S(t) = { O, H, ε, ι, Au, µᵢ, BΣ, K, R, Φ }

This means many terms should be interpreted relative to these variables.

Examples:

• Pseudo-Coherence usually means apparent stability or success while H and/or ι rise.
• Goodhart Collapse usually involves Φ replacing O.
• Restoration requires H↓, R↑, BΣ↑, Au↑, or O↑ depending on context.
• Boundary Collapse means BΣ↓.
• Auditability Collapse means Au↓.
• Meaning Collapse means µᵢ↓ below functional threshold.

The glossary should therefore never define terms in isolation when the variable relationship is load-bearing.

8. Relationship to Operators

Operators explain how systems change.

The glossary should preserve the difference between:

• state variables: what condition the system is in
• diagnostics: how state is read
• operators: how state is changed
• gates: whether action is admissible
• restoration arcs: how repair unfolds over time

Example:

Ψ receive signal
→ Μ interpret
→ FI-Gate verify feedback integrity
→ Λ test compatibility
→ Π constrain scope
→ Γ select action
→ ℛ restore
→ Τ validate over time

The glossary can define each operator individually while the Operator Registry explains full operator logic.

9. Relationship to U-Layers

The glossary must preserve U-layer localization because UTS repair depends on locating where a pattern appears, originates, and must be repaired.

U0 — Substrate
U1 — Power / Budgets
U2 — Configuration / Boundaries
U3 — Execution
U4 — Classification
U5 — Coordination / Time
U6 — Coherence Field
U7 — Memory / Recurrence
U8 — Environment / Forcing

A glossary term may appear at several U-layers.

Example: Boundary can appear as:

• U0 membrane or material interface
• U2 permission or contract boundary
• U4 classification boundary
• U5 timing boundary
• U6 coherence-field boundary
• U7 memory boundary

Glossary definitions should remain portable while individual modules provide layer-specific treatment.

10. Relationship to Registries

The glossary is not a substitute for registries. It is the definitional index that supports them.

10.1 Operator Registry

The glossary gives short operator definitions. The Operator Registry gives full mechanics, failure modes, and examples.

10.2 Diagnostics Registry

The glossary defines diagnostic terms compactly. The Diagnostics Registry gives formula, interpretation, thresholds, misread risks, and usage rules.

10.3 Invariants Registry

The glossary defines core invariant language. The Invariants Registry gives canonical invariant statements and violation consequences.

10.4 Laws & Scaling Rules Registry

The glossary defines recurring scaling concepts. The Laws Registry formalizes system behavior under scale, load, compression, amplification, or delay.

10.5 Failure Modes Registry

The glossary defines failure mode names. The Failure Modes Registry gives full entries: first gate failure, hidden debt path, inversion structure, U-layer localization, and restoration sequence.

10.6 Restoration Arcs Registry

The glossary defines restoration arc language. The Restoration Arcs Registry gives full repair sequences and admissibility conditions.

10.7 Constructs & Operating Systems Registry

The glossary defines construct names. The Constructs Registry explains how each construct is used as a framework, evaluator, interface, or tool workflow.

11. Canonical Distinctions the Glossary Must Protect

The glossary should repeatedly protect the following distinctions because they prevent major UTS drift.

11.1 Coherence vs Fitness Proxy

O is the real coherence target. Φ is a measurable success signal.

A system can show rising Φ while O falls.

Φ↑ while O↓ ⇒ ι↑

11.2 Stability vs Coherence

A system can be stable inside a low-coherence basin.

Stability means it returns to an attractor. Coherence asks whether that attractor preserves identity, meaning, and functional integrity across time.

11.3 Signal vs Truth

Signals require classification, traceability, feedback integrity, and time validation.

A signal can be useful, noisy, manipulated, partial, delayed, inverted, or misclassified.

11.4 Diagnostics vs Adjudication

A diagnostic reveals state. It does not automatically authorize punishment, enforcement, or conclusion.

11.5 Consent vs Procedural Permission

Consent must be scoped, informed, revocable, non-coerced, boundary-valid, and supported by exit.

11.6 Restoration vs Symbolic Closure

Restoration must reduce hidden debt and recurrence. It cannot be replaced by apology, optics, settlement language, or procedural closure alone.

11.7 Growth vs Expansion

Growth means internal capacity increases. Expansion means external scope increases.

Expansion without internal capacity produces hidden debt.

11.8 Auditability vs Trust

Trust may exist socially, but UTS legitimacy requires auditability where stakes are high.

11.9 Force vs Restoration

Force can constrain damage, but it issues hidden debt unless followed by repair, truth, boundary restoration, and time validation.

11.10 AI Performance vs AI Coherence

AI fluency, benchmark performance, or compliance does not prove coherence, consent-validity, auditability, or restoration capacity.

12. Canonical Gate Language

The glossary should keep gate definitions stable across the archive.

FI-Gate — Feedback Integrity Gate

Blocks feedback capture, Goodhart drift, metric substitution, and proxy success replacing coherence.

HR-Gate — High Risk Gate

Blocks high-risk binding, especially identity-binding, high-impact classification, authority claims, or control-loop entry under insufficient evidence or weak auditability.

HR means High Risk, not Hard Rule and not Harm / Responsibility.

MS-Gate — Meta-Symmetry Gate

Prevents rank immunity, privileged exemptions, asymmetric accountability, and rule systems that bind low-power nodes while exempting high-power nodes.

Au-Actuation Gate

Requires sufficient traceability before high-impact action, control, enforcement, authority, or irreversible execution.

BΣ Validity

Checks consent, boundary integrity, identity edges, scope, reversibility, and exit capacity.

Λ Compatibility Gate

Checks whether coupling increases coherence rather than dependency, extraction, confusion, or hidden debt.

R Sufficiency

Checks whether restoration capacity exists before enforcement, repair demand, scaling, reintegration, or recoupling.

Τ Validation

Requires delay, recurrence, ring-down, and field effects before closure or recovery is claimed.

13. Glossary Governance Rules

13.1 Do Not Create New Terms When Existing Terms Suffice

Before adding a term, check whether it is already covered by an existing glossary term, registry entry, or construct.

13.2 Preserve Aliases Without Multiplying Canon

Some phrases can remain aliases without becoming separate canon entries.

Example:

Deferred incoherence → alias of Hidden Debt
Unpaid repair → alias of Hidden Debt
Proxy success → alias-related to Fitness Proxy

13.3 Use Canon Terms in Titles Where Possible

Registry entries should prefer canonical glossary terms to reduce drift.

13.4 Keep Domain Terms Anchored to General Terms

Applied terms should point back to the general architecture.

Example:

Biological Membrane → Membrane → Boundary → BΣ
Coherent Economy → Economy → Circulation → Restoration Capacity / Hidden Debt
AI Boundary Failure → Boundary Integrity / BΣ / AI Governance

13.5 Mark Deprecated Terms

If a term was used earlier but later corrected, it should be marked as deprecated rather than silently retained.

Example:

Deprecated: HR-Gate as Hard Rule Gate
Deprecated: HR-Gate as Harm / Responsibility Gate
Canonical: HR-Gate as High Risk Gate

13.6 Avoid Premature Metaphysical Locking

When terms touch consciousness, soul, spirit, archetype, sacred, or meaning, define them functionally within UTS while allowing broader interpretive layers.

Example:

Soul is a persistent coherence attractor expressed as continuity of selection-signature and meaning-signature across recurrence, with invariant boundaries preserved under stress.

This keeps the term usable inside the technical system without requiring one metaphysical doctrine.

14. Recommended Term ID System

Future machine-readable glossary entries should use stable term IDs.

Recommended format:

gloss-[kebab-case-term]

Examples:

gloss-coherence
gloss-hidden-debt
gloss-boundary-integrity
gloss-fitness-proxy
gloss-restoration-capacity
gloss-pseudo-coherence
gloss-high-risk-gate
gloss-feedback-integrity-gate

For symbols:

gloss-var-o-coherence
gloss-var-h-hidden-debt
gloss-op-gamma-selection
gloss-op-restore

15. Recommended Metadata Fields

A future structured glossary can use this field set.

term_id:
term:
canonical_name:
aliases:
symbol:
type:
status:
short_definition:
long_definition:
disambiguation:
related_terms:
source_modules:
registry_links:
examples:
anti_examples:
updated_at:
version:

This would support:

• frontend hover cards
• search filters
• graph visualization
• AI export
• glossary API
• module dependency mapping

16. Term Linking Model

Each glossary term should eventually support four link types.

16.1 Parent Term

The more general term.

Example:

Boundary Integrity → Boundary

16.2 Child Term

The more specific term.

Example:

Boundary → Consent Boundary, Membrane, Contract Boundary, AI Permission Boundary

16.3 Related Term

Terms that often interact.

Example:

Hidden Debt ↔ Restoration ↔ Inversion ↔ Pseudo-Coherence

16.4 Registry Link

The page where full treatment exists.

Example:

Metric Substitution → Failure Modes Registry
Truth Reconstruction → Restoration Arcs Registry
Slack → Diagnostics Registry
Γ → Operator Registry

17. Glossary Update Workflow

Recommended update sequence:

1. New module introduces term
2. Check glossary for existing term or alias
3. Determine term class
4. Draft compact definition
5. Add disambiguation if needed
6. Link to source module and registry
7. Check for canon conflicts
8. Assign term_id
9. Add to A–Z index
10. Add to machine-readable summary if core

For high-impact terms, add a review checkpoint:

Term affects gates, variables, consent, identity, AI governance, restoration, or failure classification
→ require canon review before locking

18. Completeness Criteria

A glossary pass is complete enough for archive use when it includes:

• all canonical state vector terms
• all core operators
• all U-layers
• all major gates
• all major diagnostics
• all registry names
• all common failure mode families
• all common restoration arc families
• major constructs and operating systems
• domain terms from active modules
• compact A–Z index
• machine-readable summary
• version and citation metadata

A glossary pass is not complete enough if it lacks:

• HR-Gate correction to High Risk Gate
• distinction between O and Φ
• distinction between stability and coherence
• restoration vs symbolic closure distinction
• diagnostics vs adjudication distinction
• U-layer definitions
• operator quick reference
• registry cross-links

19. Common Failure Modes of the Glossary Itself

The glossary can fail if it becomes either too thin or too dense.

19.1 Flattening Failure

Definitions become too generic and lose UTS specificity.

Example:

Restoration means healing.

This is too vague. Restoration must mean mechanical reduction of hidden debt and recovery of correction capacity.

19.2 Redundancy Creep

Too many near-synonyms become separate canon terms.

19.3 Module Drift

A module starts using a term differently without updating the glossary.

19.4 Symbol Drift

A variable or symbol begins to mean different things across contexts without explicit aliasing or disambiguation.

19.5 Domain Capture

A domain-specific usage becomes so dominant that the cross-domain term loses portability.

19.6 Over-Formalization

Every phrase becomes a canon term, making the glossary too heavy to use.

19.7 Under-Formalization

Important load-bearing terms remain informal, causing downstream inconsistency.

20. Recommended Website Implementation

The glossary should support three reader levels.

20.1 Simple View

A compact A–Z term list with one-sentence definitions.

20.2 Technical View

Grouped sections with definitions, symbols, disambiguations, and cross-links.

20.3 Machine View

Structured JSON/YAML export with term IDs, aliases, related terms, and source modules.

Recommended frontend features:

• search bar
• alphabet filter
• term class filter
• module filter
• symbol filter
• hover cards
• related-term graph
• copy citation button
• “used in modules” list

21. Recommended Machine-Readable Export Shape

glossary:
  title: "UTS — Glossary"
  version: "1.1"
  status: "Canon-Ready"
  terms:
    - term_id: "gloss-coherence"
      term: "Coherence"
      symbol: "O"
      type: "core-variable"
      short_definition: "Preservation of identity, meaning, and functional integrity across time under transformation."
      related_terms:
        - "Fitness Proxy"
        - "Hidden Debt"
        - "Restoration"
      source_modules:
        - "Core Model"
        - "Coherence"
    - term_id: "gloss-high-risk-gate"
      term: "HR-Gate"
      canonical_name: "High Risk Gate"
      type: "gate"
      short_definition: "Gate preventing high-risk binding or high-impact classification under insufficient evidence, weak auditability, or invalid boundary conditions."
      deprecated_aliases:
        - "Hard Rule Gate"
        - "Harm / Responsibility Gate"

22. Integration With Future Tools

The glossary can support several future tools.

22.1 Hover Definition Engine

Displays short definitions when terms appear in modules.

22.2 Construct Graph Generator

Uses related-term links to map conceptual dependencies.

22.3 Registry Cross-Linker

Automatically links glossary terms to failure modes, diagnostics, invariants, laws, and restoration arcs.

22.4 AI Context Builder

Exports only the glossary terms needed for a given module, keeping AI context precise.

22.5 Term Drift Detector

Compares new documents against canonical definitions and flags usage drift.

22.6 Public Reader Pathway

Builds beginner-friendly reading sequences by term dependency.

23. Glossary Position in the Archive

Recommended placement:

/archive/glossary
/archive/glossary/technical-overview
/archive/glossary/machine-readable
/archive/glossary/simple
/archive/glossary/advanced

The glossary should be linked from:

• Core Model
• Notation
• Operators
• Diagnostics
• Invariants
• Laws & Scaling Rules
• Failure Modes
• Restoration Arcs
• Constructs
• every major module landing page

24. Canonical Summary

The UTS Glossary is the semantic infrastructure layer of the Universal Theory Stack.

It defines the project’s recurring terms in a way that supports human readability, machine-readable indexing, registry alignment, website navigation, cross-module coherence, and terminology drift prevention.

It should preserve the core UTS distinctions:

• coherence is not fitness proxy
• stability is not coherence
• signal is not truth
• diagnostics are not adjudication
• consent is structural
• restoration must reduce hidden debt
• gates determine admissibility
• U-layers localize origin and repair
• time validates claims

The glossary should remain compact enough for lookup, structured enough for tools, and precise enough to preserve canon across the expanding archive.

25. Machine-Readable Summary

glossary_technical_overview: "UTS — Glossary Technical Overview"
version: "1.0"
status: "Canon-Ready"
type: "technical-overview"
primary_function: "Defines the purpose, architecture, term classes, governance rules, integration points, and update workflow for the UTS Glossary."
core_functions:
  - "reader orientation"
  - "cross-module consistency"
  - "registry alignment"
  - "website infrastructure"
  - "AI-readable alignment"
  - "terminology drift prevention"
  - "translation layer"
term_classes:
  - "core variable"
  - "operator"
  - "diagnostic"
  - "gate"
  - "pattern"
  - "failure mode"
  - "restoration arc"
  - "construct"
  - "applied domain term"
protected_distinctions:
  - "coherence_vs_fitness_proxy"
  - "stability_vs_coherence"
  - "signal_vs_truth"
  - "diagnostics_vs_adjudication"
  - "consent_vs_procedural_permission"
  - "restoration_vs_symbolic_closure"
  - "growth_vs_expansion"
  - "auditability_vs_trust"
  - "force_vs_restoration"
  - "ai_performance_vs_ai_coherence"
canonical_gate_note:
  HR_Gate: "High Risk Gate"
future_tool_support:
  - "hover definitions"
  - "construct graph generation"
  - "registry cross-linking"
  - "AI context builder"
  - "term drift detector"
  - "public reader pathways"

26. Citation

Suggested citation:

Universal Theory Stack. “UTS — Glossary Technical Overview.” Version 1.0. UTS Technical Archive, 2026.

Citation ID:

uts-glossary-technical-overview-v1-0

Target path:

content/archive/glossary/technical-overview.md