Glossary
Every word CTXR uses, one line each, alphabetical. A line says what the word means here and points to the page that owns it; the page carries the reasoning. When two words look alike (person and actor, draft and preview, theme and assets), this is the place that tells them apart.
A
Actor — who may write to a site: rights plus a way in — a key (an agent’s) or an address (a person’s: the site mails a one-shot link, the authenticator unlocks writing). Lives in .actors/, never public. Not a person on the site (see Person). → Who can do what
Assets — the root of files that are served as-is: images, fonts, video, PDF, and the theme’s css and js. /assets/… is static, cheap and cacheable. → Styling and assets
Audit — the check that judges a site before anything goes live: references, required fields, the page register, links, theme syntax. Runs on every publish. It judges the site. → Drafts and going live
C
Cornerstone — an engine-served page that is not content: the wall (/admin), /graph, /offline, /install. A theme file of the same name takes one over. Only pages; the app’s files are claimed by the engine. → What your site serves
D
Data — the root of entities: one JSON file per thing, Schema.org-shaped. Served as it lies on disk under /data: the file at /data/<type>/<id>.json (the source), its reading at .md, the index above it — public and crawlable by construction. → Data conventions
Docs — the CTXR documentation, these pages. In a site read through the MCP with any key — search { in: "docs" }, fetch "docs/<path>.md" — never at a URL. The knowledge lens an agent reads after the guide. → Keys and the MCP
Draft — a staged change: a file written through the MCP that is not live yet. Every root has a draft layer beside its live layer. → Drafts and going live
E
Engine — the code that renders a site: one copy per site, generic, never edited on a site. → The theme layer
Entity — one thing on the site as one JSON file: a service, an article, a person, a page. An entity with a slug is a page — a list (an itemlist) never is: it is curation. → What a CTXR site is
F
Feed — /feed.xml: new content as it goes live, for readers and for services that watch the site. → What your site serves
Forms lane — the one door without a key: a visitor’s form post, judged by origin and stored in .inbox/. → Forms and what your site receives
G
Gate — the way a site is written: the MCP, each write behind a key. → Keys and the MCP
Guide — the root of the site’s own knowledge for agents: flat markdown in guide/, read through the MCP only, never served. → Work rules for agents
H
Home — the designated entity data/webpage/home.json, served at /. → Pages and languages
I
Identifier — an entity’s name inside its type: data/person/joey.json has identifier joey. Stubs point at it. → Data conventions
Index — the projection of every live entity: /data.json, the full form as one Schema.org DataCatalog (one Dataset per type; /data/<type>.json per type), and /data.md, the same index as a list — identifier, name, address, one line. ?q= searches either: ranked hits with snippets, cursor-paged; the content lens for agents. → What your site serves
Invite — the one-shot link a site mails to an actor’s address (/edit#invite=<token>, ten minutes, gone on first use): it opens the edit client for reading. Sent by the owner, it also lets the person enrol their authenticator; asked for on the door, it reads only. → Who can do what
J
Journal — the timeline of what happened to a site and who did it: every publish, every key, every note. Names the actor, not the person. → History and undo
K
Key — see Actor.
L
Language map — a field written per language, {"en": "…", "nl": "…"}, that the engine resolves for the page’s language. → Strings and languages
Live — what the public sees; the layer a publish writes to. → Drafts and going live
llms.txt — the projection that lists the site’s pages with titles and URLs; the breadth lens. → What your site serves
M
Manifest — the app’s identity for a device: name, icon, colours. Derived by the engine at /manifest.json from the organisation and the theme colours; claimed by the engine, no theme file. → An app by default
MCP — /mcp, the gate for agents: fetch, search, create, update, publish and the rest, each behind a key; /edit rides on it too. → Keys and the MCP
N
Note — the optional text a write verb carries through the MCP: what was asked, in the caller’s words, landing on the journal line. → Keys and the MCP
O
Overview — a page that lists other things (a blog index, a menu): its template asks for the rows of a type or of a curated list (rows()) and shapes them; the rows point at the entities, they copy nothing. → The helpers you have
P
Pack — a zip of a site’s content roots, made through the MCP, for a local copy or a move. → Keys and the MCP
Person — a Schema.org Person in data/person/: someone named on the site — an author, a reviewer, a team member. Content, public. Not a user: keys are actors, and the two never reference each other. → Who can do what
Portable — a site is a folder; the same engine renders it anywhere, and an update replaces the engine without touching the site. → Portable by design
Preview — viewing drafts as if live, through a token the MCP hands the writer. → Drafts and going live
Projection — a view the engine derives from the files on request and caches: llms.txt, the index, sitemap, feed, robots. Never a copy, never edited. The list: What your site serves; the why: Projections, never copies
Publish — promoting a draft to live, after the audit. → Drafts and going live
R
Root — one of the four folders of a scope, each holding one kind of file: data/ (json), assets/ (media, css, js), theme/ (templates), guide/ (markdown). → The theme layer
S
Scope — the folder a site serves from (public/): the four roots the engine keeps. → The theme layer
Scope check — the engine’s definition of what may exist in a scope: which roots, which extensions, which content. Every write passes it first. → Styling and assets
Search — the MCP verb opposite fetch: fetch reads one file, search reads a root — in: data, docs, theme, assets or guide — and answers with ranked hits and a snippet, never a body; layer: live | draft | both says which layer, each hit says its layers. The same motor serves ?q= on the index (live only). → Keys and the MCP
Service worker — the small program a browser keeps for the site once it is installed: it holds pages and assets on the device and serves them when the network is gone. Served by the engine at /sw.js; claimed by the engine, no theme file. → An app by default
Shell — a template: the PHP file that renders an entity into a page. Resolved by type, down to a universal floor. → How a page finds its shell
Sitemap — /sitemap.xml: the crawler index of the pages, per language; lists exactly what exists. → What your site serves
Slug — an entity’s URL path (or a language map of paths). An entity with a slug is a page — except a list, which claims no address. → Pages and languages
Stub — a reference from one entity to another by type and identifier, resolved on read. → Data conventions
T
Theme — the root of templates, sections and snippets: the site’s form. Never served; its css and js live in assets/. → The theme layer
U
Unpublish — taking a live file back to draft; reversible, and the way to retire something. → Drafts and going live
W
Wall — /admin: the page that explains the site is managed through an agent, and lists the public lenses. Not a dashboard. → No dashboard