Signal Press

The reference succeeded by refusing options

The hero above Cursor's article about agent swarms is built from a remarkably small vocabulary. A stable field of short marks bends into local currents. Most marks stay warm white. A sparse orange signal moves through the system. There is no label inside the image, no simulated depth, and no attempt to illustrate an agent literally. The image works because its visual rule and the article's subject agree: many small actions acquire meaning through their relationships.

That restraint mattered more than the exact algorithm. Copying the muddy background, orange accent, regular lattice, and motion path would preserve the surface while losing the judgment. Signal Press instead borrowed the editorial constraint. Each mode gets one mark grammar, one compositional job, and one semantic use of accent color. The goal is not to manufacture infinite novelty. It is to make a bounded set of defaults that are already fit for publication.

One canonical string removes three classes of drift

Many browser graphics tools maintain separate implementations for the editor, the vector download, and the bitmap export. The preview may be Canvas or WebGL, the SVG may be reconstructed later, and the PNG may capture the surrounding DOM. Small differences accumulate: colors come from page CSS, fonts disappear, filters render differently, or a hidden control leaks into the image. A user can no longer predict which version is authoritative.

Signal Press goes the other direction. A pure renderer receives a normalized recipe and returns one complete SVG string. Attribute order, numeric precision, IDs, metadata, whitespace, and playhead phase are deterministic. The preview parses that string. Copy SVG returns it. Download SVG wraps it in a Blob. PNG asks the same renderer to resolve the selected timeline phase into static geometry, decodes it as an image, and draws it to a scaled canvas. The app does not serialize a mutated preview DOM, so focus rings, drag handles, or UI text cannot leak into the artwork.

This is a narrow claim, not a universal architecture. Same-browser renders of the same recipe can be byte-identical because Signal Press controls the string builder. Different browsers may parse and reserialize XML differently, so cross-browser verification focuses on the visible geometry and exported dimensions instead of pretending that every engine will emit identical bytes.

Three engines share intent, not appearance

Current, Contour, and Loom use one recipe model, but they are not skins. Current establishes direction. It samples an irregular field, combines the vector influence of up to four focal basins, rotates each capsule through global flow and bounded counterflow, then removes marks to create one interruption. Contour establishes pressure. It draws a small family of closed, edited rings around the focal set's shared field and leaves most of the page alone. Loom establishes relationship. A few long paths cross in a controlled order while protecting the territory between focal points. Their output topology, node count, and visual rhythm are deliberately different.

The shared controls describe editorial intent: focus strength, signal reach, headline clearance, reading direction, and format. Each mode translates those concepts differently. Reserved headline bends Current away from an opening, omits Contour rings near the calm field, and routes Loom around a structural void. The geometry changes because the communication job changes. That is more useful than applying one density number to three unrelated algorithms and calling the result a system.

Portable SVG is a productive limitation

A standalone SVG cannot assume that the destination page has the same stylesheet, font files, image permissions, or JavaScript. When an SVG is loaded as an image, browsers restrict scripts and external resources. Those restrictions are useful here. Signal Press exports only trusted geometry, presentation attributes, a title, a description, and deterministic recipe metadata. It uses no remote images, web fonts, event handlers, scripts, or HTML inside foreignObject.

The last omission is deliberate. The SVG specification permits embedded foreign XML, including HTML, but browser and vector-editor behavior remains less consistent than pure SVG geometry. Tools that screenshot arbitrary DOM often rely on a foreignObject bridge. That is appropriate when the product is a screenshot tool. It is unnecessary risk when the product already owns the vector source.

Portable does not mean unbounded. Large canvases consume memory quickly, especially on phones. Signal Press advertises only fixed formats whose 4× output fits under its pixel and maximum-side limits. The rasterizer waits for SVG image decoding, checks that Canvas 2D and toBlob succeed, and revokes every temporary object URL. A transparent preview uses a checkerboard in the app shell, but that checkerboard never enters the exported source.

PNG is a delivery format, not a second renderer

The browser already knows how to paint SVG. The export path uses that implementation instead of translating every path into a separate Canvas drawing routine. The app creates an SVG Blob, assigns its object URL to an image, waits for decode, and draws the image onto a canvas at 1×, 2×, or 4×. Canvas then returns a PNG Blob through toBlob. This keeps the bitmap aligned with the inline vector artifact while avoiding the memory expansion of a large base64 data URL.

The origin-clean rule still applies. Drawing a cross-origin image without the right CORS headers can taint a canvas and prevent export. Signal Press sidesteps the issue by shipping no external artwork at all. If image or font inputs are added later, they will need explicit fetching, licensing, embedding, failure states, and tests. Hiding that complexity behind a generic upload button would make today's clean export contract untrue.

Taste lives in defaults and failure conditions

A generative tool can expose every constant and still offer very little control. Users then search slider space for a composition the product should have provided. Signal Press keeps the visible tier small: intent, format, palette, density, focus, and signal reach. Fine tuning exists, but it starts closed. Presets are communication briefs rather than cosmetic themes. Hot path creates one accelerated route. Reserved headline protects a usable opening. Split decision creates directional tension.

The stronger quality gate is negative. Current fails if it becomes uniform vector-field wallpaper. Contour fails if it looks like raw topographic output. Loom fails if a primary ribbon crosses the headline opening. Every mode fails when accent color becomes confetti, negative space disappears, controls outweigh the artwork on a phone, or the default needs repair before it can be published. Those conditions are more actionable than a claim that the result should feel premium.

Verification has to include the artifact people take away

Build success proves very little about visual software. The browser checks the page at narrow and wide viewports, exercises every mode, adds, selects, removes, and drags focal points, verifies that animated marks change length around stable anchors, opens both disclosures by keyboard, and watches for console or request failures. It exports SVG and PNG at fixed dimensions, parses metadata, checks unsafe nodes, and balances temporary object URLs. Reduced-motion mode stops autonomous movement without disabling direct manipulation.

Automated checks still cannot award taste. The review set therefore includes unlabeled grayscale thumbnails, realistic editorial contexts, maximum-complexity states, and a side-by-side comparison with the source reference. Independent reviewers score each mode and the shell separately. If they cannot distinguish Direction, Pressure, and Relationship without labels, the system has three implementations but only one idea.

Start from the communication job

Use Current when the reader should feel direction before they read detail. Use Contour when the page needs an area of pressure or emphasis without a literal chart. Use Loom when relationships must frame a headline, product, or number. Then choose a preset, place one to four focal points, and export the source. If the image needs an explanation to justify its marks, change the composition rather than adding more controls.

The operating principle is simple: shape once, publish as SVG, and let every other format derive from that artifact. The constraint reduces implementation drift. More importantly, it makes the product show its judgment in the only place that matters: the graphic itself.