From f7cefcc9ba6f844d203fa6197f611a8dd2d3a10b Mon Sep 17 00:00:00 2001 From: Vitor Mattos Date: Thu, 24 Sep 2026 02:59:17 -0300 Subject: [PATCH] docs: align public Action boundary --- docs/architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture.md b/docs/architecture.md index c8d9d83d..9747e328 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -24,4 +24,4 @@ GitHub Actions is orchestration only. Workflows may check out code, provide cred Machine-readable stage artifacts and consumer configuration are versioned. A mutating stage consumes the artifact from the preceding stage and may revalidate external state, but must not silently recalculate values already finalized upstream. -The public integration boundary is the CLI plus `actions/prepare`, `actions/post-merge`, and `actions/publication`. Organization workflow templates may consume those Actions, but they do not own release policy or release runtime code. +The primary lifecycle integration boundary is the CLI plus `actions/prepare`, `actions/post-merge`, and `actions/publication`. Purpose-specific public Actions may also expose release operations that have independent consumers outside that lifecycle, currently stable selection, artifact validation, metadata inspection, release-note generation, manual release preflight, and App Store publication waiting. These Actions are thin adapters over the same versioned PHP product; they must not become parallel policy implementations. Organization workflow templates may consume the public Actions, but they do not own release policy or release runtime code.