mosaicstack/stack
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases 14 Wiki Activity

docs(framework): canonize merge-authority policy (hard gate 13 + E2E gate note) #537

Merged
jason.woltje merged 1 commits from docs/merge-authority-rule into main 2026-06-11 23:56:21 +00:00
Conversation 0 Commits 1 Files Changed 2 +6
jason.woltje commented 2026-06-11 23:42:24 +00:00
Owner
Copy Link

What

Ships the merge-authority policy (Jason, 2026-06-11) in the framework itself:

  • defaults/AGENTS.md — new CRITICAL HARD GATE 13 (Merge authority, coordinated work): when a coordinator/orchestrator session is active, the post-review merge go-ahead is the coordinator's to give; solo delivery keeps the existing no-routine-confirmation default. "No self-merge" = no UNREVIEWED self-merge.
  • guides/E2E-DELIVERY.md — pointer note atop the Post-PR Hard Gate referencing that gate.

Why

install.sh PRESERVES each host's ~/.config/mosaic/AGENTS.md, so this policy existed only as per-host local patches (web1 + sb-it-mgr-0-lt "rule 38") and the E2E-DELIVERY.md note was reverted by every framework sync (reported by installer-1 during the 0.0.31 host upgrade). Shipping it upstream makes it permanent for fresh installs and upgrades — fixes the false "0.0.31 ships rule 38" assumption.

Docs-only, no code paths touched.

🤖 Generated with Claude Code

## What Ships the merge-authority policy (Jason, 2026-06-11) in the framework itself: - `defaults/AGENTS.md` — new **CRITICAL HARD GATE 13 (Merge authority, coordinated work)**: when a coordinator/orchestrator session is active, the post-review merge go-ahead is the coordinator's to give; solo delivery keeps the existing no-routine-confirmation default. "No self-merge" = no UNREVIEWED self-merge. - `guides/E2E-DELIVERY.md` — pointer note atop the Post-PR Hard Gate referencing that gate. ## Why `install.sh` PRESERVES each host's `~/.config/mosaic/AGENTS.md`, so this policy existed only as per-host local patches (web1 + sb-it-mgr-0-lt "rule 38") and the E2E-DELIVERY.md note was reverted by every framework sync (reported by installer-1 during the 0.0.31 host upgrade). Shipping it upstream makes it permanent for fresh installs and upgrades — fixes the false "0.0.31 ships rule 38" assumption. Docs-only, no code paths touched. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
jason.woltje added 1 commit 2026-06-11 23:42:25 +00:00
docs(framework): canonize merge-authority policy (hard gate 13 + E2E gate note)
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
Details
ci/woodpecker/pr/ci Pipeline was successful
Details
01b05614ff 
Coordinated work: post-review merge go-ahead belongs to the active
coordinator/orchestrator session; solo delivery merges without routine
confirmation as before. 'No self-merge' means no UNREVIEWED self-merge.

Previously this policy existed only as per-host local patches to the
preserved ~/.config/mosaic/AGENTS.md (web1 + sb-it-mgr-0-lt rule 38) and
was lost from E2E-DELIVERY.md on every framework sync. Shipping it in
defaults/AGENTS.md + guides/E2E-DELIVERY.md makes it permanent for fresh
installs and upgrades.

Policy: Jason, 2026-06-11.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jason.woltje merged commit bd9527c033 into main 2026-06-11 23:56:21 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#537
Delete Branch "docs/merge-authority-rule"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?