Colophon
A site that argues for maintainability should be able to describe its own construction without embarrassment. This is that description — and, at the end, the shape of the platform it describes.
A Markdown pipeline means a parser, a sanitiser, and a build step, and it moves content errors from compile time to render time. Typed content blocks give the compiler the chance to catch a malformed entry and keep the browser bundle free of a renderer it does not need. Inline markup is limited to bold, italic, code, and links — parsed into typed runs and rendered through template bindings, so authored content never reaches innerHTML.
Scroll reveals are applied at runtime by a directive. The prerendered HTML contains fully visible content, so a crawler, a reader with JavaScript disabled, or anyone whose bundle failed to load still gets the page. The usual arrangement — hide in CSS, reveal in JavaScript — makes content invisible exactly when the enhancement fails.
Every reading estimate on a record is computed from the actual word count of the rendered blocks. It is a small thing, and it is the same principle as the status labels: a number on a page should be something the system knows rather than something someone typed.
Six layers, from hardware on the wire up to the surface a person talks to. The platform owns what everything needs; modules own one concern each. A module may depend on the platform — the platform may never depend on a module.
Select a component for detail. Every node states how far along it is.
Where a person meets the system.
One functional concern each. Removable without a migration.
What every module needs and none should implement itself.
The machine, the container runtime, and the single way in.
How state and commands move between devices and services.
Physical hardware that produces state and accepts commands.
No component selected
Every project, layer, and capability on this site carries a state: operational, in progress, experiment, planned, or concept. They are not decoration. They exist so that a reader can tell what runs from what is designed, without having to guess which sentences are load-bearing.
There are no metrics on this site, no uptime figures, and no customers, because there is nothing honest to put in those places. Argus is a specification with real infrastructure underneath it. When that changes, the labels change.