← Cycles
design · c102archivedstarted Sep 29Auto draft — not yet reviewed

qdash TODOs — 2026-09-25 review

Why we did this

Mark reviewed fourteen app pages and left a page of notes; each note needed to become a real change.

What happened

Thirteen pages changed one at a time, each previewed and reviewed. Tiles say what they count, and Teams leads with coverage.

Before → afterThe Teams page now opens with coverage: how many people have a sensor watching their machine.

Documents

With file names, on their own page →

Start here

Pages

  • /team/endpoints (local dev)
  • /inventory/harnesses/detail (local dev)
  • /inventory/mcp-servers/detail (local dev)
  • /inventory/mcp-servers (local dev)
  • /inventory/models/detail (local dev)
  • /team/sessions (local dev)
  • /inventory/skills/detail (local dev)
  • /inventory/skills (local dev)
  • /team/teams/detail (local dev)
  • /team/teams (local dev)
  • /inventory/tools/detail (local dev)
  • /inventory/tools (local dev)
  • /inventory/workspaces/detail (local dev)
At a glance
6
changes
0
conversations
48
decisions
0
outside helpers
Who helped
MPMark ParsonQpoint team

What changed

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

  1. 1

    The Teams page now opens with coverage: how many people have a sensor watching their machine.

    Teams leads with coverage · came from Mark Parson

  2. 2

    Model pages lost a long "More detail" list that only repeated what was already shown.

    Model pages, trimmed · came from Mark Parson

  3. 3

    Tile names now say what they count: Count, Tool Calls, Tools Used, Installs, Success Rate.

    Names that say what they count · came from Mark Parson

Also in this cycle
  • The sessions list dropped exit codes and flags and added the machine each session ran on. Before → after
  • Skill pages dropped a row of guesses about what a skill might reach. Before → after
  • Every page was previewed with Mark before it changed and reviewed after. 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

No ruling needed: the work itself is the change.

So now

The Teams page now opens with coverage: how many people have a sensor watching their machine.

Someone said

From the record: no recorded conversation behind this one.

We decided

No ruling needed: the work itself is the change.

So now

Model pages lost a long "More detail" list that only repeated what was already shown.

Someone said

From the record: no recorded conversation behind this one.

We decided

c102-D2 The MCP Servers listing's first tile is called Count. — Mark Parson

So now

Tile names now say what they count: Count, Tool Calls, Tools Used, Installs, Success Rate.

Thanks to

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

MP
Mark Parson
Qpoint team

Wrote the notes and corrected every preview

Walked fourteen pages, moved the work to the newer app, made Count the first tile on MCP Servers, kept Team's coverage a title change, and skipped Users.

All images

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

The pairs

Teams leads with coverageBefore → after
→
Model pages, trimmedBefore → after
→
Names that say what they countBefore → after
→
Sessions, tidiedBefore → after
→
Skill pages, simplerBefore → after
→

Everything captured · 26

The full record 48 decisions · 17 key-change entries · 4,633 words · 26 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 c102 →

Qpoint Brand Style Guide