Hengmu
GitHub

Turn repository truth into architecture decisions that survive scrutiny.

Hengmu turns facts, approved design intent, and explicit constraints into evidence-bound current-state assessments, open or constrained targets, decisions, implementation plans, and deterministic gates.

Start with Hengmu View on GitHub

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

The Qingye builder calibrates repository facts and constraints into a target architecture

Start with an assessment or a design brief. End with a governed decision.

  1. Context
  2. Assess / design
  3. Verify / challenge
  4. Decide
  5. Plan
  6. Gate

Assess the present. Design the target. Govern the change.

Current-state assessment

Boundaries, quality attributes, candidate findings, verification

Target architecture

Open or constrained units, data, interfaces, trust, operations

Decisions and plans

Options, trade-offs, authorization, implementation slices

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

One entry. Eight focused architecture workflows.

Use $hengmu — menu or natural-language routing
  1. 01Project audit
  2. 02AI agent audit
  3. 03Mobile audit
  4. 04Portfolio audit
  5. 05Finding verifier
  6. 06Target architecture
  7. 07Implementation planning
  8. 08Quality gate

Start with repository truth or an approved brief.

git clone https://github.com/qingye-lab/hengmu.git
Read the quick start View releases