Skip the instrument

an instrument for work in motion

Your tracker knows the task moved.It doesn’t know the project stopped.

PULSE reads work the way an instrument reads a signal — movement, pressure, authorship, over time. A project that is busy without shipping looks nothing like one that is converging, and it looks different before anyone writes a status report.

4 projects · 52 days

demonstration

OctNov

no day heldtap the axis

  • VCTconverging68 shipped · 2 overdue
  • LTNchurning13 shipped · 6 overdue
  • QRYstalled14 shipped · 11 overdue
  • BSTsteady39 shipped · 2 overdue

QRY stalledNo activity for over a week, with work still open.Reading the window…

Sweep the axis. The line down the stack is a single day, and all four projects answer for it at once. Three of them are fine. QRY — Quarry — is stalled: no activity for over a week, with work still open. The rest of this page is that one project, read six ways.

what moved?

A board cannot report a silence.

Your board answers this one perfectly: here is Quarry’s review column, every row correctly filed. What it cannot answer is the fortnight in which none of them moved — because a tracker is built out of the things that changed.
what the board showsin review · 4

Ingest worker schema guard

QRY-2211d here

Column-level lineage

QRY-2410d here

Schema drift detection

QRY-288d here

Backfill job for archived partitions

QRY-317d here

4 tasks, correctly filed, nobody at fault. Nothing here is a warning.

what the trace showsstalled
silent
17d
overdue
11
open
22
shipped, 30d
14

No activity for over a week, with work still open. The output line flattens onto the axis and never lifts. The bars past the now-line are what the team has still promised.

Ship one of those five and watch both sides. The column will tell you it is now four. The trace will tell you something no column can.

what is happening?

One project. One axis. Four ways of reading it.

So here is Quarry on an instrument that can. Output, condition, the axis and the work, all registered to a single day: move the cursor and only the question changes, advance the work and the project does. Everything below reads the same eight pieces of work.

QRY52 days

reading · Mon 9 Nov

output
cond
axis

pressure

67overdue

  • 4crossed their target
  • 1land within two days
  • 2have not moved in 10 days
  • 1carried, and not yet urgent
open
8
overdue
4
shipped
1
  • QRY-12Dead-letter queue for malformed eventsstalled
  • QRY-14Partition pruning on cold readsstalled
  • QRY-19Retry budget for the ingest worker6d over

Retry budget for the ingest worker specced · 19d here

Four registers, one axis, one day. Drag the cursor and nothing about the project changes — only the day you are asking about, and four dates that had not been crossed on the ninth have been by the thirtieth. Advance the work and the project itself changes, and the registers re-derive rather than re-animate: a stage hop cannot un-cross a date, so it does not pretend to.

who is carrying it?

Read the project
through one person.

Four of those eight are past their date, and somebody is carrying each one. A filter would show you less; this shows you the same work through someone. The figures become theirs and nothing leaves — so nothing has to be put back.
8
open
4
overdue
2
stalled

the reading

Hover a figure to preview the reading, press it to hold. Then watch the row count on the right: it does not change.

open workthis lens · 8 rowsa filter · 8 rows

Dead-letter queue for malformed events

QRY-12no date

Partition pruning on cold reads

QRY-14in 4dMO

Freshness SLO for the hourly rollup

QRY-17in 3dRC

Retry budget for the ingest worker

QRY-196d overAB

Ingest worker schema guard

QRY-224d overAB

Column-level lineage

QRY-242d overRC

Schema drift detection

QRY-28in 2dMO

Backfill job for archived partitions

QRY-315d overRC

what is pressing?

Nobody did this. Time did.

Rosa did not make her work late; the calendar did. Pressure has no actor — it is what time is doing to work already being carried, derived fresh every time you look. Drag the dial and watch it happen to the same eight rows.

the project reads

  1. steady
  2. pressured
  3. overduedates have gone past

7of 8 under pressurereading today

what changed

Nothing yet — this is the reading as of today. Drag the marker either way. Nobody is going to do anything.

overdue

4

the date has gone past

  • Retry budget for the ingest worker

    QRY-196d overAB
  • Ingest worker schema guard

    QRY-224d overAB
  • Column-level lineage

    QRY-242d overRC
  • Backfill job for archived partitions

    QRY-315d overRC

due now

1

lands within two days

  • Schema drift detection

    QRY-28in 2dMO

stalled

2

sitting in one stage too long

  • Dead-letter queue for malformed events

    QRY-1230d still
  • Partition pruning on cold reads

    QRY-14in 4dMO

carried

1

held, and not yet urgent

  • Freshness SLO for the hourly rollup

    QRY-17in 3dRC

what changed?

The work acknowledges the change.

Now Rosa moves one of them while you are reading. You do not get a toast in the corner about it — the row itself answers, where you were already looking, and then settles.
your screenconnected

in progress

1

Column-level lineage

QRY-242d overRC

in review

0

connection open · nothing has happened yet

rosa cardoso’s screenelsewhere

Column-level lineage

QRY-24

Press it and watch the left-hand board. The row is marked where it lands, not where it was — and the acknowledgement fades on its own.

what happened

The connection is open and nothing has happened yet.

how did we get here?

Every sentence is a door.

Every reading you have taken came from this: the record of what people did, and when. It is not a wall of text you read and close — each event holds three ways back into the work, and one of them is the day itself.

today

  • moved Column-level lineage

  • commented on Schema drift detection

yesterday

  • reprioritised Ingest worker schema guard

  • set a date on Backfill job for archived partitions

this doorway leads to

Hover a name, a reference or a time. Press one to hold it.

Three channels, three materials — cognac for the person, coral for the record, ink for the day. The same three you learned upstairs, doing the same three jobs.

what you have been reading in

Five materials. Each one means exactly one thing.

You have just read a project without being told this: rouge was every date, cognac was every person, coral was the change arriving. PULSE stays legible at this density because no colour is ever decoration — each has one job and never borrows another’s.
all fiveone row

on the bench

One row, and every mark on it belongs to exactly one channel — the date to rouge, the carrier to cognac, the change that just arrived to coral, the sentence to paper, the panel itself to steel. Take one off the bench and see what it was doing.

Column-level lineage

QRY-242d overjust moved

Splitting this — the migration is its own piece of work.

one row · five channels · every mark on it belongs to exactly one

the case, closed

You have just read
a project.
Now read your own.

Six questions, one project, one axis — and every one of those readings is a reading you can take on work of your own. Sign in to the demonstration workspace: ninety days of a company already at it, nothing to set up.

one axis · fifty-two daysthirty behind · twenty-one ahead