PerishLab/actions
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages 1 Wiki Activity Actions

Carry every declared projection through the shared lane #43

Merged
PerishFire merged 1 commit from land/plumb-release-contract into main 2026-08-16 12:21:23 +00:00
Conversation 0 Commits 1 Files changed 1 +23
PerishFire commented 2026-08-16 12:19:43 +00:00
Owner
Copy link

Carry every declared projection through the shared lane

ship oci, ship chart and ship npm had no call site anywhere in the estate.
Three adaptors answered, doctor accepted their attachment tables, and no lane
delivered them, so a product could declare an image, a chart or a module and
learn the difference only by looking for the artifact that never arrived.

The lane now prepares and publishes them beside the Cargo attachment it already
carried. Preparing changes nothing outside the workspace, so those deeds run
before the seal and cost nothing for a product declaring no such attachment:
each answers that it has none and succeeds. Publishing runs behind the published
seal, where the same rule binds every medium.

No spelling is probed here. The deeds carry no earlier spelling to fall back to,
so a Plumb that cannot answer them must fail the release aloud rather than skip
a projection in silence.

The lane names no attachment and holds no account. A product declares what it
projects and which forge identity it projects as, and this workflow supplies the
credential and nothing else.

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

Carry every declared projection through the shared lane `ship oci`, `ship chart` and `ship npm` had no call site anywhere in the estate. Three adaptors answered, `doctor` accepted their attachment tables, and no lane delivered them, so a product could declare an image, a chart or a module and learn the difference only by looking for the artifact that never arrived. The lane now prepares and publishes them beside the Cargo attachment it already carried. Preparing changes nothing outside the workspace, so those deeds run before the seal and cost nothing for a product declaring no such attachment: each answers that it has none and succeeds. Publishing runs behind the published seal, where the same rule binds every medium. No spelling is probed here. The deeds carry no earlier spelling to fall back to, so a Plumb that cannot answer them must fail the release aloud rather than skip a projection in silence. The lane names no attachment and holds no account. A product declares what it projects and which forge identity it projects as, and this workflow supplies the credential and nothing else. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Carry every declared projection through the shared lane
All checks were successful
guard / runner-control (pull_request) Successful in 13s
Details
guard / guard (pull_request) Successful in 29s
Details
guard / package-windows (pull_request) Successful in 53s
Details
guard / runner-control (push) Successful in 10s
Details
guard / guard (push) Successful in 28s
Details
guard / package-windows (push) Successful in 32s
Details
427b29d4ad 
Carry every declared projection through the shared lane

`ship oci`, `ship chart` and `ship npm` had no call site anywhere in the estate.
Three adaptors answered, `doctor` accepted their attachment tables, and no lane
delivered them, so a product could declare an image, a chart or a module and
learn the difference only by looking for the artifact that never arrived.

The lane now prepares and publishes them beside the Cargo attachment it already
carried. Preparing changes nothing outside the workspace, so those deeds run
before the seal and cost nothing for a product declaring no such attachment:
each answers that it has none and succeeds. Publishing runs behind the published
seal, where the same rule binds every medium.

No spelling is probed here. The deeds carry no earlier spelling to fall back to,
so a Plumb that cannot answer them must fail the release aloud rather than skip
a projection in silence.

The lane names no attachment and holds no account. A product declares what it
projects and which forge identity it projects as, and this workflow supplies the
credential and nothing else.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Land-Source: plumb-release-contract@314bbe9cfb89267d0257b5ed3d682f4c66a45596
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
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!43
No description provided.