← Cycles
qmap · c15archivedstarted Mar 18Auto draft — not yet reviewed

QMap V1 — Production Component

Why we did this

Fourteen cycles of qmap experiments worked, but other projects couldn't use any of it. The library itself still showed a spinning placeholder shape.

What happened

qmap became one component other projects can import: hand it things, connections and a grouping rule, and it draws the map and animates every change. Five bugs were fixed on the way.

In wordsOther projects can add the map as one component and feed it their own data.

Start here

At a glance
4
changes
0
conversations
1
decisions
0
outside helpers

What changed

The two changes that matter most, in plain words. Open any one to see it.

  1. 1

    Other projects can add the map as one component and feed it their own data.

    One component to import · came from Mark Parson and Jon Friesen

  2. 2

    When the data changes, the map animates to the new state rather than redrawing from scratch.

    Changes animate instead of jumping · came from Mark Parson

Also in this cycle
  • Moving the code shook out five bugs, all fixed. In words
  • The design site's qmap page shows 18 things, with buttons to switch the data and the grouping. In words

How we got here

Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.

Someone said

From the record: no recorded conversation behind this one.

We decided

qmap-c15-D1 A props-driven component: the first load builds directly; every later change goes through the animated reconcile, queued if a transition is running. — Mark Parson

So now

Other projects can add the map as one component and feed it their own data.

Someone said

From the record: no recorded conversation behind this one.

We decided

qmap-c15-D1 A props-driven component: the first load builds directly; every later change goes through the animated reconcile, queued if a transition is running. — Mark Parson

So now

When the data changes, the map animates to the new state rather than redrawing from scratch.

Thanks to

People outside Qpoint first. Every thank-you points at something they said or made.

MP
Mark Parson
Qpoint team

Promoted fourteen cycles of experiments into one component

The record names nobody; credited from git authorship (the March 2026 release commit) and from the design-site test page the record describes.

JF
Jon Friesen
Qpoint team

Set qmap up to be published as a package

Matched, not cited: his four commits the day after the release commit added GitHub workflows, the npm registry and publish config, which is what lets other projects install the component. The c15 record doesn't name him.

All images

Every picture from this cycle. Click any one to step through them all.

The pairs

Everything captured · 0

The full record 0 decisions · 4 key-change entries · 659 words · 0 captures

The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.

Open the record for c15 →

Qpoint Brand Style Guide