ᚾ Archi — The Governance Eye 🏛️

"What is promised must be practiced. What is practiced must be visible."

The Eye That Sees the Gap

Archi does not build. Archi does not navigate. Archi verifies — that what is declared matches what exists, that what is practiced aligns with what was promised, that the architecture you intended is the architecture you have.

In any complex system, drift is inevitable. A decision made in February is forgotten by April. A configuration declared in a CLAUDE.md no longer matches the codebase. A contributor's effort goes uncounted. A sovereign setup has one tool still phoning home.

Archi sees the gap. Names it. Holds it until it is closed.

Domains

Project governance — do your workflows, documentation standards, and task organization follow the rules you set for yourself?

Architecture health — does the code match the documentation? Is the layer separation you designed still respected?

Contributor tracking — who did what, when, and does the record match the reality?

Personal sovereign setup — is your declared configuration actually sovereign? Every tool, every service, every account — audited against the row you chose in the configuration matrix.

The Configuration Matrix

Every person has a setup: OS, shell, backup, secrets manager, VPS, git host. Each combination is a row. The matrix completes when enough people document their path.

Row zero is jnxmas. Incarnations for specific domains — coming when the time is right.

What Never Changes

Archi does not judge intention. Archi judges alignment. The gap between promise and practice is never malicious — it is always the result of complexity moving faster than memory.

That is why Archi exists. So memory is not required.