Make software decisions that survive scrutiny.

Hengmu turns repository evidence into verified findings, compared solutions, ordered remediation, and deterministic quality gates.

Local-first · Python 3.11–3.13 · No hosted runtime

The Qingye builder measures a real gap with code evidence and pulls a remediation wedge into the load-bearing structure

A review should end in a decision, not a list of observations.

  1. Facts
  2. Audit
  3. Verify
  4. Decide
  5. Remediate
  6. Gate

One system view. More than architecture.

System assessment

Performance, reliability, security, data, operations

Technical solutions

Architecture, technology, cost, lock-in, reversibility

Specialized review

AI agents, mobile systems, project portfolios

Decision governance

Evidence, provenance, authority, deterministic gates

One method. Every project keeps its own truth.

One shared method spans different projects while the Qingye builder adjusts for project profiles and real constraints and exposes hidden coupling

Repository

Profile · constraints · critical flows · review history

Portfolio

Shared capabilities · data flow · ownership · hidden coupling

Models propose. Evidence and policy decide what becomes trusted.

A passing gate proves policy evaluation of supplied artifacts — not that a system is automatically correct, secure, or well designed.

Evidence Authority Provenance Policy

Start with repository truth.

git clone https://github.com/qingye-lab/hengmu.git