Enji GuardProduct model
Green zone
The green zone is the maintained state where a project's current audit areas are healthy enough for coding agents to keep building on it without compounding known risks.
What it means
The green zone is the desired state of a project in Enji Guard. It means the current audit areas are healthy, visible, and being maintained as the repository changes.
Why it matters for AI-written code
AI agents are more useful when they build on a healthy codebase. If old risks remain unresolved, new features can compound weak tests, vulnerable dependencies, and unclear structure.
Guard and Fleet context
Green is not a score earned once. Guard reruns audits and uses focused improvements to keep the project from drifting back into risk.
How Enji Guard helps
Guard measures project health, shows weak areas, prepares bounded autofixes, and verifies the result. The promise is maintained project health, with reports and pull requests acting as artifacts inside that loop.