cx
the front door: pins every repo, builds the four cx builds and libcx-core/libcx, holds the site, the release, the installer
Why reach for it
We keep one front door. cx is the tree that pins every
repository of CX at a sha, builds the four builds of one binary from
those pins, and serves this site. You install from it, you read from
it, and every change to CX arrives through it: a pin moves only when
the newer set passes together.
A pin is a sha, never a branch, and deps.cxd is the one place a pin
is written: make deps-sync fetches each pinned repository into
deps/ and refuses a stale pin or a drifted checkout out loud
rather than warning. The status table below is that document read
back — what the front door builds on is the whole pin list, and the
figure's left column draws it.
From those pins we build the four builds of cx — data, embed,
cli and platform — the same binary name with a build-decided
surface, so you take on only as much of CX as you need
(rings is the map; the downloads page lists the four). The
release, the installer this site's one-liner fetches, the guide and
the primer are built here too, from the pinned corpora, so an example
on any page of this site was replayed against the binary the same
tree produced.
What it gives you
No module of the language lives in the front door: every bundled module is pinned in from the repository that owns it, which is why the table below is empty and the plug-in figure's left column is long. What the front door gives you is the assembled binary, the site, the release and the installer — and one contract, that flags bind before the file.
This repository ships no bundled module of its own; what it gives you is above, and its links are below.
Try it
The run surface is cx [flags] FILE [args…]: everything before the
file is ours, everything after it belongs to the program. The case
below is the corpus's own statement of that rule — the grant before
the file, and the program reading what it was granted.
prog.cx
[?lib 'cx-stdlib/env' as=env]
[probe args=[$count [$env:argv]] home=[$env:var-or-default 'CX_PRIMER_ABSENT' 'unset']]
$ cx --allow-env prog.cx
[probe args=1 home=unset]
Fixture ap-flags-after-file-right in conformance/llm/antipatterns.cxd — replayed against this cx when the page was built.
Status
The front door is not pinned by anyone — it is the root that pins the rest. Its repository is public; the pins it names are private until the release cut.
| fact | as the registry records it |
|---|---|
| ships as |
binary
|
| status | the front door — the tree this site was built from |
| pinned at | not pinned — it pins the others (deps.cxd) |
| builds on | cx-platform-agent, cx-platform-ux, cx-platform-workbench, cx-platform-sso, cx-platform-flow, cx-core-data, cx-core-code, cx-platform-db, cx-platform-net, cx-platform-mail, cx-platform-store, cx-platform-identity, cx-platform-connector, cx-platform-secrets, cx-platform-fabric, cx-platform-xsp, cx-platform-xap |
| built on by | nothing pins it yet |
| bundled modules | 0 |
cx plugs into: the repositories it builds on (left), the modules it ships (centre), the repositories that build on it (right) · drawn from registry/repos.cxd, deps.cxd and registry/modules.cxd when this page was builtLinks
- github.com/cx-home/cx — the repository
- README — what it is, how to install it, what it pins
-
spec/03-approved— the specification, the only truth -
conformance— the conformance corpus, the executable truth