Tool 05 Available · v0.1

Tempo.The Metronome

Processes do not die for lack of ideas. They die from losing the pulse.

AI mode: sentinel · watches time, does not manage it Phase: cross-cutting Element N.7 · Times, Rhythms and Cycles
01The problem

Almost all the expensive breakdowns of a participatory process are temporal. And almost none of them is designed.

A process that disappears for weeks loses the trust that took months to build.

Silence is the most expensive breakdown, and nobody sees it coming because nobody is measuring it.

The usual few stay to the end and they are the ones who determine the decisions.

The meeting that runs over is not a scheduling problem: it is a frontier of exclusion that decides badly.

The elections cut the process from 18 to 8 months.

The territory's political, school and festive calendar collides with the process. Anticipating it is design; discovering it, an accident.

02How it works

A single tool, three movements. Its memory lives in two plain-text files that are yours: partitura.md and pulso.md.

MOV. I

The Score: design

Times (who does this schedule leave out?), rhythm (and who sustains it), cycles with an entry window and a close, external calendar and intensities. The maximum number of simultaneous fronts is agreed in writing.

MOV. II

The Pulse: monitor

Ten minutes a week: you paste the log, the AI checks it against the Score and returns at most three alerts. Every alert ends in a question, never in an instruction.

MOV. III

The Memory: report

At the close: what was promised against what was lived, six figures at most, and what the tempo taught, put in your words. It feeds the Evaluate phase, the public report-back and the report to the promoter.

03The result

The Pulse Panel: the vital state of the process in a single glance. Six figures, the rhythm drawn, and the alerts that ask.

Pulse Panel · Plaza de la Estación process

week 14 of 32 · last log: 12 May

The process is breathing: sustained rhythm and two cycles closed, but the evening session is running over and there is one front too many.

11/12rhythm appointments kept
2/2cycles closed with minutes
4new faces this cycle
2h20real duration (announced: 1h50)
0weeks of silence
4/3active / agreed fronts
RHYTHM · THURSDAYS 18:30
The meeting that decides badly

The last three sessions ran half an hour over. Who was being left out of the decisions at the end?

Overload

You agreed three fronts and the log shows four. Which of the new ones replaces which, or what stops getting done?

The other two objects of the tool: the Process Score (the cycles as arcs over the line of weeks, with the external calendar as its own band and the collisions marked) and the Tempo Memory (two timelines superimposed: the promised one, faint; the lived one, full; the distance between them is the learning, not a failing grade).

04Three rules that are not negotiable

Every alert ends in a question

The AI does not reschedule, does not convene, does not prioritise. It is a metronome, not a conductor: the judgement is yours.

The value is in the silence

The most important thing about tempo is what is not happening: the week without activity, the cycle that does not close, the new face that did not come back.

Six metrics at most

A hundred eyes produce zero decisions. A panel that does not fit in a single glance is no use for deciding.

Start with the Score

The working document is uploaded to the AI you already use, like modules 01 to 04. No new accounts, no platform: your process, your log, your judgement.

Start today · €19 → See the other tools
All ten01020304050607080910index →