Call the ship binary projections #37

Merged

PerishFire merged 1 commit from land/ship-binary-verbs into main 2026-08-14 02:48:09 +00:00

Conversation 0 Commits 1 Files changed 2 +55 -37

PerishFire commented 2026-08-14 02:46:50 +00:00

Owner

Copy link

Call the ship binary projections

Route matrix, build, assemble, publish, verify and smoke through ship binary.
source, authority, inspect, packport, promote, compile, registry and activate
stay on release: the first four are the truth cycle, and the last three are
transitional until a Cargo adaptor and the activate split land.

This must not merge before the Plumb version carrying ship binary activates as
stable. Every job installs the frozen stable Plumb, so the workflow can only
name verbs that the current stable already answers.

Read the release anchor from its ref

The binary and Cargo lanes took channel and version as workflow inputs, so the
anchor reached every job as two strings a human typed into a dispatch form.
Worse, channel bypassed the freeze entirely: resolve emitted version and commit
while build and coordinate re-read inputs.channel directly, which is the second
source the release law forbids.

Derive both from github.ref instead. refs/heads/release/vX.Y.Z carries a stable
version and refs/tags/vX.Y.Z-c.N an exact one; anything else refuses. The
channel then comes from plumb release channel, which owns that rule alone, and
every downstream job reads the frozen resolve outputs.

The concurrency group can call no binary, so it reads the ref directly: a
release line collapses to one consensus group per repository while an exact tag
keys its own, which is what the old channel and version expression produced.

Both inputs stay declared and unread so every existing caller keeps working.
Behaviour is single -- the anchor always comes from the ref -- and the
declarations are inert, so this is a migration window rather than a second code
path. Callers drop them at their own pace; a later commit drops the
declarations once none remain.

Call the ship binary projections Route matrix, build, assemble, publish, verify and smoke through ship binary. source, authority, inspect, packport, promote, compile, registry and activate stay on release: the first four are the truth cycle, and the last three are transitional until a Cargo adaptor and the activate split land. This must not merge before the Plumb version carrying ship binary activates as stable. Every job installs the frozen stable Plumb, so the workflow can only name verbs that the current stable already answers. Read the release anchor from its ref The binary and Cargo lanes took channel and version as workflow inputs, so the anchor reached every job as two strings a human typed into a dispatch form. Worse, channel bypassed the freeze entirely: resolve emitted version and commit while build and coordinate re-read inputs.channel directly, which is the second source the release law forbids. Derive both from github.ref instead. refs/heads/release/vX.Y.Z carries a stable version and refs/tags/vX.Y.Z-c.N an exact one; anything else refuses. The channel then comes from plumb release channel, which owns that rule alone, and every downstream job reads the frozen resolve outputs. The concurrency group can call no binary, so it reads the ref directly: a release line collapses to one consensus group per repository while an exact tag keys its own, which is what the old channel and version expression produced. Both inputs stay declared and unread so every existing caller keeps working. Behaviour is single -- the anchor always comes from the ref -- and the declarations are inert, so this is a migration window rather than a second code path. Callers drop them at their own pace; a later commit drops the declarations once none remain.

PerishFire added 1 commit 2026-08-14 02:46:50 +00:00

Call the ship binary projections ... 77532638dc

Call the ship binary projections

Route matrix, build, assemble, publish, verify and smoke through ship binary.
source, authority, inspect, packport, promote, compile, registry and activate
stay on release: the first four are the truth cycle, and the last three are
transitional until a Cargo adaptor and the activate split land.

This must not merge before the Plumb version carrying ship binary activates as
stable. Every job installs the frozen stable Plumb, so the workflow can only
name verbs that the current stable already answers.

Read the release anchor from its ref

The binary and Cargo lanes took channel and version as workflow inputs, so the
anchor reached every job as two strings a human typed into a dispatch form.
Worse, channel bypassed the freeze entirely: resolve emitted version and commit
while build and coordinate re-read inputs.channel directly, which is the second
source the release law forbids.

Derive both from github.ref instead. refs/heads/release/vX.Y.Z carries a stable
version and refs/tags/vX.Y.Z-c.N an exact one; anything else refuses. The
channel then comes from plumb release channel, which owns that rule alone, and
every downstream job reads the frozen resolve outputs.

The concurrency group can call no binary, so it reads the ref directly: a
release line collapses to one consensus group per repository while an exact tag
keys its own, which is what the old channel and version expression produced.

Both inputs stay declared and unread so every existing caller keeps working.
Behaviour is single -- the anchor always comes from the ref -- and the
declarations are inert, so this is a migration window rather than a second code
path. Callers drop them at their own pace; a later commit drops the
declarations once none remain.

Land-Source: ship-binary-verbs@889c103f4bc30df15f37a5a41c626ef859b7f57c

PerishFire merged commit 77532638dc into main 2026-08-14 02:48:09 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

PerishLab/actions!37

No description provided.