Thank you for your interest in contributing to LIFE FORGE. We welcome contributions from researchers, security engineers, systems developers, and artificial life practitioners.
To maintain an enterprise-grade and defense-ready codebase, all contributions must adhere to the following architectural standards:
-
Zero-Emoji Policy:
- No emojis in source code, docstrings, commit messages, documentation, CLI outputs, or UI assets.
- Use standard defense/aerospace ASCII markers:
[OK],[FAIL],[CRITICAL],[HIGH],[MEDIUM],[LOW].
-
Deterministic & Vectorized Implementations:
- Substrate physics and metric calculators must be vectorized using NumPy.
- All random generation must accept and respect explicit
seedparameters for scientific reproducibility.
-
Type Annotations:
- Python code must feature comprehensive type annotations (
from __future__ import annotations).
- Python code must feature comprehensive type annotations (
-
100% Test Passing Rate:
- All contributions must pass the entire test suite without regressions:
pytest -v
- All contributions must pass the entire test suite without regressions:
-
Fork and Clone:
git clone https://github.com/<your-username>/life-forge.git cd life-forge
-
Create Virtual Environment:
python -m venv .venv # On Windows: .\.venv\Scripts\Activate.ps1 # On Linux/macOS: source .venv/bin/activate
-
Install Editable with Development Extras:
pip install -e ".[all,dev]" -
Verify Test Suite:
pytest -v
We actively invite pull requests in the following core areas:
- New Mutators (
lifeforge/evolution/mutators/): Novel environmental pressures (e.g. latency jitter, multi-turn conversational diversion, token budget compression). - New Policy Invariants (
lifeforge/sandbox/oracle.py): Enterprise compliance checks, PII leakage detection, regulatory constraint monitors. - Model Harnesses (
lifeforge/sandbox/): Adapters for local and specialized agent frameworks (LangGraph, CrewAI, AutoGen, Semantic Kernel). - Substrates & Complexity Metrics (
lifeforge/substrates/,lifeforge/metrics/): Additional Artificial Life systems (Lenia, Continuous CA) and open-ended evolution metrics.
- Create a focused feature branch:
git checkout -b feature/your-feature-name
- Write unit tests for all new functionality under
tests/. - Ensure no trailing whitespaces or formatting issues.
- Submit your pull request against the
mainbranch with a clear description of the problem solved and test evidence.