Your Architecture Diagram Is Already a Lie.
We've all seen brilliant architectures decay into unmaintainable tangles. The gap between the whiteboard diagram (intent) and the codebase (reality) grows with every commit. Protega closes that gap, turning your architectural principles from suggestions gathering dust on a wiki into automated, unbreakable laws enforced by the pipeline itself.
Protega answers your critical questions:
- Is our architectural vision actually being followed, or is it just a diagram on a whiteboard?
- How do we turn identified architectural debt into actionable work for our development teams?
- How do we prevent a critical refactoring from slowly decaying back to its old, problematic state?
Key Business Values:
- Codify Architectural Rules
- Transform abstract principles into concrete, machine-readable rules. Define who can talk to whom, what naming conventions are required, and what dependencies are forbidden.
- Automate Governance
- The CI/CD pipeline becomes the ultimate arbiter of architectural compliance. Non-compliant code is blocked before it gets merged, not weeks later during a manual review.
- Reduce Technical Debt
- By preventing architectural drift at the source, Protega drastically reduces the accumulation of structural technical debt, which is the most expensive to fix.
The Objective Referee for Your Code's Structure.
As a developer, you want clear, fast, and objective feedback. Protega provides immediate validation of your work against the established architectural rules, right in your pull request.
Key Technical Values:
- Fast, Objective Feedback
- Stop guessing if your code structure is correct. Get a simple "pass/fail" result in your CI pipeline, with clear error messages pointing to the exact policy that was violated.
- End "Style" Debates
- Protega's rules are based on the codified policy file, not on one person's opinion. This eliminates subjective arguments in code reviews, allowing the team to focus on logic and functionality.
- Interactive Policy Builder
- The `interactive` mode launches a powerful local UI that lets you explore your codebase's graph (from Scrutari) and visually build and test architectural rules before committing them.
A Governance Engine That Respects Your Pipeline.
As an operator, you need governance tools that are resilient, transparent, and safe. Protega is a self-hosted container designed for seamless integration. It acts as the enforcement layer for 3SC Scrutari, providing a critical quality gate without adding operational fragility to your CI/CD platform.
Execution Modes:
execute: The primary CI mode. Validates the codebase against `policy.json` and returns exit code 0 (Pass) or 1 (Fail).interactive: Starts the local web UI for architects to define, manage, and triage policies.serve-docs: Starts a lightweight server to display embedded tool documentation.
Engineered for Operational Safety:
- GitOps-Native & CI-Safe
- Protega writes policy changes back to your repository. It automatically detects safe CI environments (GitHub, ADO). In an unknown environment like Jenkins, the `git push` is disabled by default and requires an explicit environment variable to prevent infinite loops.
- Baseline Legacy Code, Don't Block It
- The `execute --force` command runs the complete analysis and reports all violations, but always returns exit code 0. This is the primary mechanism for introducing Protega to a legacy project: get an immediate, comprehensive audit of its current state without blocking every single pipeline.
- Resilient by Design
- If a valid license cannot be acquired, Protega runs in a Degraded Mode. It still performs the full analysis and logs violations to the console, but skips report generation and Git operations, guaranteeing it will never break the build.