iFMade with iterFact™

iterFact for Joe — The 25-Day Delta

Built as an interactive document with 8 sections in the Obsidian Cyan theme.

A pitch, Joe — built by the thing being pitched

In 25 days, iterFact went from a toolkit to a product.

This page was composed, not authored. Eight sections. One tool call. The deterministic assembler picked the layout, the design system shipped the polish, and the front door never blinked. Scroll and you're reading the pitch in the medium of the pitch.

  • Front door collapsed 5 tools into 1
  • Template path: 2–8 seconds, hosted URL
  • 17 named products. 24 composable sections. 10 recipes.
  • Every artifact is the demo
See the deltaJump to the move

The numbers that changed

March 22, 2026 → April 16, 2026. 25 days. No rewrites, no pivots, just sharper edges.

UX score bridge: 34 → 76

Each upgrade was an independent commit. Stacked, they moved the floor from operator-grade to product-grade.

25 days. Every move was load-bearing.

Not a feature list. A sequence where each shipped thing unlocked the next.

Current platform state

Live as of April 16, 2026

March 22 vs April 16 — capability by capability

Same platform. Same moat. Different front door. Different product.

For Joe, specifically

Open your MCP. Type a goal. Get a URL.

This page is the test. You just scrolled through eight different section types in a composed artifact, rendered deterministically, hosted at a.iterfact.com, built in one tool call. If the pitch is the product and the product shipped, the only thing left is to use it.

create_artifact(goal='…')One call. Hosted URL. Same for you as it was for this page.