Skip to content

Contributor Rulebook

Jump to bottom
SHAURYASANYAL3 edited this page Jul 24, 2026 · 2 revisions

Contributor Rulebook

We run a lean, brutalist engineering operation. To keep our review queue moving and our codebase robust, we enforce strict guidelines for all pull requests. If you violate these rules, your PR will be closed.

1. The YAGNI Mandate

You Aren't Gonna Need It. We do not merge "preparation hooks," "speculative abstractions," or unused theoretical architectures. If a feature is not actively being used in the critical path right now, do not submit it. Build what is needed today.

2. V2 Performance Constraints (0.1ms Latency)

AgentWatch V2 is designed to be a brutally fast, deterministic safety engine.

  • Any PR that touches the core SafetyEngine or the Invariant Lattice must not add significant latency.
  • The latency budget for the entire lattice evaluation is ~0.1ms.
  • No LLM Calls in the Critical Path: Do not attempt to use an LLM to evaluate safety during the execution intercept. Use static rules and Shadow Simulators.

3. Issue Assignment Rules

  • Maximum Load: A contributor can claim a maximum of 2 issues at a time.
  • New Contributors: If you are new to the repository and wish to claim a mid or hard issue, you must post a brief approach/plan detailing how you intend to solve the issue before you will be assigned. We do not hold issues for ghosting contributors.
  • Veterans: Consistent contributors with merged PRs can request assignment directly.

4. Pull Request Hygiene

  • One Feature, One PR: Do not bundle unrelated refactors, typo fixes, or feature additions into a single PR. Keep them atomic.
  • No Duplicates: Submitting multiple PRs for the exact same fix or documentation update clutters the board. Duplicate spam will result in immediate closures.
  • No Custom Roll-Your-Own: If a standard, battle-tested library (like tenacity for backoff) exists, use it. Do not write custom mathematical logic for solved problems.

Clone this wiki locally