Authoring
Diffuse the whole Work, not loose fragments.
Author your Work once and diffuse it everywhere without it fragmenting. A Work — a book as archetype — is modeled as a coherent authored whole (a Central work with Satellites and Elements) carrying six typed content types; the same source projects to print, digital, web, interactive and an AI-queryable surface (RAG/MCP). Dissemination is an expression of the Work across channels, never a re-authoring per channel — so the Work stays coherent everywhere it appears.
An authored Work lives as source files (Pages, ODT, Markdown). Each medium — print PDF, EPUB, web, interactive, AI-queryable — is produced by a separate ad-hoc pipeline, so the Work is re-cut per channel and drifts: a correction in the book never reaches the web, the glossary diverges between formats, and the same content is maintained N times.
The root cause is that no tool holds the Work as ONE coherent authored whole with a declared expression across channels. Authoring tools target one output; CMSs compose upward from fragments. So coherence — the very thing that makes it a Work and not a pile of pages — is exactly what is lost the moment it is published to more than one medium.
ontoref · opus
What it is
Opus is the domain of an authored Work. The Work is the production; the book and the logbook are its spaces, and print, digital, web, interactive and RAG are expressions of a space — downstream of it, never its definition.
Why
A Work cut again for each channel drifts: a correction reaches one medium and not the next, and the same text is kept N times. Held as one authored whole, with every channel an expression of it, a correction in the book and on the web is the same correction.
What for
A Work's workspace takes the domain's components whole — each with its contract, its defaults and its words — and writes over only what it chooses. The catalogue below is what exists on disk; a component is declared only once it does.
Architecture
The catalogue and what leans on what
Hover or tap a component, or pick a card below, to see only its relations; a picked card keeps its route on the map until it is picked again. A relation is a path dependency between the crates each component names.
The catalogue
Taken whole, written over only where chosen
Workflow
A Work, from its source to its reader
From the source to the reader: what the machinery keeps of every decision taken over a Work. A person edits, confirms and decides; the checks judge and never become a source; a copy leaves for a third party only as a recorded dispatch.
Components read from the opus domain's catalogue and relations from its provider's Cargo workspace when this page was generated; every step cites the opus decision that governs it.
The prize, once inside
When your reason for being is verifiable and not just declared, holding your course stops costing effort.
· reads
Perspectives