4 MIN READ•findings

Readability Before Expansion

A finding from the Forge Readability Stabilization (Slice 16).

Typography is infrastructure, not decoration. Before adding features, before wiring providers, before expanding architecture — make the room readable.

The Problem

The Forge suffered from what can be called semantic compression overload:

Dense monospace text at tiny sizes (10px everywhere)
No typography hierarchy — everything looked the same
Body text in monospace, where proportional fonts would be more readable
Navigation with 8 items at 13px with tight wrapping
No mobile readability baseline
Inline text-[10px] and text-[9px] classes scattered across every page

The forge was dense by design — that is its soul. But density without readability creates fatigue, not atmosphere. The monastery-forge should feel like a place of focused work, not a wall of unreadable glyphs.

The Principle

Readability is a prerequisite for operational clarity.

A forge that cannot be read cannot be used. Before the operator can shape intents, ward semantics, or generate manuscripts, they must be able to read the room.

This means:

Body text at readable sizes — never below 14px for important reading text
Proportional fonts for body — monospace is for metadata, sigils, and coordinates
Clear typography hierarchy — headings, body, metadata, and labels should be visually distinct
Generous line-height — dense text needs breathing room
Mobile baseline — the forge must be readable on small screens
CSS custom properties — typography scale defined once, consumed everywhere

The Typography Scale

| Token | Size | Usage | |-------|------|-------| | --forge-text-xs | 11px | Metadata, labels, mono details | | --forge-text-sm | 12px | Small labels, timestamps | | --forge-text-base | 15px | Main body manuscript text | | --forge-text-lg | 18px | Section headings | | --forge-text-xl | 22px | Major page titles | | --forge-text-2xl | 24px | Hero titles | | --forge-leading-base | 1.7 | Body line-height | | --forge-leading-tight | 1.3 | Heading line-height |

What Changed

All inline text-[10px] and text-[9px] classes removed from every forge page
Body text set to 15px proportional font throughout
Metadata/labels at 11-12px monospace
Navigation items at 12px
Section headings at 18px
Page titles at 22px
New CSS utility classes for sections, data panels, manuscript previews, chamber rooms, phase indicators, tabs, wards, buttons, and shell banners
Single mobile breakpoint at 640px
Grids collapse to single column on mobile
Never below 14px for important reading text

What Was Preserved

The forge remains black-and-white. No color was added. No gradients, no shadows, no SaaS styling. The dense manuscript atmosphere is intact — it is now readable density rather than fatiguing density.

Monospace is preserved for:

Metadata and labels
Timestamps and coordinates
Sigils and ritual notation
System messages and status lines
Code and configuration

Proportional fonts are used for:

Body manuscript text
Section descriptions
Navigation items
Button labels
Most panel content

Relationship to Forge Philosophy

The forge manuscript atmosphere is not weakened by readability. It is strengthened.

A manuscript that cannot be read is not a manuscript — it is a wall of ink. The forge is a place of focused, deliberate work. Readability is the foundation of that focus.

This finding aligns with the broader forge philosophy:

Atmosphere is infrastructure, not decoration
Density without readability is noise
The operator must be able to read the room before shaping the work

What This Enables

With readability stabilized, the forge can now support:

Longer operator sessions without fatigue
Mobile inspection and quick checks
Clearer distinction between metadata and content
Easier onboarding for new operators
Future expansion without readability regressions

BOOKCASE