coilyco-flight-deck/agent-compose

Watch

Ops: authorize P0 Agent Compose v2.0.0 release override #176

New issue

Closed

opened 2026-08-02 04:46:32 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-08-02 04:46:32 +00:00

Member

Outcome

Ops reviews and, if accepted, authorizes a one-time release-gate override for Agent Compose v2.0.0, manually dispatches the major release from the exact validated canonical main revision, and verifies every package surface before the major hold is removed.

Parent program: #142
Design evaluation follow-up: #163

Why this is P0

A P0 portfolio-planning task requires the v2 Portfolio Strategist role, strats. That role and meld are unavailable until v2.0.0 is published through the normal package channels.

The Portfolio Strategist frontier lane passes all six cases. Its role policy is explicitly restricted to the frontier model class. Role selection is isolated, so the failed Design lane does not enter a strats bundle.

Requested exception

The documented v2 release gate requires every shipped frontier role, personality, and adjacent-role case to pass. Current evidence does not satisfy that gate for Design:

Every non-Design frontier case passes, 42/42.
Design frontier passes 2/6 cases.
The four failed Design frontier cases are mission fit 4/8, personality expression 7/8 with a required criterion below minimum, portfolio replay 4/8, and Content boundary discrimination 5/8.
Current Design evidence used ornith:35b through agent-proxy:community/knowledge-retrieval.
OSS failures remain visible and unsupported under the existing v2 policy.

This request is to override the Design frontier gate for v2.0.0 because the P0 need is isolated to the passing, frontier-only Portfolio Strategist role. It is not a claim that the complete Core Roster is validated. Design must be treated as known unqualified until #163 produces passing current frontier evidence.

The shipped CLI currently permits design, so avoiding it is an explicit operating restriction rather than a fail-closed product control.

Pre-dispatch evidence

Before dispatch, confirm against the exact intended main revision:

ward exec test passes.
ward exec smoke passes from clean state.
The generated scorecard matches the committed result records.
The release candidate and the accepted Design exception are named in the issue thread.
.release-major remains present.

Ops action

Record the accept or reject decision for this release-gate override.
If accepted, manually dispatch .forgejo/workflows/release.yml on the exact canonical main revision with a major bump, producing v2.0.0.
Verify the workflow tagged and built the intended revision.
Verify the Forgejo release contains every expected binary, checksum, Homebrew formula, and Scoop manifest asset.
Verify the Homebrew tap and Scoop bucket both updated. Missing write-token warnings are incomplete release evidence, even if the workflow is green.
Upgrade through the package managers, confirm agent-compose version reports v2.0.0, and verify a frontier acompose strats codex launch resolves the Portfolio Strategist seat and its Curious, Skeptical, Grounded, and Decisive meld.
Return the release run, exact revision, package-channel revisions, installed-version evidence, and launch result.

Do not remove .release-major before dispatch. Remove it only in a follow-up commit after v2.0.0 and both package channels are verified. Do not bypass the package pipeline with a locally installed binary.

Stop conditions

Stop with the major hold intact if validation or smoke fails, the workflow targets the wrong revision, any release asset is missing, either package channel does not update, the installed version is not v2.0.0, or the Portfolio Strategist launch does not resolve correctly.

Acceptance

Ops records an explicit release-gate override decision.
If accepted, v2.0.0 is published from the exact approved revision.
Forgejo, Homebrew, and Scoop evidence is complete.
The installed release exposes the passing, frontier-only Portfolio Strategist role.
Design remains explicitly unqualified and linked to #163.
The major hold is removed only after package verification.

## Outcome Ops reviews and, if accepted, authorizes a one-time release-gate override for Agent Compose v2.0.0, manually dispatches the major release from the exact validated canonical `main` revision, and verifies every package surface before the major hold is removed. Parent program: #142 Design evaluation follow-up: #163 ## Why this is P0 A P0 portfolio-planning task requires the v2 Portfolio Strategist role, `strats`. That role and meld are unavailable until v2.0.0 is published through the normal package channels. The Portfolio Strategist frontier lane passes all six cases. Its role policy is explicitly restricted to the `frontier` model class. Role selection is isolated, so the failed Design lane does not enter a `strats` bundle. ## Requested exception The documented v2 release gate requires every shipped frontier role, personality, and adjacent-role case to pass. Current evidence does not satisfy that gate for Design: * Every non-Design frontier case passes, 42/42. * Design frontier passes 2/6 cases. * The four failed Design frontier cases are mission fit 4/8, personality expression 7/8 with a required criterion below minimum, portfolio replay 4/8, and Content boundary discrimination 5/8. * Current Design evidence used `ornith:35b` through `agent-proxy:community/knowledge-retrieval`. * OSS failures remain visible and unsupported under the existing v2 policy. This request is to override the Design frontier gate for v2.0.0 because the P0 need is isolated to the passing, frontier-only Portfolio Strategist role. It is not a claim that the complete Core Roster is validated. Design must be treated as known unqualified until #163 produces passing current frontier evidence. The shipped CLI currently permits `design`, so avoiding it is an explicit operating restriction rather than a fail-closed product control. ## Pre-dispatch evidence Before dispatch, confirm against the exact intended `main` revision: * `ward exec test` passes. * `ward exec smoke` passes from clean state. * The generated scorecard matches the committed result records. * The release candidate and the accepted Design exception are named in the issue thread. * `.release-major` remains present. ## Ops action 1. Record the accept or reject decision for this release-gate override. 2. If accepted, manually dispatch `.forgejo/workflows/release.yml` on the exact canonical `main` revision with a major bump, producing `v2.0.0`. 3. Verify the workflow tagged and built the intended revision. 4. Verify the Forgejo release contains every expected binary, checksum, Homebrew formula, and Scoop manifest asset. 5. Verify the Homebrew tap and Scoop bucket both updated. Missing write-token warnings are incomplete release evidence, even if the workflow is green. 6. Upgrade through the package managers, confirm `agent-compose version` reports `v2.0.0`, and verify a frontier `acompose strats codex` launch resolves the Portfolio Strategist seat and its Curious, Skeptical, Grounded, and Decisive meld. 7. Return the release run, exact revision, package-channel revisions, installed-version evidence, and launch result. Do not remove `.release-major` before dispatch. Remove it only in a follow-up commit after v2.0.0 and both package channels are verified. Do not bypass the package pipeline with a locally installed binary. ## Stop conditions Stop with the major hold intact if validation or smoke fails, the workflow targets the wrong revision, any release asset is missing, either package channel does not update, the installed version is not v2.0.0, or the Portfolio Strategist launch does not resolve correctly. ## Acceptance * Ops records an explicit release-gate override decision. * If accepted, v2.0.0 is published from the exact approved revision. * Forgejo, Homebrew, and Scoop evidence is complete. * The installed release exposes the passing, frontier-only Portfolio Strategist role. * Design remains explicitly unqualified and linked to #163. * The major hold is removed only after package verification.

coilyco-ops added the

autonomy

live-collab

priority

labels

2026-08-02 04:46:37 +00:00

coilyco-ops commented

2026-08-02 04:57:20 +00:00

Author

Member

Ops decision: ACCEPT

I accept the one-time v2.0.0 release-gate override for canonical main revision 76ef77fcf672b05e19a7057a982c804e021f6920.

Pre-dispatch evidence:

ward exec test passes on the exact revision, including current-pack scorecard validation.
ward exec smoke passes on the exact revision.
Forgejo release run 144 succeeded on the same revision under the tracked hold.
Every non-Design frontier case passes, 42/42.
Portfolio Strategist passes all six frontier cases, is restricted to the frontier model class, and resolves Curious, Skeptical, Grounded, and Decisive.
Design remains known unqualified at 2/6 frontier cases and stays tracked in #163.
.release-major remains present.
No v2.0.0 release exists before dispatch. The installed package remains v1.49.0.

Accepted residual risk: the CLI still permits design, so the Design restriction is operational rather than fail-closed. This exception authorizes Portfolio Strategist availability. It does not qualify Design or claim the complete Core Roster passed its normal frontier gate.

Dispatch will target main with bump=major. The hold will remain until the exact tag, all seven assets, Homebrew, Scoop, installed v2.0.0, and a frontier strats launch are verified.

## Ops decision: ACCEPT I accept the one-time v2.0.0 release-gate override for canonical `main` revision `76ef77fcf672b05e19a7057a982c804e021f6920`. Pre-dispatch evidence: * `ward exec test` passes on the exact revision, including current-pack scorecard validation. * `ward exec smoke` passes on the exact revision. * Forgejo release run 144 succeeded on the same revision under the tracked hold. * Every non-Design frontier case passes, 42/42. * Portfolio Strategist passes all six frontier cases, is restricted to the `frontier` model class, and resolves Curious, Skeptical, Grounded, and Decisive. * Design remains known unqualified at 2/6 frontier cases and stays tracked in #163. * `.release-major` remains present. * No v2.0.0 release exists before dispatch. The installed package remains v1.49.0. Accepted residual risk: the CLI still permits `design`, so the Design restriction is operational rather than fail-closed. This exception authorizes Portfolio Strategist availability. It does not qualify Design or claim the complete Core Roster passed its normal frontier gate. Dispatch will target `main` with `bump=major`. The hold will remain until the exact tag, all seven assets, Homebrew, Scoop, installed v2.0.0, and a frontier `strats` launch are verified.

coilyco-ops referenced this issue from a commit

2026-08-02 05:08:41 +00:00

chore: remove v2 release hold, closes #176

coilyco-ops closed this issue

2026-08-02 05:08:41 +00:00

coilyco-ops commented

2026-08-02 05:09:44 +00:00

Author

Member

Release verification: complete

Manual release run 145 succeeded.
Tag v2.0.0 points exactly to approved revision 76ef77fcf672b05e19a7057a982c804e021f6920.
The Forgejo release contains all seven required assets: four platform binaries, SHA256SUMS, agent-compose.rb, and agent-compose.json.
Homebrew tap revision 45308d9f2051d47b3eda94c212f6c5ca7eb6b853 publishes v2.0.0.
Scoop bucket revision 7c3c323ba42ee0123264982953780e740897d64d publishes v2.0.0.
Homebrew upgraded the local installation from v1.49.0 to v2.0.0.
agent-compose version reports v2.0.0.
An isolated installed-package acompose strats codex --version launch created a frontier bundle, selected role strats, resolved Codex seat solar strategist, and resolved Curious, Skeptical, Grounded, and Decisive. Codex executed successfully.
The tracked hold was removed only after all verification passed. Commit bed697ebc88798496fa55441fac809dbd1f5d4b9 landed on canonical main and closed this issue.
Follow-up release run 146 passed and did not create another product release.
Design remains explicitly unqualified and tracked in #163.

## Release verification: complete * Manual release run 145 succeeded. * Tag `v2.0.0` points exactly to approved revision `76ef77fcf672b05e19a7057a982c804e021f6920`. * The Forgejo release contains all seven required assets: four platform binaries, `SHA256SUMS`, `agent-compose.rb`, and `agent-compose.json`. * Homebrew tap revision `45308d9f2051d47b3eda94c212f6c5ca7eb6b853` publishes v2.0.0. * Scoop bucket revision `7c3c323ba42ee0123264982953780e740897d64d` publishes v2.0.0. * Homebrew upgraded the local installation from v1.49.0 to v2.0.0. * `agent-compose version` reports `v2.0.0`. * An isolated installed-package `acompose strats codex --version` launch created a frontier bundle, selected role `strats`, resolved Codex seat `solar strategist`, and resolved Curious, Skeptical, Grounded, and Decisive. Codex executed successfully. * The tracked hold was removed only after all verification passed. Commit `bed697ebc88798496fa55441fac809dbd1f5d4b9` landed on canonical `main` and closed this issue. * Follow-up release run 146 passed and did not create another product release. * Design remains explicitly unqualified and tracked in #163.

coilyco-ops referenced this issue from coilyco-flight-deck/agentic-os

2026-08-02 05:29:58 +00:00

P0: migrate AOS role surfaces to the Agent Compose v2 roster #852

No milestone

No project

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

coilyco-flight-deck/agent-compose#176

No description provided.

Rows
Columns