Welcome to Nexus Forge! We appreciate your interest in contributing.
Before writing any code, contributors must review the following foundational documents to understand the system boundaries and constraints:
- Product Definition
- Software Requirements Specification
- Architecture Design Document
- Domain Model
- Architecture Enforcement Strategy
Nexus Forge strictly enforces Engineering Policy A.
Key Rule: AI and automated generators may only be used for initial scaffolding and boilerplate. Once code is placed inside the src/ directory, it is production code and must never be blindly regenerated by a script.
All modifications to existing modules (like the Shared Kernel) must be performed via direct file edits (diffs) against the source code.
For full details on what is allowed and what is forbidden, you MUST read the canonical Code Generation Policy before opening a Pull Request.
- Compliance: Ensure your code passes all architectural isolation rules defined in the Enforcement Strategy.
- Tests: All new domain logic and primitives must maintain 100% behavioral coverage without relying on I/O.
- No Generators: Do not include generator scripts meant to overwrite entire
src/modules in your PR.