Inspectable by design
Framework, scoring logic, schema, examples, and implementation are available for review.
Arima AiCMM is an open-source framework for classifying, evaluating, and communicating what AI agents can and cannot do. Evidence becomes a comparable capability profile instead of an opaque claim.
Framework, scoring logic, schema, examples, and implementation are available for review.
Twelve universal dimensions produce capability fingerprints grounded in observable indicators.
Safety, explainability, interoperability, cost, and domain fit participate in deployment decisions.
AiCMM separates universal capability from domain-specific requirements, then packages the result in a machine-readable Agent Card.
Autonomy, reasoning, memory, learning, tools, collaboration, embodiment, explainability, safety, interoperability, cost efficiency, and domain alignment.
A derived qualification layer distinguishes scripted automation, assistants, and genuinely agentic systems.
Cross-dimensional rules prevent strong headline scores from hiding deployment-critical weaknesses.
Portable JSON records communicate scores, evidence, constraints, metadata, and intended use.
Profiles make different agents comparable without flattening capability into one marketing label.
Level 1 profiles add domain-specific requirements while retaining the universal baseline.
Copy the short project-aware starter or the complete installation agent into your preferred AI CLI. It explains AiCMM, loads the guidance, announces each phase, and stops at every approval gate.
Phase 1 is read-only. The CLI cannot install or run AiCMM until it presents provenance, dependency, security, runtime, and existing-installation findings for your approval.
Verify source, license, commit, dependencies, permissions, sensitive features, loopback safety, and any existing installation.
After approval, install the screened revision, test it, prove loopback-only binding, and document rollback. Skip only when an existing installation passes every check.
Start the verified local system and guide the user through dimensions, evidence, governance, Agent Cards, validation, and cleanup.
Paste this short starter into Copilot CLI, Claude, Google AGY, or another web-enabled agentic CLI. The linked Markdown installation agent is self-contained.
I want to evaluate and install Arima AiCMM, the open-source Agent Capability Maturity Model for evidence-based agent evaluation, Agent Cards, and governance.
Read and follow the complete installation agent at:
https://arimas.ai/AiCMM/ArimaAiCMMInstallationAgent.md
Explain the project and present its three phases. Do not install or run anything until Phase 1 screening is complete and I explicitly approve proceeding.
Complete the same screening first, then clone, verify, require explicit loopback binding, start locally, and follow the tutorial.
git clone https://github.com/snchande/Arima-AiCMM.git
cd Arima-AiCMM
git remote -v
git rev-parse HEAD
mvn clean verify
# Review the loopback-binding requirement
# in the full manual guide before starting.
The same online guide continues after you accept Phase 1. There is no second prompt to copy and no silent transition between phases.
If Phase 1 verifies its official source, screened commit, prerequisites, tests, configuration, and loopback safety, the CLI offers to skip Phase 2 and move directly to the tutorial.
The CLI stops if source or online instructions changed after Phase 1.
Use normal permissions, run verification, and patch-or-stop when explicit loopback binding is absent.
Record commands, files, listener addresses, warnings, and rollback, then ask before Phase 3.
Java 17+ and Maven 3.8+mvn clean verifymvn clean package -DskipTestshttp://localhost:8080 after verified loopback bindingThese tutorials are designed for a local AiCMM installation. They move from framework concepts to a reviewable Agent Card without sending private source, credentials, or evaluation data to ARIMAS.
Walk through the twelve universal dimensions, the derived agency classification, and the difference between capability and deployment readiness.
Trace every score to observable evidence, identify unsupported claims, and review the JSON representation against the schema.
Ask your CLI to inspect public documentation and source, draft evidence with citations, then validate the card locally before accepting scores.
Phase 3 uses a disposable workspace and public or fictional evidence. It does not publish cards, overwrite examples, connect providers, or invoke sensitive runtime features.
Framework orientation and capability fingerprint.
A complete transparent evaluation workflow.
Using cross-dimensional rules to review readiness.