Rules and gates

Project and task rules

Project rules apply to project-aware capability Chats, agents, MCP context, and task rounds. A task inherits them and may add task-specific rules. Locked project rules cannot be overridden; an unlocked rule is replaced only by an explicit task override of that exact rule id.

Rule edits affect the next round. Each run freezes effective rules and their revisions in its Context Pack, so changing a rule never rewrites historical evidence. Machine-local and cloud projects use the same inheritance contract.

Authoring

Project settings and the task dashboard provide accessible rule editors, ordering controls, and optional presets for focused React components, focused tests, accessibility, design-token use, and secret protection. Presets create ordinary editable rules; they have no hidden authority.

Gates

Gates are project-configured commands such as typecheck, lint, tests, or the React-component size check. They run in the round's exact workspace after execution and produce pass/fail evidence beside Accept. Rules can ask an agent to follow a convention; only a Gate can deterministically prove that a command passed.

Invalid or unreadable configured rules fail preparation closed rather than silently running without the user's constraints.