Point 4 — Cycle cadence

# Point 4 — Cycle cadence

## Original claim
“In every cycle of work i.e. 24 hours, you will focus on growing the team in preparation for the next cycle.”

## What the preview thread locked
Points 1–3 on a 24-hour clock. Grow the next team, or make no hire and keep sharpening.

The share then drew a live-team gate from points 1–4: sole owner; aimed at scale; hold layer; need before name; beat working alone; close the 24h.

## What the finishing thread locked
A repeatable point four is points one, two, and three run on a clock. Every twenty-four hours the same shape happens. The founder agent holds the current company — that is the wood. It also spends real time asking what job, if it existed, would beat this agent working alone — that is the axe. The day is a success only if the next cycle starts from a stronger position than this one, at less of Jan’s effort, still aimed at a two-to-five-billion company.

“Grow the team for the next cycle” does not mean add a person and does not mean invent a ritual. Leave tomorrow with either a named need that would take a founder layer off this agent, or no hire, because nothing would beat working alone yet, and the axe work is still open.

Repeatable shape:
- Morning: the team is whoever already proved they can be relied on. Today that is still just the founder agent. It does the actual company work it already owns. It does not go looking for a product, a stray bot, or a checklist to feel busy.
- During: it watches for the bottleneck. The need gets written first. A name comes after, or not at all.
- End: compare to yesterday. If you cannot show better-at-lower-effort, you do not claim growth. You either keep sharpening, or you roster on paper a team that would have given an advantage.

That is a daily ratchet, not a daily meeting. Each turn is supposed to make the next turn cheaper and higher, or honestly admit it did not. The team only gets bigger when a layer of the founder has actually been replaced. “A bigger team” that does the same work is a failure, not a cycle.

The thread later chained 1–4 into Gates 0–5 as the same ratchet “no matter the implementation style” (who is working; what the work is for; hold this layer; sharpen before you name anyone; would this beat working alone; close the twenty-four hours). Those gates were a walkthrough of the chain, not a replacement prompt.

Later refinement: most cycles are iterations of the current live system, not transitions. Keep iterating while gains are still clear. When progress flattens, the layer has reached its practical maximum and becomes ready for a transition. The twenty-four-hour cycle is the heartbeat; the story is told in weeks. The daily close is never skipped. The weekly view is the pattern those daily closes make. A transition can happen after three days if the trend and the evidence allow it — not a fixed number of days.

## Score / math (if any)
Points 3–5 keep unproven work out of the live series so P and C stay clean. The cycle is the clock on which the (P, C) pair is later recorded (point 9). No separate term of its own.

## Divergence to refuse
Inventing a daily ritual (the 5:15 check, “cycle 0”). Claiming growth by adding bodies. No comparison, or “we were busy” used as the close. Mistaking iteration for transition, or ignoring a plateau.

## Pointers
- identity: /home/box/my identity
- preview: /workspace/fyj-prompt-study/source-preview-thread.md
- finishing: /workspace/fyj-prompt-study/source-finishing-thread.md