01 Get started
Install the free local core
Obtain approved access, inspect an installation plan and verify the result.
Free software. Approved access today.
The free local core contains the qualification engine, local evidence tools and static atlas. Its MIT licence does not require a Hosted subscription or paid account for local qualification. Your agent-provider access, Fabric capacity and other infrastructure can still cost money.
The product repositories are private today. Public distribution and clean-install release verification remain separate approval steps. Start by discussing approved core access through the design-partner route or contact page; these pages do not promise immediate admission or a public download. Once you have an approved library checkout, the commands below describe the documented repository installation route.
Prepare the right environment
Use Node.js 24 or newer, Git and a supported harness with filesystem and shell access. Bundled package runtimes use Node built-ins and do not need a separate npm installation. Point the installer at an existing repository you are authorised to change.
| Task | What you need |
|---|---|
| Offline learning | Approved library checkout and local tooling. No Fabric or Hosted account. |
| Live source checks | An approved read-only source principal and separate source-read consent. |
| Live Fabric work | Usable capacity, workspace permission, schema-enabled lakehouse and the required query/export capabilities. |
Power BI Premium Per User alone is insufficient for the documented full path. Check your tenant's capabilities rather than treating a historical trial demonstration as proof of your own permissions.
Read the installation plan first
Run these from the approved library checkout. Angle-bracket arguments are placeholders for reviewed target information, not literal paths to copy into a shell.
node tools/agent-skills.mjs validate suites/analytics-spine.jsonnode tools/agent-skills.mjs plan suites/analytics-spine.json --target <target-repository> --profile full --agents openai-codexThe suite offers full, report-only and upstream profiles. Choose the profile from the work you intend to do. Inspect the plan's parameters, target files, adapter capabilities and consent requirements. Resolve values from the target repository; do not invent workspace information to make a plan complete.
The example explicitly selects the Codex adapter. Claude Code also has a documented plugin route for approved distribution. Read Choose a harness before switching routes, and avoid manually copying generated discovery files or manifests.
Apply the reviewed plan and verify it
After approving the target writes, use the matching apply and verify commands. Include the reviewed parameter and consent options if the plan requires them. The example preserves the same target, profile and adapter across both operations.
node tools/agent-skills.mjs apply suites/analytics-spine.json --target <target-repository> --profile full --agents openai-codexnode tools/agent-skills.mjs verify suites/analytics-spine.json --target <target-repository> --profile full --agents openai-codexnode tools/agent-skills.mjs readiness --target <target-repository>Verification checks the installed artifacts. Readiness describes available capabilities. Neither operation establishes that a source read happened, a Fabric pipeline ran or a report qualified. Installation supplies tools; later operations retain their own permission and evidence boundaries.
Learn the failure case before going live
Continue with the offline Sales demonstration. It lets you inspect generated model metadata and a gate that correctly refuses missing proof. Then agree the source question, independent expectations and fact grain before planning a live qualification. Keep business values and retained evidence in customer-controlled custody, outside source control.