Ergon is an open-source resolution engineering platform. It turns evidence and organizational knowledge into policy-gated procedures that people and AI can execute, then requires proof that the requested outcome was achieved.
- Ergon models a problem as a case, not as a chat transcript or ticket.
- Versioned resolution contracts describe evidence, actions, approvals, and outcome proof.
- Models may propose; deterministic policy and capability boundaries authorize.
- A case is verified as resolved only after its pinned proof condition succeeds.
- The active implementation is a Kotlin/JVM modular monolith; predecessor executable services have been retired rather than retained as compatibility boundaries.
request -> case graph -> evidence bundle -> resolution contract
-> authorized run -> outcome proof -> improvement proposal
Read the product definition for the vocabulary, positioning, and non-goals, and the architecture for module and trust boundaries.
| Path | Role | Status |
|---|---|---|
domain-kernel |
Framework-free Ergon domain model | Active |
control-plane |
Ergon case, contract, policy, and run APIs | Active |
tools/repository-policy |
Tooling-only repository and documentation policy sensor | Active tooling |
The moving inventory of implemented behavior belongs in current state, not in this entry point.
Requirements:
- JDK 25;
- Docker Desktop or another Testcontainers-compatible Docker runtime for PostgreSQL integration tests; and
- Git with LF line endings preserved by EditorConfig.
Run the fast repository-policy feedback while changing documentation, decisions, milestones, templates, or harness configuration:
./mvnw -B -ntp -pl :repository-policy verifyRun the required full repository verification before completion:
./mvnw -B -ntp verifyFormat Kotlin before committing:
./mvnw -B -ntp ktlint:formatThe root Makefile provides equivalent convenience targets on
systems with make; Maven Wrapper commands remain canonical. See the active
module READMEs for runtime configuration and local startup.
- Documentation map
- Coding harness and feedback tiers
- Contributor workflow
- Tool-facing working agreement
- Engineering standards
- SQL and Flyway criteria
- Implementation milestones
- Architecture decisions
- Security policy
- Code of conduct
Ergon is pre-release. Internal endpoints and local defaults are development boundaries, not production authorization or deployment guidance.