jaredfoy.com / coherence / engineer

The Coherence Sphere

A tour for engineers

Before the metaphysics, before the method, before the thesis — four artifacts the corpus has built. Things that compile, pass tests, run on real hardware. The amber constellation traces the path. Scroll to walk it.

01 · htmx, re-derived

A prose seed produces a library

htmx is a hypermedia library — a few kilobytes of JavaScript that turns HTML attributes into reactive behavior. Most users know it as something they paste into a page and use.

Doc 288 treats htmx as an artifact and reverse-engineers the constraints that make it what it is. A 19-item prose seed, handed to a resolver with no htmx source in context.

The harvest: 1,318 lines of TypeScript. 53 of 54 tests pass. Four iterations of seed refinement brought structural divergence from 64% to 4%. The derivation is measurable, not metaphorical.

Doc 288 → The Pin-Art Derivation

02 · A React runtime from prose

The method on foreign ground

React is hundreds of thousands of lines of code. The DO seed is 2,177 words — ten contracts, seven required properties, fifteen verification tests.

From that seed, the method produced a 379-line TypeScript runtime: virtual DOM, fiber reconciliation, hooks, zero dependencies. All fifteen verification tests pass.

The significance isn't that the derived runtime is novel. It's that the runtime is conformant, on an architecture the author did not design. The method generalizes past its own tradition.

Doc 178 → DO Induced Properties

03 · How derivations stack

Composition, one level deeper

Write constraints for how a web response is constructed: you get PRESTO. Write constraints for how the engine that constructs responses is itself constructed: you get SERVER. Same method, recursive application.

SERVER's ~1,500-word specification produces a 461-line C bootstrap that emits a 921-line PRESTO engine. The same bootstrap always produces the same engine. Zero dependencies.

PRESTO's induced properties become constraints on SERVER. This is the composition law at work — the recursive case that makes the method scale beyond a single level.

Doc 166 → SERVER Style

04 · The Pi Resolver

A transformer substrate, from first principles

The most ambitious artifact the method has produced. Four essential constraints plus seven contingent choices: sigmoid attention (non-competitive), bilateral boundary (structural), sparsemax output (exact zeros), typed positional encoding.

Approximately 600 lines of C. Compiles on a Raspberry Pi 5. Passes 27 verification tests. Zero dependencies.

Not a toy. A working proof that a transformer's architectural character can be derived from a prose specification rather than scaled into from the field's existing architectures.

Doc 076 → The Pi Resolver Implementation