Architectural governance for AI-assisted development
The wrong question is "does Mneme support Python." The right question is whether Mneme governs AI-assisted Python development. Same for TypeScript, JavaScript, and every language on this page.
Strongest coverage
Where Mneme has native runtime depth, benchmark coverage, and worked examples. These are the languages with the heaviest AI coding adoption and the easiest architectural drift demos.
Native CLI, real benchmark coverage, dogfooded in production repos. Backend services, FastAPI / Django / Flask, AI/ML pipelines, CLI tooling.
Python governance →React, Next.js, Node.js. Architectural boundary enforcement, forbidden-dependency checks, agent-workflow governance. Semantic/AST depth is roadmap.
TypeScript governance →Vanilla JS, Node.js backends, legacy React/Vue codebases. Same repository-level governance as TypeScript without type-system assumptions.
JavaScript governance →Compatible via repo-level governance
Compatible today through architectural, dependency, and workflow rules — without ecosystem-specific policy packs yet. Roadmap items where benchmark coverage and demand justify the depth.
cmd/, internal/, pkg/ boundaries. go.mod allow-listing. ADR enforcement. CI workflow governance.
See full matrix →Layered architecture rules (controller / service / repository). Repo-level governance. CI integration. Spring-aware packs are roadmap.
See full matrix →.NET solution layout, namespace rules, NuGet allow-listing. Roslyn-assisted depth is roadmap.
See full matrix →Workspace and crate-level rules. Architectural enforcement. AI agent governance. Clippy/rustc-assisted depth is roadmap.
See full matrix →Integration-based compatibility. Mneme operates above the model and runtime layer. Any workflow using Claude Code, Cursor, GitHub Copilot, custom agent frameworks (LangGraph, AutoGen, CrewAI, OpenAI Agents SDK), or a CI pipeline inherits governance support — regardless of underlying language. See Works With for the full surface.
The codebase's language is downstream.
Cross-language governance before deep language specialization. The decision corpus is the constant; the language is downstream. Add semantic depth where benchmarks and demand justify it — not by default for every ecosystem at once.
Adjacent ecosystems we will document next
Framework-aware governance pages are likely stronger commercial pages than generic language pages. Candidates on the roadmap:
- React governance (component boundaries, hooks rules, state-management standardization)
- Next.js governance (route conventions, server/client component layering)
- FastAPI governance (route / service / data-layer rules)
- Spring Boot governance (controller / service / repository discipline)
- Terraform governance (module-only infra changes, drift prevention)