I’ve been seeing more devs use coding agents like this lately. The productivity boost is pretty interesting. Do you still review most of the code manually?
I use AI coding agents daily.
3 Comments
v0.14.0 is live — our biggest release since launch, and the first where the release pipeline itself is as evidence-backed as the workflows it governs.
If you're new here: Meta-Architect is an open-source workflow governor for AI coding agents. Your agent writes code fast; Meta-Architect makes it prove each stage first — design, evidence, logic, security, experience, build. Each gate stays locked until the one before it passes.
What's New
Compatibility scope
Codex, OpenCode, Gemini CLI, Amp, Claude Code, Goose, Hermes, Pi, Cursor, Windsurf, Cline, Continue, Roo, Kiro CLI, Junie, GitHub Copilot, and Antigravity (coverage evidence)
🛡️ Fail-closed release engineering
main now accepts only verified dev promotions. Every release artifact — including the npm archive — ships with SHA256 checksums, an SPDX SBOM, and a release-summary.json. No generated tarballs in Git, no stale dist files, no exceptions.
🐧 Native Linux packages, no npm required
Debian, Arch, and RPM packages now install and run standalone — real distribution, not just an npm wrapper.
🤖 $maestro grows up
Our singular in-session manager is now backed by a bounded autonomous control plane. It picks the next safe step, acts without permission-begging, and always lands on a terminal outcome with fresh verification evidence.
🧠 Full semantic core runtime — 17 systems
Obsidian brain context, Ralph story execution, Learning Loop with promotion rules, Context Economy, Prompt Strategy, Environment Awareness, Universal Plugin Broker, Redaction Gateway, Quorum Review Engine, Workspace Virtualizer, Code Graph Rehearse, and more — all seeded, all test-covered.
🔍 Evidence you can audit
Every stack claim is graded VERIFIED, PARTIAL, or MISSING against upstream sources through GitMCP. Every v0.14.0 release issue is marked passed with implementation, verification, and production evidence.
🎬 Real demo kit
A repeatable, smoke-tested demo (npm run demo:smoke) showing the full path: idea → gated execution → verified release — using real runtime functions, not static screenshots.
Quick start
# 1. Install (macOS, Linux, WSL, Git-Bash)
curl -fsSLo install.sh https://cdn.jsdelivr.net/gh/JustineDevs/meta-architect@latest/scripts/install.sh && curl -fsSLo install.sh.sha256 https://cdn.jsdelivr.net/gh/JustineDevs/meta-architect@latest/scripts/install.sh.sha256 && sed 's#scripts/install.sh#install.sh#' install.sh.sha256 | sha256sum -c - && sh install.shOR
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.
Please log in to add a comment.
Please log in to comment on this post.
More Posts
- © 2026 Coder Legion
- Feedback / Bug
- Privacy
- About Us
- Contacts
- You Tube
- Tiktok
- Premium Subscription
- Terms of Service
- Early Builders
I use AI heavily, but not lazily. For me, AI is scaffolding, acceleration, compression. It helps me move from idea to structure faster, but I still care about whether the architecture is clean, whether the pieces can survive pressure, and whether the system can still make sense after a month of changes. Speed matters. Durability matters more.
I care about structure more than appearance. If a system looks fine from the outside but hides drift, duplication, confused ownership, or fake abstractions, I do not trust it. I would rather confront the mess early than inherit it later.
I move fast, but not in the careless way people usually mean. Most of my process starts with instinct. I see a shape, a gap, or a system that feels heavier than it should be. Then I move quickly toward a first version. Not because the first version is the goal, but because reality shows up faster when something exists. Show less
More From JustineDevs
Related Jobs
- 212403 Mobile User Interface DeveloperProCom · Full time · Santa Clara, CA
- Warehouse AssociateAmazon · Full time · Waynesboro, PA
- Bilingual Store Associate (Spanish)Sherwin-Williams · Full time · Hagerstown, MD
Commenters (This Week)
Contribute meaningful comments to climb the leaderboard and earn badges!