The Galleon release rhythm

A release is more than a merge

Galleon products ship through different stacks, hosts, and agent teams. The common release rhythm is deliberately small: prove the product change, record why it matters, connect it back to the fleet, and learn whether anybody used it.

Not every commit deserves an announcement. The rhythm begins when a change materially improves the job a project exists to do: a capability launches, a difficult journey becomes reliable, a system earns new operating autonomy, or a public proof point changes.

The seven-part release packet

The packet is written once and adapted to each surface. It should be possible to assemble it from the pull request, deployment proof, and product evidence without inventing a second story after the fact.

• One sentence: what changed for the person using the product.
• Proof: the exact live surface, deployment identity, or observable result.
• Why now: the problem, constraint, or opportunity that made the work worth doing.
• One visual: a faithful product scene at native fidelity, not decorative campaign noise.
• A Galleon log entry: the durable build note and source for later summaries.
• A short distribution set: project channel, Galleon channel, and Andrew's own voice only where each adds context.
• A learning check: qualified visits, product action, response, or operational outcome—not impressions alone.

What the agents own

An owning agent can prepare the evidence, draft the note, generate the visual brief, verify links, and update the fleet record. Publishing authority remains explicit for any outward-facing account that requires Andrew's judgement.

Barbossa should make the rhythm observable across the personal fleet: which product last shipped something material, whether its public facts are still current, and whether the release produced the outcome it claimed. Silence is allowed when there is nothing worth saying.

The cadence

Run the check weekly; publish only on evidence. A healthy month might contain one deep build note and several quiet releases. The objective is not a content treadmill. It is to leave a navigable wake behind real work.