Skip to content

docs(jules): retire sentinel/bolt/palette daily audit contract #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
RazorBackRoar merged 1 commit into from
Sep 12, 2026
Merged

docs(jules): retire sentinel/bolt/palette daily audit contract #47

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,8 +126,9 @@ Jules reads this repository-root `AGENTS.md` when it clones the repository. Pare

- Jules runs tasks in an Ubuntu VM; SwiftUI, ImageIO, AVFoundation, iCloud behavior, packaged-app behavior, and macOS runtime behavior are not proven there.
- The repository's GitHub macOS `quality` workflow is authoritative for merge readiness.
- Daily audits must inspect existing open and recently closed PRs before proposing work, avoid duplicates, and open at most one focused PR per task.
- `sentinel-*` security, `bolt-*` performance, and `palette-*` design branches always require human review.
- **Daily sentinel / bolt / palette audit branches are retired.** Do not create `sentinel-*`, `bolt-*`, or `palette-*` branches for scheduled security, performance, or design audits.
- Open **real fix PRs only** (concrete bugs, dependency updates, or code-health fixes with a clear verified defect). Inspect existing open and recently closed PRs before proposing work; avoid duplicates; open at most one focused PR per task.
- Any **legacy** `sentinel-*` / `bolt-*` / `palette-*` branches that already exist still require human review and owner merge. Do not open new ones.
- Jules PRs are merged by the owner. There is no auto-merge workflow.
- PR descriptions must list changed files, risk, verification commands and results, benchmark evidence when relevant, and unverified paths.
- Never auto-merge runtime, dependency, lockfile, workflow, packaging, release, privacy, file-operation, or user-data changes.
Expand All @@ -136,8 +137,10 @@ Jules reads this repository-root `AGENTS.md` when it clones the repository. Pare
- **Jules PR Review**: all Jules PRs require the owner to merge; there is no auto-merge workflow.
- **No Duplicate Issue/PR Reopening**: Jules subagents must verify existing closed and open PRs before proposing repetitive fixes or contact info updates.
- **Branch Cleanup**: Head branches are deleted automatically upon squash-merge.
- **No audit-branch program**: do not schedule or open sentinel/bolt/palette daily-audit PRs. Real fixes only.


### Jules Autonomous Execution Rules
- **Auto-Approve Plans**: Automatically approve execution plans for background suggestions (testing, code health, performance). Do not pause or wait for human plan approval on routine refactoring.
- **Auto-Approve Plans**: Automatically approve execution plans for background suggestions that are real fixes (testing, code health, performance) with a concrete defect. Do not pause or wait for human plan approval on routine refactoring.
- **Batching**: Group related unit tests or code health fixes into a single PR rather than creating endless single-function PRs.
- **Do not invent audit workstreams**: never create `sentinel-*`, `bolt-*`, or `palette-*` branches for standing audit programs.