Welcome to the Aegis community! We are building a universal governance engine for modern development. Whether you are an architect, a security specialist, or a passionate software engineer, your contributions are vital to our mission of automating architectural perfection.
We value specialized perspectives on architectural integrity and code quality.
-
Browse our Issue Tracker.
-
Look for the
good-first-issuelabel. -
Filter by your expertise using our deterministic labels:
- Roles:
role:architect,role:security-engineer,role:devops-sre - Domains:
domain:structural-governance,domain:architecture-strategy,domain:security-compliance - Ecosystems:
ecosystem:mcp-protocol,ecosystem:tree-sitter-ast
- Roles:
-
If you have a new idea, please open a Discussion first to align on the architectural direction.
Aegis uses uv for modern Python package management.
# Clone the repository
git clone https://github.com/seismael/aegis.git
cd aegis
# Synchronize dependencies
uv sync
# Install the Aegis protocol globally for local testing
uv run aegis initAegis is a self-referential system. We use the engine to enforce the project's own architectural invariants. Your PR cannot be merged if it violates these laws.
- Structural Integrity: Adhere strictly to the project's defined boundaries and patterns.
- Domain Isolation: Core logic must never depend on infrastructure implementation details.
- TDD First: Every feature or fix must be accompanied by comprehensive tests.
- Verification: Run the full suite before submitting:
uv run pytest tests/ uv run aegis run --headless-check # Architectural governance gate
By contributing to Aegis, you agree that your contributions will be licensed under the MIT License. We strive for a professional environment where all contributors are respected and recognized.
Thank you for helping us build the future of architectural governance.