← Cycles
design · c29archivedstarted Mar 18Auto draft — not yet reviewed

Cycle Management Consolidation

Why we did this

Six projects each kept their own copy of the instructions for running cycles, and the copies had drifted apart. Updating them meant six edits and guesswork.

What happened

All six projects now share one set of cycle instructions, kept in design, with room at the bottom for each project's own rules. qflow and qmap moved to the same layout.

In wordsOne set of cycle instructions lives in design; the other five projects copy it and add their own extras at the end.
At a glance
3
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

    One set of cycle instructions lives in design; the other five projects copy it and add their own extras at the end.

    One master copy · came from Mark Parson

  2. 2

    qflow's 11 and qmap's 15 past cycles each got a record in the shared layout; their code stayed where it was.

    qflow and qmap fall in line

Also in this cycle
  • Closing a cycle now also saves it with a standard message, and several can be closed at once. 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

c29-D1 Consolidate every project on the cycles folder pattern used in design and bob-wire: the first prompt, the record, and working files. — Mark Parson

So now

One set of cycle instructions lives in design; the other five projects copy it and add their own extras at the end.

Someone said

From the record: no recorded conversation behind this one.

We decided

c29-D1 Consolidate every project on the cycles folder pattern used in design and bob-wire: the first prompt, the record, and working files. — Mark Parson

So now

qflow's 11 and qmap's 15 past cycles each got a record in the shared layout; their code stayed where it was.

Thanks to

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

MP
Mark Parson
Qpoint team

Asked for one way of running cycles

His prompt asked to consolidate around the cycles folder used in design and bob-wire (first prompt, record, working files) and asked how to keep the assistant in sync across projects.

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 · 10 key-change entries · 295 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 c29 →

Qpoint Brand Style Guide