Deterministic
Validate architecture intermediate representation with deterministic IR-LINT, policy packs, and drift checks against exports in agent-driven design loops.
Overview
io.github.archradhq/deterministic is an MCP server for the Ship phase that performs deterministic IR and IR-LINT validation, applies policy packs, and detects drift versus architecture exports.
What is this MCP server?
- @archrad/deterministic npm MCP server v0.4.1 (stdio)
- Deterministic IR and IR-LINT validation with policy packs
- Drift detection versus exported architecture artifacts
- Apache-2.0 licensed; GitHub archradhq/arch-deterministic
- Suited to archrad workflows where agents must not silently bend schema rules
- Server and npm package version 0.4.1
- License Apache-2.0 per registry description
- stdio transport; registryType npm identifier @archrad/deterministic
Community signal: 1 GitHub stars.
What problem does it solve?
Agent-edited architecture IR drifts from policy and from exported truth, and nondeterministic review lets bad graphs ship.
Who is it for?
Builders on archrad-style IR pipelines who want MCP-gated validation and drift detection in Claude Code or Cursor.
Skip if: Apps without an IR model, or teams that only need ESLint or Terraform fmt without architecture policy packs.
What do I get? / Deliverables
Your agent can run deterministic lint and drift checks so IR changes either conform to policy packs or get blocked with explicit violations.
- IR-LINT validation results against configured policies
- Drift report comparing IR to exports
- Agent-repeatable deterministic gates before architecture changes land
Recommended MCP Servers
Journey fit
Deterministic validation is a Ship review gate for teams using archrad-style IR before merges and releases, with follow-on use when infra definitions drift in Operate. review fits linting and policy enforcement on structured architecture artifacts rather than writing new application code.
How it compares
Architecture IR lint MCP, not a generic code formatter or cloud deploy skill.
Common Questions / FAQ
Who is deterministic for?
Developers and solo builders maintaining archrad intermediate representation who need agents to validate IR against policy before merge or deploy.
When should I use deterministic?
Use it during Ship review when IR or exports change, or when you suspect drift between canonical IR and exported artifacts.
How do I add deterministic to my agent?
Install @archrad/deterministic from npm, add it as a stdio MCP server in your client, and point agent workflows at IR validation and drift tools per the arch-deterministic repo.