# Decantr

> AI Frontend Governance for production codebases touched by AI agents. Decantr defines contracts, route-scoped context, graph-backed evidence, and repair prompts around AI-edited frontend code.

## Current Product Model

Decantr 3.8.1 is content-first and governance-first. The official corpus lives in `@decantr/content` inside the monorepo and feeds schemas, search, resolution, content health, and execution-pack compilation. The public `registry.decantr.ai` marketplace/portal is retired. `@decantr/registry`, `decantr registry ...`, and MCP `decantr_registry` remain Decantr 3.x compatibility names for content-corpus and pack-resolution workflows.

`@decantr/css` is a legacy optional adapter. Greenfield and Brownfield defaults are contract-only unless `--adoption=decantr-css` is explicit.

## Docs

- [Homepage](https://decantr.ai/): Product overview for AI Frontend Governance.
- [Design contract basics](https://decantr.ai/guides/design-contract-basics.md): Essence, DNA, Blueprint, context files, and the Decantr loop.
- [Existing app adoption](https://decantr.ai/guides/existing-apps.md): Brownfield attach without rewriting the runtime.
- [Monorepos](https://decantr.ai/guides/monorepos.md): Root install, app-scoped attach, workspace health, pinned CI, and what to commit.
- [Project Health CI](https://decantr.ai/guides/project-health-ci.md): Local, GitHub Actions, and generic CI gate setup.
- [AI assistant setup](https://decantr.ai/guides/ai-assistant-setup.md): MCP-compatible assistants and CLI context.
- [Typed graph agent playbook](https://decantr.ai/guides/typed-graph-agent-playbook.md): Contract capsules, route graph context, impact reads, and historical graph reads.
- [Workflow model](https://decantr.ai/reference/workflow-model.md): Workflow/adoption policy for greenfield contract-only, Brownfield attach, Hybrid local law/style bridge, legacy Decantr CSS, adapters, monorepos, and offline mode.
- [Project Health](https://decantr.ai/reference/project-health.md): Local reliability, Evidence Bundle v2, loop readiness, authority resolution, workspace health, browser evidence, Studio, and GitHub artifacts.
- [Command surface](https://decantr.ai/reference/command-surface.md): Current CLI command audit and consolidation decisions.
- [Content Health](https://decantr.ai/reference/content-health.md): Local health checks for the official content corpus.
- [Content API reference](https://decantr.ai/reference/registry-public-api.html): Historical filename; current content/search/schema/intelligence/showcase/pack API surface.
- [Security and permissions](https://decantr.ai/reference/security-permissions.md): Installed package permissions, telemetry defaults, MCP boundaries, and upload posture.
- [Package support matrix](https://decantr.ai/reference/package-support-matrix.md): Stable, legacy, internal, and experimental package status.

## Operational Notes

- For app-scoped monorepos, pass `--project <app>` to `doctor`, `check`, `verify`, `ci`, `task`, `resolve`, `codify`, and `graph`.
- For manual pack hydration, prefer `decantr content compile-packs apps/web/decantr.essence.json --write-context`; legacy `decantr registry compile-packs ...` still works.
- MCP agents should use the submitted eight-tool surface. `decantr_registry` is the compatibility content-corpus tool name; do not expect a ninth content tool in Decantr 3.x.
- Browser evidence is local-only. `decantr verify --base-url <url> --evidence` writes screenshots and Evidence Bundle files under `.decantr/evidence/`.
- CLI telemetry has no Decantr-hosted default. Opt-in is a local preference; network delivery requires an explicit caller-controlled `DECANTR_TELEMETRY_ENDPOINT`.

## Packages

- [@decantr/content](https://www.npmjs.com/package/@decantr/content): Official content corpus, schemas, validation, search, resolution, and health helpers.
- [@decantr/cli](https://www.npmjs.com/package/@decantr/cli): Workflow commands, contract/context generation, Brownfield/Hybrid governance, Project Health, Studio, CI, and content helpers.
- [@decantr/mcp-server](https://www.npmjs.com/package/@decantr/mcp-server): MCP server exposing project state, contracts, context, graph reads, verification, repair prompts, and compatibility content-corpus lookups.
- [@decantr/registry](https://www.npmjs.com/package/@decantr/registry): Legacy compatibility package for content/API client naming in Decantr 3.x.
- [@decantr/essence-spec](https://www.npmjs.com/package/@decantr/essence-spec): Essence schemas, validation, migration, and TypeScript types.
- [@decantr/core](https://www.npmjs.com/package/@decantr/core): Execution-pack compiler, typed graph builders, ranking, evidence/proof ingestion, and Contract capsules.
- [@decantr/verifier](https://www.npmjs.com/package/@decantr/verifier): Audit, critique, Evidence Bundle, loop readiness, authority resolution, diagnostics, and report schemas.
- [@decantr/css](https://www.npmjs.com/package/@decantr/css): Legacy optional CSS atom runtime.

## Repositories

- [decantr-ai/decantr](https://github.com/decantr-ai/decantr): Monorepo for packages, API, docs, and official content corpus.
- Historical separate content repo references should point to `packages/content` in the monorepo after 3.8 migration.