Skip to content

docs(agents): document the path-scoped merge-gate #10

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
maxwellsantoro merged 1 commit into from
Jun 25, 2026
Merged

docs(agents): document the path-scoped merge-gate #10

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
7 changes: 7 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,6 +72,13 @@ Gates are shell scripts in `tools/ci/`, run via `just`. Representative set (full

S2 needs `S2_COMPAT_KERNEL`/`S2_COMPAT_INITRD`/`S2_COMPAT_ARTIFACT` (or `S2_COMPAT_KERNEL_URL` to fetch).

## Merge policy (path-scoped gate)
The branch rule requires the **`merge-gate`** check, which is path-scoped:
- **Docs/org-only PRs** (no `.rs`/`Cargo`/`idl`/`rust-toolchain`) — the heavy `foundry` job is **skipped**; the PR merges on `org-governance` + `merge-gate` in seconds.
- **OS-code PRs** — `foundry` **runs** and `merge-gate` refuses to pass unless it succeeds. OS-code changes are forced through the full Foundry suite.

All PRs are opened by the `ramen-implementer` bot (A2) and approved + merged by a human (A3); see `docs/org/RAMEN_IMPLEMENTER_BOT.md`.

## IDL workflow
1. Define the interface in `idl/harness/*.toml` (harness) or `idl/portals/*.toml` (portal).
2. `just codegen` → `kernel_api/src/generated/*.generated.rs` (+ sdk/native_runner host bindings + native_runner `generated/mod.rs`).
Expand Down
Loading