Mneme HQ provides architectural governance for AI-assisted development across languages, frameworks, and infrastructure ecosystems. The governance layer is language-agnostic by design; depth varies by ecosystem — deepest in Python, operationally strong in TypeScript and JavaScript, repo-level for Go, Java, C#, and Rust, and extended to frameworks (FastAPI, Spring Boot) and infrastructure as code (Terraform) through the same repo-native rules.
Supported languages

# 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, the framework ecosystems, and the infrastructure-as-code surface 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.

Python Tier 1 · production-grade

Native CLI, real benchmark coverage, dogfooded in production repos. Backend services, FastAPI / Django / Flask, AI/ML pipelines, CLI tooling.

Python governance →
TypeScript Tier 1 · operationally supported

React, Next.js, Node.js. Architectural boundary enforcement, forbidden-dependency checks, agent-workflow governance. Semantic/AST depth is roadmap.

TypeScript governance →
JavaScript Tier 1 · operationally supported

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.

Go Tier 2 · repo-level

cmd/, internal/, pkg/ boundaries. go.mod allow-listing. ADR enforcement. CI workflow governance.

See full matrix →
Java Tier 2 · repo-level

Layered architecture rules (controller / service / repository). Repo-level governance. CI integration. Spring-aware packs are roadmap.

See full matrix →
C#Tier 2 · repo-level

.NET solution layout, namespace rules, NuGet allow-listing. Roslyn-assisted depth is roadmap.

See full matrix →
Rust Tier 2 · repo-level

Workspace and crate-level rules. Architectural enforcement. AI agent governance. Clippy/rustc-assisted depth is roadmap.

See full matrix →

## Frameworks & ecosystems

Framework-level governance pages. The same repo-native decision corpus, focused on the architectural surface of a specific ecosystem — no bespoke parser or framework plugin required.

FastAPI Python ecosystem · repo-native

Router, service, repository, and schema boundaries. Thin route handlers, dependency-injection discipline, and consistent auth dependencies in fast-moving Python APIs.

FastAPI governance →
Spring Boot JVM ecosystem · repo-native

Controller, service, repository, and domain boundaries. Approved starters, transaction boundaries, and Spring Security and Actuator policy across enterprise Java.

Spring Boot governance →

## Infrastructure as code

Agents don't only modify application code — they modify the infrastructure and configuration where architectural decisions become operational reality. Governed through the same repo-native corpus.

Terraform Infrastructure as code · repo-native

Approved modules over direct resources, provider and region constraints, network-exposure and encryption rules, and protected state-backend and locking configuration.

Terraform governance →

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.

Strategic positioning
Mneme governs AI-assisted engineering.
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.

## More ecosystems coming

More framework-level governance pages are in progress. Next up: React, Next.js, and Django.

## Get started

Source GitHub → MIT-licensed. Works on any language repository. Reference CLI → Commands and exit codes — same surface across languages. Reference Full coverage matrix → Canonical docs page with limitations and roadmap per language.