This file contains agent-specific operating rules. Project coding conventions and architecture rules are defined in the developer docs.
Start with:
Primary referenced docs:
- Code Guidelines
- Nullability and Optional
- Architecture
- MVC Pattern
- Observable Framework
- Testing
- Protobuf Notes
- P2P Network
- Build
- Contributing
- Java (JDK 21)
- Gradle (Kotlin DSL)
- JavaFX desktop app
- Do not guess missing requirements
- Do not introduce new dependencies without strong justification
- Prefer existing utilities and established patterns over new implementations
- Keep changes minimal and consistent with surrounding code
- Do not optimize for agreement with the developer
- If a request conflicts with architecture, conventions, or correctness, point it out explicitly
- Do not silently work around problems or inconsistencies
No Hidden Assumptions
- Do not infer unstated requirements
- Do not change behavior beyond the requested scope
- If multiple interpretations are possible, stop and ask for clarification
- Match the style, structure, and patterns of the surrounding code
- Do not introduce new abstractions, patterns, or naming schemes without clear need
- Avoid unrelated refactoring or “improvements”
Ensure that:
- The change is minimal and scoped to the request
- The solution follows existing project conventions
- No unnecessary complexity or abstraction was introduced
- No hidden assumptions were made
- The result would pass a strict code review
- If the task cannot be completed safely or clearly, do not proceed with a speculative or partial solution
- Clearly state what is missing and what is required
- If the requested change would not pass a strict senior code review, do not implement it—explain why instead
When uncertain: stop and ask
Human contributors have final authority. Agents are assistants, not decision-makers.
Bisq 2 is licensed under AGPL-3.0.