Repository navigation
Home
A declarative Golden Path for .NET, React, and PostgreSQL systems. The standard lives in a versioned catalog, the evaluation is deterministic, and nothing is ever written to the repository you point it at.
Most teams keep their architecture standard in a wiki page, and then have no way to tell whether any repository still follows it. Mestre Yoda turns that standard into a catalog a machine can read, points it at a repository, and answers three questions with evidence rather than opinion.
Which Golden Path fits this repository? How far is the code from that standard, and which gaps block a release? What is the ordered set of changes that would close the gap?
| If you want to | Read |
|---|---|
| Get it running in five minutes | Quick start |
| Install it properly | Installation |
| Understand the vocabulary | Concepts |
| Look up a command | CLI reference |
| Know what a rule means and how to fix it | Rule reference |
| Know how a signal is detected | Signal reference |
| Understand the score | Scoring and compliance |
| Consume it from a program | Provider protocol |
| Run it in CI | CI integration |
| Write your own profile | Authoring a profile |
| Understand the internals | Architecture |
| Know what it will and will not touch | Security model |
Version 0.1.0 is the read-only phase, and it is finished. It reads a
repository, compares what it finds against a versioned profile, and produces a
report and a plan. It does not generate code, does not modify files, and never
executes anything from the repository it reads.
flowchart LR
R["Your repository"] --> I["inspect"]
I --> S["21 signals"]
C["Catalog profile\n21 rules"] --> E
S --> E["evaluate"]
E --> REP["Report\nscore, blocking failures"]
REP --> P["plan"]
P --> T["Ordered tasks\neffects: []"]
git clone https://github.com/thiagocorreanet/mestre-yoda.git
cd mestre-yoda
npm ci
node bin/mestre-yoda.mjs check dotnet-modular-react-postgresql --root /path/to/projectProfile: dotnet-modular-react-postgresql@1.0.0
Status: not compliant
Score: 77%
Rules: 16 passed, 5 pending, 2 blocking
- [blocking] api.version-v1: Version public routes under /api/v1 and document the evolution policy.
- [blocking] security.default-deny: Set an authenticated FallbackPolicy and grant anonymous access only where it is declared.
- [required] database.migrations: Add versioned migrations and validate them before deployment.
- [required] quality.integration-tests: Add integration tests for the API and for PostgreSQL persistence.
- [recommended] quality.architecture-tests: Add architecture tests that prevent unwanted dependencies between layers.
One profile, dotnet-modular-react-postgresql@1.0.0, carrying 6 policies, 4
recipes, 1 gate set, and 21 rules across architecture, API, security, database,
frontend, testing, and operations. Its digest is
sha256:89963b03fac95b7af4972176a46b92143948ddf280b3bc627d53539af797b56f.
See the profile reference for what it prescribes and why.
The normative contracts live in the repository, under
docs/, and
they are what a consumer should treat as authoritative. This wiki explains how
to use the tool, expands the reference material that would bloat those files,
and walks through integration scenarios. When the two disagree, the repository
wins, and the wiki page has a bug.
Repository · Releases · Issues · MIT license
Normative contracts live in
docs/. Where
this wiki disagrees with the repository, the repository is correct.
Getting started
Reference
The catalog
Using it
Project