# The Rules

Through the autumn and into the winter, the rules grew. Seventy-eight of them by the end. A web of guidance, cross-linked and navigable, that encoded everything I had learned in twenty years of building software and everything the project had taught me in its first six months.

## The Web

The rules lived in .cursor/rules/, and they were the first thing the AI agent read at the start of every session. Each rule was a file — a focused, actionable document that covered one domain. Design system colors. Design system typography. Dark mode. Database conventions. Security headers. Rate limiting. Dependency scanning. Observability patterns. Error capture. Logging standards. Internationalization. Testing. Documentation. Deployment. API conventions. Authentication flows. The content management system. The email system. The analytics layer. Each rule was a lens, and together they formed a kaleidoscope: every aspect of the platform, viewed from every angle, documented and cross-referenced.

The cross-referencing was deliberate. Each rule linked to the rules it depended on, the rules it reinforced, the rules that provided context. The design system rules pointed to the typography rules. The typography rules pointed to the internationalization rules. The internationalization rules pointed to the content management rules. The web was navigable — an agent could start anywhere and follow the links to understand the full picture, the way a reader follows footnotes through a library.

Four rules were marked alwaysApply: true. These loaded on every session, without being asked, because they were the constitution. The soul rule — who Malaika is. The user rule — who the architect is, what he cares about, who he is building for. The memory rule — the accumulated context, the decisions made, the direction committed to. The orchestration rule — how the work flows, how the agent and the human collaborate, what the defaults are. These four rules were the identity of the system, loaded into the agent's context at the start of every conversation, so that every session began with a shared understanding of who we were and what we were doing.

## The Design System

The design system went through six iterations. The first five were external — produced by a design agency, delivered as Figma exports and HTML mockups. Each iteration refined the previous one: the first was the base, the second added chat and content interaction screens, the third added five more files, the fourth added eleven, the fifth was the most complete, with home and library and settings canvases, a master tokens stylesheet, and a full component library.

The sixth iteration was mine. I called it self-authored.

The self-authored design system was where I stopped receiving design from outside and started producing it from inside. It was smaller than the agency versions — fifty files instead of three hundred — and it was denser, every file load-bearing. Nine atelier notes, each one a dated design-decision journal. The first: right-body layout and fast search. The second: pretext as canonical chat. The third: voice composer glyph wiring. The fourth: slash commands as verb plane. The fifth: home, pocket, and telegram parity. The sixth: linear rollback. The seventh — one hundred and fifty-three kilobytes, the largest — revenue, ad card, and the dreamteam block.

Forty step-PRs. Step twelve through step forty-seven, each one a small, reviewable, reversible change to the design system. Step twelve was "closing the system." Step seventeen had a critique file and an activity stream. The steps built on each other the way a house is built: foundation, frame, walls, windows, finish. Each step was small enough to review in one sitting and reversible enough to undo without damage.

This was the generator principle applied to design: small, perfectly-made components, arranged with care, built to last. The self-authored design system was the moment the platform's visual identity became something I owned, something that came from the same mind that wrote the rules and the code and the creed.

## The Self-Authored

The aesthetic that emerged was specific and it was warm. Danish Modern — the furniture movement, the idea that beautiful things should be functional and functional things should be beautiful. Warm paper tones instead of cold white. A color palette built on burnt sienna — the orange-red of terracotta, of autumn, of the embers of a fire. Dark mode first, because the platform was read at night, and the night deserves a surface that does not blind.

The typography carried meaning. The wordmark — the logo, the name rendered in type — was designed to hold Hopkins and Rumi at twenty-two seconds per cycle. Gerard Manley Hopkins, the Jesuit poet of the nineteenth century, whose poetry is so dense with alliteration and stress that it feels like music. Rumi, the Sufi mystic of the thirteenth century, whose poetry is so spacious with longing that it feels like prayer. Two poets, seven centuries apart, held in the shape of the letters that spelled the name. The wordmark was a poem itself, a compressed allusion to the literary tradition the platform served.

The navigation breathed. A subtle pulse, like embers, like a heartbeat, that signaled presence without demanding attention. The design called it the ember-breathing nav. It was the visual equivalent of a librarian who is always there when you need her and never intrusive when you do not.

The self-authored design system was the craft layer of the project. The rules were the engineering layer. The database was the data layer. The ingestion pipeline was the logistics layer. The voice system was the communication layer. And the design system was the layer the user actually saw — the surface where all the engineering and the data and the logistics and the communication became an experience that felt like entering a room where someone had been expecting you.

By the end of the winter, seventy-eight rules governed the codebase. Six iterations of the design system had been produced. The self-authored version carried forty step-PRs and nine atelier notes. The web of rules and the craft of design had converged into something coherent, something that could be handed to another person and understood, something that reflected, in every detail, the conviction that beauty and function are the same thing and that both serve the reader.

The seventy-eight cursor rules are preserved in the archive, along with the complete self-authored design system — nine atelier notes and forty step-PRs. The design system iterations (base through five, plus self-authored) are documented in the era-03 and era-04 archive folders. The wordmark description — "Hopkins and Rumi at 22 seconds per cycle" — is from the sovereign-vision document. The ember-breathing nav is from the same source. The aesthetic principles (Danish Modern, burnt sienna, dark-mode-first) are documented in CLAUDE.md and the impeccable.md design context file.