\n\nDecantr checks the UI change an AI coding agent actually made against the components, styles, interaction rules, and source boundaries already owned by your project. It reports a small set of source-anchored findings without replacing your stack or generating the change itself.\n\n## Check your current UI change\n\nNo account, setup, or adoption step is required:\n\n```bash\nnpx @decantr/cli@3.11.3 verify\n```\n\n```text\nCHANGED UI PROJECT AUTHORITY VERIFY RESULT\nWhat the agent → What your app → Compare the → Pass, attention,\nactually edited already owns current change or not proven\n```\n\nBare `verify` is read-only. It resolves the current Git change, selects exactly one changed UI app only when that choice is provable, and returns at most three consequential findings with source and repair targets.\n\n| Built for adoption | What that means |\n| --- | --- |\n| **Works before setup** | Run it against the current change in an existing Git worktree. |\n| **Respects project authority** | Production source, components, styling, tests, and accepted local rules remain in control. |\n| **Agent-neutral** | Use the CLI, JSON, CI, or MCP with the coding agent and editor you already use. |\n| **Fails closed** | Ambiguous apps, missing Git scope, and unsupported authority return `not_proven`, not a reassuring score. |\n\n## From one check to a governed loop\n\nChanged-UI Assurance is the zero-setup entry point. Teams can deepen it into an authority-aware workflow when they need durable task context and CI evidence.\n\n1. **Observe** project-owned UI authority and state what is unknown.\n2. **Prepare** compact, change-scoped context for any coding agent.\n3. **Verify** the resulting diff against project authority and available evidence.\n4. **Report** typed, reproducible evidence for people, agents, and CI.\n\n```bash\nnpx @decantr/cli@3.11.3 scan\nnpx @decantr/cli adopt --yes # one-time attachment\nnpx @decantr/cli task /feed \"add saved actions\"\nnpx @decantr/cli verify --full\nnpx @decantr/cli ci init # one-time CI setup\n```\n\nIn a monorepo, install once at the workspace root and select the app consistently:\n\n```bash\npnpm add -D -w @decantr/cli\npnpm exec decantr scan --project apps/web\npnpm exec decantr adopt --project apps/web --yes\npnpm exec decantr task /feed \"add saved actions\" --project apps/web\npnpm exec decantr verify --project apps/web\n```\n\n`scan` and bare `verify` are read-only. `adopt` is the explicit one-time write boundary. Use `verify --full` for Project Health and its evidence or baseline options.\n\n## What Decantr treats as UI authority\n\nRoutes are evidence, not the product ontology. Decantr can reason about routes, layouts, reusable components, stories, overlays, flows, design-system packages, runtime states, and exact source files.\n\nIt evaluates authority on independent axes:\n\n- selected app and production surface authority;\n- topology completeness and implementation taskability;\n- component inventory and styling authority;\n- available runtime evidence.\n\nThe deeper workflow reports `ready`, `limited`, `blocked`, or `unsupported`. A numeric score never hides an unresolved axis. Source declaration and deployment reachability remain separate facts, and tests, fixtures, stories, generated files, build output, and sibling apps never become production authority.\n\nSee [UI authority and workflow](./docs/reference/workflow-model.md) for the complete model.\n\n## Local-first by design\n\n- Source inspection and verification run locally.\n- Hosted source upload is retired.\n- Browser evidence stays in the project unless you move it.\n- Existing repository instructions and MCP servers remain project-owned.\n- Production source is the first authority; reviewed local law or style mappings may refine it.\n- Official Decantr content is guidance and never silently overrides the application.\n\nDecantr does not replace your router, component library, styling system, tests, design tools, editor, or coding agent.\n\n## Current release\n\nDecantr **3.11.3** is the current stable Changed-UI Assurance line. It adds SvelteKit task-authority hardening while preserving the existing report schemas and eight-tool MCP surface.\n\n- [3.11.3 release note](./docs/releases/2026-08-08-decantr-3-11-3-sveltekit-task-authority.md)\n- [Change Assurance contract](./docs/reference/change-assurance.md)\n- [3.11 qualification evidence](./docs/research/2026-08-07-decantr-3-11-change-assurance-trials.md)\n- [Package support matrix](./docs/reference/package-support-matrix.md)\n\n### Supported package surface\n\n| Package | Current posture |\n| --- | --- |\n| `@decantr/cli` 3.11.3 | Primary changed-UI and local workflow surface |\n| `@decantr/verifier` 3.11.3 | Primary authority and evidence engine |\n| `@decantr/mcp-server` 3.11.3 | Stable eight-tool agent integration surface |\n| `@decantr/core` 3.10.0 | Supported graph and execution foundation |\n| `@decantr/essence-spec` | Supported contract foundation |\n| `@decantr/content` | Supported policy and reference foundation |\n| `@decantr/registry` | Legacy 3.x compatibility facade |\n| `@decantr/css` | Legacy optional adapter |\n| `@decantr/telemetry` | Optional compatibility package |\n| `@decantr/vite-plugin` | Experimental; outside the primary reliability layer |\n\nThe MCP server preserves exactly eight public tools: `decantr_project`, `decantr_contract`, `decantr_context`, `decantr_graph`, `decantr_registry`, `decantr_verify`, `decantr_repair`, and `decantr_contract_write`.\n\n## Research boundary\n\nDecantr does **not** currently claim that it materially improves frontier-model outcomes. That causal claim is governed by a separate, unfinished, predeclared research program. Deterministic product qualification and shipped availability do not substitute for paired model evidence or independent human review.\n\nRead the [frontier-model lift research program](./docs/programs/2026-07-22-decantr-3-10-ui-change-control-proof.md) and [4.0 entry criteria](./docs/reference/decantr-4-entry-criteria.md) for the complete gates and current limitations.\n\n## Development\n\nRequires Node.js `>=20.19.0` and pnpm `>=9`.\n\n```bash\npnpm install\npnpm build\npnpm test\npnpm qualification:3-11:changes\npnpm benchmark:3-10:validate\n```\n\nPaid research execution is not implied by product release validation. It requires explicit budget approval, configured provider credentials, frozen treatment artifacts, sealed evaluators, and independent review.\n\n## Documentation\n\n- [Existing apps](./docs/guides/existing-apps.md)\n- [Change Assurance](./docs/reference/change-assurance.md)\n- [AI assistant setup](./docs/guides/ai-assistant-setup.md)\n- [Workflow model](./docs/reference/workflow-model.md)\n- [Command surface](./docs/reference/command-surface.md)\n- [FAQ](./docs/faq.md)\n- [Release notes](./docs/releases)\n- [Research and qualification evidence](./docs/research)\n\nHistorical programs, audits, benchmarks, and release notes remain available as evidence of what was proposed or shipped at that time. They do not override active references or convert regression evidence into a model-lift result.\n\n## License\n\nMIT. Test-corpus repositories retain their own licenses and are not redistributed by Decantr.\n",
"bytes": 7955,
"sha": "59ceca6524fbed698e286badda1697236cf2758afc7cdb749972aa2aa58ac788",
"repo_slug": "decantr-ai/decantr",
"fonte": "repo",
"truncated": false,
"api": "https://agentalog.com/api/listings/mcp_io_github_decantr_ai_mcp_server_ee311441/readme"
}
![\"Decantr\"](\"./docs/logo.svg\"){kind=logo}
\n \n![\"Watch](\"./docs/assets/readme/decantr-product-film-poster.webp\")
\n \n