the colophon

Credits, typography, color, the framework as design instruction, the refusals with their apparatus citations, reproducibility. The colophon documents what the site refuses, and why. The framework critiques attention-capture; the site refuses the UX patterns the framework critiques.

Distinct from the v1 colophon (at /closed-loop/colophon), which is preserved as historical artifact.

Credits

Author: Adnan Selimović. Apparatus design: A. Selimović with collaborator contributions documented in the manuscript's bibliography. The site is built atop the v1 closed-loop rebuild; the v2 work cataloged at /closed-loop/the-apparatus renders the formal apparatus from the canonical manuscript against the new performative-prediction spine.

Typography

EB Garamond for body prose. JetBrains Mono for operational and labeling work — section breadcrumbs, formal-block labels, plate controls, axis labels in figures. Both self-hosted under /fonts/; no external font-CDN call.

Color

A six-color palette. Each color carries theoretical or operational meaning across the site:

  • cream — the unforeclosed substrate; page background.
  • warm-ink — the operational ground; body text, primary curves.
  • oxblood — foreclosure intensity; chrono-debt regions; the contractivity boundary; visited links.
  • fog — secondary text; pre-closure baseline curves.
  • slate — Mode A intervention sites; the cooler register.
  • moss — reflective intervals when marked positively; Mode B; the unforeclosed region in chrono-debt plots.

Color carries information but never carries information alone. Pattern, shape, position, and labels carry redundantly (WCAG AA + accessibility commitment).

The framework as design instruction

The framework critiques attention-capture; the site refuses the UX patterns the framework critiques. The refusals below are theoretically grounded — each pattern is refused because the apparatus formalizes the mechanism the pattern instantiates. The site's politics are applied to its own hosting.

Reading the colophon as a substantive document: each refusal cites the apparatus result that licenses it. The framework is inseparable from its presentation.

The refusals

Forward-motion and attention-capture refusals

These instantiate the closed-loop optimization the framework critiques — they drive the reader toward continued engagement or compress reading into consumption.

  • No analytics (Google Analytics, Plausible, Fathom, segment.io, server-side event logging).→ Lemma 1
  • No "next chapter" or "continue reading" buttons at the end of any surface.→ §5 + §7
  • No completion progress bars for reading, watching, or scrolling.→ §3.5
  • No estimated read times.→ Lemma 1
  • No reading-history badges ("unread," "new since your last visit").→ §3.2 Prop 5'
  • No "you may also like" or related-articles recommendations.→ §3.5 + §8
  • No autoplay of any media — video, audio, animation.→ Prop 6
  • No infinite scroll, no lazy-loading of next sections, no autoplay-next.→ Lemma 1
  • No notifications — browser push, in-page badges, unread counters.→ Prop 7' + §3.5

Anticipatory-interface refusals

These instantiate the dividual posterior reading the reader before the reader has acted.

  • No predictive search, no auto-suggest, no type-ahead.→ Prop 4'
  • No hover-states that telegraph clickability before deliberation.→ Prop 4'
  • No optimistic UI — no pre-rendering of state changes before they are confirmed.→ Prop 4'
  • No personalization based on browsing history, geolocation, or any reader characteristic.→ §0 Definition 0.1

Persistent-presence and state-accumulation refusals

These instantiate the metric superego's constant evaluative gaze and the cohort-formation substrate the framework formalizes.

  • No sticky nav bars, floating action buttons, persistent footer CTAs.→ Prop 5'
  • No localStorage, sessionStorage, or IndexedDB usage for reader-specific state.→ Prop 4'
  • No accounts, no sign-up, no login.→ Prop 4'
  • No persistent reading list, no "saved for later," no "continue where you left off."→ Prop 5'
  • No view counts, like counts, read counts displayed to the reader.→ §3.5 + §8.4

Engagement-aesthetic refusals

Visual or interaction patterns that signify SaaS/platform optimization even when not technically driving engagement.

  • No skeleton loaders or shimmer effects.→ §3.5
  • No micro-interactions for delight — hover bounces, click ripples, success confetti.→ design system
  • No emoji in navigation, headers, or button labels.→ design system
  • No gradient buttons, glass morphism, neumorphism, SaaS visual language.→ design system
  • No dark-mode toggle. Dark mode follows the system preference.→ Prop 5'

Cross-register-routing refusals

These instantiate libidinal routing — the cross-register coupling the framework formalizes as the closure's relational form.

Voice and marketing-register refusals

Copy patterns that simulate intimacy, manufacture urgency, or smuggle in the marketing register.

  • No urgency framing — "limited time," "act now," "join now."→ §3.5
  • No social-proof framing — "readers love this," "thousands have read," "trusted by."→ §3.5 + §8.4
  • No "we" speaking to "you" in marketing register.→ Prose Writing Charter
  • No SEO-optimized writing that distorts voice for keyword density.→ Prose Writing Charter

What survives

The site does have UX. The refusals carve out what remains:

  • Static URLs that are stable and citable.
  • Anchor links to headings and to apparatus results.
  • Plain hyperlinks with explicit text.
  • Underline-on-hover as confirmation of an action chosen.
  • Keyboard navigation for every interactive element.
  • Visible focus indicators in the cream / warm-ink / oxblood palette.
  • Five navigation hubs — the architecture figure, the apparatus index, the dynamics plates, the instruments, and the glossary.
  • Plates with controls the reader operates — sliders, dropdowns, pause/step/replay.
  • Equations rendered with KaTeX, configured for screen-reader compatibility.
  • Theme that respects prefers-color-scheme.

Reproducibility and source

The site lives at github.com/acephalous77/closed-loop-libidinal-economy. The v2 rebuild lives on the v2/closed-loop-rebuild branch.

The apparatus content is rendered from a canonical manuscript source. Substantive changes to the apparatus flow upstream from the manuscript; the manuscript is the source of truth, and the site is its rendering.

v2 closed-loop.