Sheet 01 · The ring model
Four rings.
One contract.
Agentic ready.
CX is one language for data and code — the same bracket form is a document, a schema, a query, and a program. How much of it you take on is a ring: Ring 0 is a data format that cannot execute anything, each ring outward adds exactly one commitment, and imports point inward, never out. The contract is machine-checked.
R0Datadocuments · schemas · values
R1Codeevaluation · deny-by-default capabilities
R2Platformthe store · transports · live surfaces
R3Ecosystemtooling · packs · the catalog
Fig. 1 — four rings, one-directional import contract
Table of contents
Start here
Ring 0 — Data
Ring 1 — Code
- 6 The code language
- 6a Computation identity
- 6b Commands and effects
- 6c How a value is represented at runtime
- 15 50 Ways to Love Your CX Programs
- 16 Capabilities and permissions
- 16a Code tooling
- array
- bytes
- crypto
- csv
- diagram
- env
- format
- fp
- ft
- geo
- hash
- html
- i18n
- io
- json
- jsonrpc
- jsonschema
- locale
- log
- map
- math
- mime
- path
- process
- prof
- random
- re
- sched
- similar
- strings
- supervise
- test
- time
- url
- uuid
- validate
Ring 2 — Platform
- 17 Operations
- 18 The store platform
- 18a Time: valid time and transaction time
- 18b Consistency, in the words we use
- 18c Event evolution
- 19a Projected surfaces — the ux capability
- authz
- bus
- did
- fabric
- http
- journal
- live
- net
- session
- store
- vc
- xap
- xsp
- Overview
- D1 · Greeting CLI
- D2 · Guestbook (the cascade)
- D3 · Guestbook on the web
- D4 · Guestbook + agent
Ring 3 — Ecosystem
x/ tier — experimental
Reference
Source: docs-src/canonical/sections/*.cxd +
the co-located docs in stdlib/*.cx and x/*.cx. Built by
make guide.