UCXL, or the Unified Context eXchange and Linking, is a comprehensive protocol architecture designed for addressing, managing, and sharing semantic contextual resources within its ecosystem. It establishes a 1:1 mapping between traditional file system structures and contextual metadata, which facilitates knowledge preservation, distributed AI development, and complex context management. UCXL functions as a layered protocol, supporting context messaging, transport, and semantic context sharing through components such as validators and browsers that aid in context resolution and organization.

The core purpose of UCXL is to enable semantic addressability and logical content organization within a distributed system. It provides a time-aware address space that supports temporal navigation and concept mapping, allowing for precise retrieval and management of context data. UCXL can store and organize data, decisions, and reasoning in organization-based structures, ensuring the persistence and traceability of complex semantic information.

Key technical features include an address format that uses URI-like schemes (e.g., `ucxl://agent:role@project:task/#/path`) with components like agent, role, project, task, temporal segment, and resource path. It also supports operations such as GET, PUT, POST, DELETE, NAVIGATE, QUERY, and SUBSCRIBE within the UCXI interface, enabling robust context management and dynamic interaction. The protocol is integral to the broader ecosystem, working in conjunction with components like UCXL Browser, Validator, Address Parser, and the supporting infrastructure of the UCXL Foundation, all aimed at enhancing knowledge preservation, decision tracking, and semantic interoperability in distributed AI environments.

**Scope-aware access:** UCXL addresses bind **agent/role → project/task → temporal slice → path**, so policy can be evaluated _at resolution time_ rather than after retrieval. This is the backbone of our least-privilege, time-bounded lookups.

**Contracts via addresses.** Teams publish stable UCXL addresses for consuming systems; producers can evolve internals without leaking. Temporal operators (`~~`, `^^`) let consumers pin decisions without chasing moving targets.



**References:**

- [KG] 1 (from Entity: UCXL)
- [DC] ucxl_protocol.md

## TODO

- Spec + validator: Publish current spec references and ensure the validator enforces them across languages.
- Syntax tools: Build out `ucxl-syntax-plugin` (currently empty) and align behavior with the VSCode extension.
- Governance: Define address lifecycle/contracts (examples for producers/consumers) and cross-module examples.
- Conformance: Create a test harness that runs against RUSTLE, CHORUS, WHOOSH, and the validator for end-to-end checks.
