AI coding agents can generate code quickly. The hard part is knowing whether the architecture makes sense, dependencies are real, logic holds, security was checked, and “done” is actually verified.
It adds a fail-closed release runway:
`Architecture → Evidence → Logic → Security → Experience → Build`
A build stays locked until the required upstream gates pass. Red stays red.
What it includes
- 6 gated lanes — $arch, $sage, $flow, $vet, $vibe, and $build
- $maestro — a bounded manager that reads workflow state and choose the next safe action
- 11 public skills — including $align, $diagnose, $tdd, and $cleanup
- Evidence grading — stack claims are marked VERIFIED, PARTIAL, or MISSING through GitMCP/MCP sources
- Learning Loop — learnings begin as candidates and require source, evidence, authority, and a next verification path before promotion
- Obsidian brain context — vault notes inform planning as vault_context; they do not become build evidence automatically
- Ralph execution — approved plans become story-sized, verification-backed implementation loops
- Security and release proof — MCP policy, redaction, dependency/exposure review, issue-linked evidence, checksums, SBOMs, and release summaries
- 55 supported AI-agent hosts through the Universal Plugin Broker compatibility model
- Native Linux packages for Debian, Arch, and RPM, plus npm and Bash installation paths
Why it’s different
Most spec tools organize what an agent writes.
Meta-Architect governs what an agent can claim to have proven.
It separates discovery from evidence, context from authority, helper work from gate approval, and “looks finished” from verified build readiness.
🧩 Quick start
AI agent installation prompt
Copy and paste this prompt into your AI coding agent:
Install Meta-Architect for this project.
1. Detect the current AI host and its native project configuration surface.
2. Install or update `@jstn-sdk/ma@latest` using the host's supported package manager.
3. Set `MA_AGENT` to the detected host ID when a host-specific surface is available.
4. Run `ma setup` and accept the detected project scope and targets.
5. Verify the generated `.ma/` state and native host artifacts.
6. Report the installed version, selected host, generated files, and any unsupported capabilities.
Do not overwrite user-owned files, modify unrelated configuration, or claim a host is supported without verification.
Uninstall Meta-Architect: npm uninstall -g @jstn-sdk/ma
Uninstall Meta-Architect and Codex: npm uninstall -g @jstn-sdk/ma @openai/codex
Install into an AI vendor host
Install Meta-Architect once, then select the host surface before launch. The
pre-launch step detects installed hosts and writes the selected scope and
targets to .ma/prelaunch.json.
# Codex (reference host)
npm i -g @openai/codex@latest @jstn-sdk/ma@latest
ma --madmax --high
# Claude Code
MA_AGENT=claude-code npm i -g @jstn-sdk/ma@latest
MA_AGENT=claude-code ma --madmax --high
# Cursor
MA_AGENT=cursor npm i -g @jstn-sdk/ma@latest
MA_AGENT=cursor ma --madmax --high
# Any registered host surface
MA_AGENT=<host-id> npm i -g @jstn-sdk/ma@latest
MA_AGENT=<host-id> ma --madmax --high
